Integrating the two-headed giant after the Yawata–Fuji merger (1970)
Scale does not become one body by itself
The heart of this problem was how to reconcile the world-leading scale the merger produced with the internal friction that same scale created. The cultures of the two predecessors were called water and oil, and communication silted up as meetings grew larger. That Nippon Steel’s leadership avoided a hurried reorganization and gave priority to reconciliation by consensus — on the view that a genuine new agreement could only be built by passing through the friction — can be read as a decision to absorb the pain of integration slowly, over time. Immediately after its founding, the company was itself the proof that expanding scale does not automatically deliver an integrated organization.
This struggle gradually disappeared from view in the growth that followed. The rationalization gains appeared, and a structure capable of holding the world’s top position in crude steel for many years took shape. But the friction and the communication problems that come with sheer size are things that management-by-scale meets again and again. Half a century after that reunion of two firms separated for a quarter of a century, Nippon Steel went on to the largest cross-border acquisition in its history. How to bind together organizations with different cultures — the question posed in the first months of 1970 — returns in a new form every time the company reaches for scale.
Revenue and net margin, FY1965–FY1975
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY1970 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 Nippon Steel
- 1987 The fourth rationalization and merit pay for managers (1987)
- 2007 Answering ArcelorMittal: a memorandum with Mittal and a three-way defensive alliance (2007)
- 2016 Taking in Nisshin Steel: consolidating blast furnaces under steel deflation (2016)
- 2023 Acquiring U.S. Steel outright — a ¥2tn cross-border deal through a political wall (2023)
- 2025 Facing 3D’s conglomerate-discount campaign against the president’s re-election (2025)
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
Nippon Steel’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/5401/manifest.json | Resource index |
| GET | /api/5401/history.json | History overview |
| GET | /api/5401/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/5401/decisions.json | Management decisions (index) |
| GET | /api/5401/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/5401/executives.json | Executives |
| GET | /api/5401/shareholders.json | Major shareholders |
| GET | /api/5401/financials.json | Financial statements |
| GET | /api/5401/financials-longterm.json | Long-term results |
| GET | /api/5401/segments.json | Business segments |
| GET | /api/5401/regions.json | Sales by region |
| GET | /api/5401/workforce.json | Workforce |