Serial system failures and the turn to governance (2021)
Could it call a "system problem" a "management problem"?
The core of this decision was that Mizuho took failures that could have been written off as technical defects and shouldered them as problems of management and corporate culture. To insist that the core system, into which it had poured nineteen years and $3.6B (¥400bn), held no defect, while admitting weaknesses in operation and governance and having the top step down of his own accord — this was an awkward way of taking responsibility, different in kind from confessing that a huge investment had failed. Having followed the same rut as 2002 and 2011, it located the cause not in the system but in the culture, and in that lies how far this decision was willing to go.
That said, culture does not change on command alone. The siloing bred by three banks coexisting, and the air in which no one speaks up to those above, remained even after the systems were bound back together. Some 200 remedial items and the lifting of the order stopped the recurrence for now, but whether that amounts to a mechanical fix or a change in the very quality of decision-making can only be confirmed by the next crisis. The completion of an integration is decided not by technology but by people and culture — a question twenty years in the asking, and one Mizuho still carries.
Revenue and net margin, FY2016–FY2026
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2021 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Other key decisions at Mizuho Financial Group
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
Mizuho Financial Group’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/8411/manifest.json | Resource index |
| GET | /api/8411/history.json | History overview |
| GET | /api/8411/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/8411/decisions.json | Management decisions (index) |
| GET | /api/8411/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/8411/executives.json | Executives |
| GET | /api/8411/shareholders.json | Major shareholders |
| GET | /api/8411/financials.json | Financial statements |
| GET | /api/8411/financials-longterm.json | Long-term results |
| GET | /api/8411/segments.json | Business segments |
| GET | /api/8411/regions.json | Sales by region |
| GET | /api/8411/workforce.json | Workforce |