Japan - Mizuho to punish staff for computer glitches

greenspun.com : LUSENET : Y2K discussion group : One Thread

TOKYO - Japanese banking giant Mizuho Holdings Inc will punish more than 100 employees for a string of computer glitches that marred its debut in April as an integrated megabank, a report said today.

The punishment will be the largest punitive measure taken by a Japanese financial institution, the business daily Nihon Keizai Shimbun said.

Under the punishment, some Mizuho employees who were directly involved in computer system programming would be forced to step down while Mizuho president Terunobu Maeda would take a 50 percent pay cut for six months, the daily said.

A spokesman for Mizuho declined to comment on the report.

Business Times

-- Anonymous, June 18, 2002

Answers

Tokyo: Mizuho must upgrade computers

Yomiuri Shimbun

The major computer disaster at Mizuho Bank resulted from downgrading former Fuji Bank's advanced computer system to the lower level of former Dai-Ichi Kangyo Bank's computer system to integrate the two systems into one for the new bank, according to findings of an emergency inspection announced Friday by the Tokyo metropolitan government.

The two banks and the Industrial Bank of Japan were merged and reorganized into retail and corporate banking units, Mizuho Bank and Mizuho Corporate Bank.

The inspection had been conducted based on the Local Government Law because Mizuho Bank had taken over from former Fuji Bank as one of the Tokyo government-designated financial institutions handling transactions for the metropolitan government.

Although Fuji Bank's computer system was more advanced than DKB's system, Fuji Bank's system was downgraded for internal reasons, according to the metropolitan government's inspection.

Because Mizuho Bank's computer system is inferior to the former Fuji Bank computer system, the metropolitan government is worried about whether Mizuho Bank can function properly as a financial institution serving the metropolitan government, according to the Chief Accountant's Office of the metropolitan government.

The metropolitan government summoned Mizuho Bank President Tadashi Kudo on Friday and asked him to upgrade Mizuho's computer system to the level of the former Fuji Bank system as soon as possible. It also told him to report to the metropolitan government on the development of a new system when the bank upgrades its computer system.

Tokyo Gov. Shintaro Ishihara said at a press conference Friday that Mizuho Bank would continue to be a metropolitan government-designated financial institution, but it would step up monitoring of the bank.

===

Mizuho streamlining

The Mizuho Financial Group announced on Friday that 14 executives, including two auditors, of the two banks under its umbrella would resign next Monday.

As the group announced on Wednesday that 18 executives of Mizuho Bank and Mizuho Corporate Bank would be cut from their rosters, it said Friday it would add four more to the list of departing senior personnel in the near future.

The 14 executives are two executive managing directors, four managing directors and one auditor each from Mizuho Bank and Mizuho Corporate Bank. Of the six senior managing and managing directors who will step down, two each are from former Dai-Ichi Kangyo Bank, Fuji Bank and the Industrial Bank of Japan, taking the balance of the three former banks into consideration.

Daily Yomiuri

-- Anonymous, June 23, 2002


A problem of corporate ethos

The Financial Services Agency has ordered the Mizuho Financial Group, whose computer system crashed spectacularly on the occasion of its integration last April, to improve its internal management setup so as to prevent any recurrence of the bungle. Mizuho itself has decided to cut the pay of all of its 107 directors as a punishment. This has confirmed our suspicion that although there were certainly technical reasons for the glitch, it was in fact a man-made disaster. Human misjudgments and poor understanding exacerbated the problem and resulted in huge inconvenience to customers.

The causes of the error can be summarized as (1) a delay in management's decision-making relating to the computer system; (2) inadequate preparations, such as preliminary tests that should have been considered the minimum necessary; (3) a failure to relay important negative information to the top; and (4) a lack of recognition of the risks involved in system integration.

Among these causes, the third factor is the most important. Even though people understood at the test stage that the system was not functioning properly, the negative information remained in the development section and was not transmitted to the top management. Why on earth did the people on the floor not report such important information to the top? Mr. Terunobu Maeda, president of Mizuho Holdings Inc. and chief executive officer of the Mizuho Financial Group, recognized that there was an "atmosphere" in the group that made people hesitant to report negative information to the top. The point that should be severely criticized here is that this atmosphere and ethos in the group, which made it so difficult for employees to directly relay awkward information to their bosses, was ignored by management.

There are two starting points in the management of an organization that lead to completely different atmospheres and results. In the first, you begin with the understanding that people invariably make mistakes, whatever the circumstances. In the second, you start with the battle cry that there must be no errors, whatever the circumstances. The former accepts that mistakes and errors are inevitable and at all times thinks in terms of keeping botches to a minimum. This galvanizes the organization because it encourages individuals to boldly tackle new challenges and issues once thought impossible, even at the expense making of a few mistakes. It is a method based on merit, evaluating results and positive attitudes.

The latter, on the contrary, is a method based on demerit, assuming that things can be done and knocking off points for mistakes and errors. Under this approach, people do only what they are told and grow smaller and smaller as they try as hard as possible not to make any mistakes. Inevitably they become dispirited and view challenges negatively. People conceal any untoward information and put a lid on the truth. As a result, the organization becomes infested with recriminations and a shirking of responsibility. This atmosphere was especially pernicious in Mizuho, a merger of three banks, because employees apparently still felt a strong sense of loyalty to their former banks.

Unfortunately, it is this latter ethos that is the mainstream in Japanese companies. As a stream of recent examples shows, this ethos putrefies and destroys companies: the large banks that went bankrupt after getting carried away in the bubble period; the food-product company that was forced to disband after a scandal involving the mislabeling of beef; the automaker that has plunged into the red after being shunned by consumers following its attempt to conceal defective cars; and so on.

The fundamental cause of Mizuho's problem this time, and also of the problem of nonperforming loans held by banks, boils down to the structure and ethos of Japan's corporate society. So, however much the pay of directors is cut or managers are replaced by new faces, the stream of blunders and scandals that rock the foundations of Japanese companies will only continue unless there is also a change of attitude and a reform of organizational management, from top to bottom.

The problem is not limited to Japan's corporate world, either. It also holds true for the bureaucracy and the political circles of Nagata-cho. That is why this country writhes in agony today. And remember how, not so many decades ago, the Imperial Army and Navy kept the covers on negative information and, riding on a wave of temporary fanaticism, embarked on arbitrary action that led the whole Japanese nation into the fires of war? We have not fully learned the lessons of that huge blunder, either.

Japan Times

-- Anonymous, June 25, 2002


Moderation questions? read the FAQ