Rebuilding the core: the MINORI system (2012)
Completion did not promise stability
The heart of this decision was the resolve to abandon the path of patching and getting by, and to rebuild the core banking system itself. The two failures had exposed the limits of a design that interconnected the systems while leaving each of the three predecessor banks’ logic intact. What Yasuhiro Sato chose was not a near-term fix but a full migration onto a platform recomposed into functional units. Its scale — some 350,000 person-months and roughly $4.1B (¥450bn) — would tie up domestic IT engineers for years and bind Mizuho’s financial stamina over the long run. Even so, set against the danger of forever deferring an unfinished task, it must have looked like a price worth paying.
The verdict is still unsettled. The full cut-over, nineteen years in the making, resolved on the technical plane the integration that had been deferred at the group’s birth. But immediately afterward MINORI became the stage for eight failures, proving that building a thing does not promise it will run stably. Where the 2011 failure pulled the trigger on the overhaul, the 2021 failures happened on the brand-new platform itself. A vast IT investment easily makes completion its own goal, and the difficulty of keeping the thing running remains after it goes live. Finishing an integration and operating it stably are separate tasks — Mizuho’s MINORI will be remembered as the case that left that lesson behind, together with a price tag of roughly $4.1B (¥450bn).
Revenue and net margin, FY2007–FY2017
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2012 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 |