Collegial management as a “great synthesis,” and the move to divisional headquarters (1965)
Choosing to have no one-man ruler
The core of this decision was to replace, with committees and delegation, the founding family’s gravity that the dissolution of the zaibatsu had taken away whether Taisei liked it or not. Rather than entrust an ownerless company once more to a single powerful chief, president Homma Kahei referred management policy to the board of managing directors and confined himself to the chair — a check system, as he called it. His reading of the name “Taisei” as Mencius’ synthesis, a chorus, presented that collective leadership not as an arrangement borrowed from outside but as an idea rooted in where the company came from.
Collegial management is, of course, slower than the flash of a gifted individual, and Homma himself conceded the weakness: “we cannot do anything extraordinary.” Even so, the pattern of dividing authority among headquarters — the great synthesis of organisation — survived as the result of choosing, unusually early in the postwar period, to run on something other than one person, and it shaped the organisational character of the company that later grew into a super general contractor. Not who leads, but by what mechanism decisions are made: this decision is instructive for having put that question into the design of the organisation itself.
Revenue and net margin, FY1960–FY1970
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY1965 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 Taisei Corporation
- 1873 Founding Taisei: from Okura Kihachiro’s trading house to the industry’s first “construction” name (1873)
- 1946 The zaibatsu dissolution and the renaming to Taisei — rebuilding as a company owned by its employees (1946)
- 1987 Correcting decentralisation: reorganising to stop being a pure contractor (1987)
- 2018 Indicted over the maglev bid-rigging — and denying that it was collusion (2018)
- 2025 Acquiring Toyo Construction, a leading marine contractor, by tender offer (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
Taisei Corporation’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/1801/manifest.json | Resource index |
| GET | /api/1801/history.json | History overview |
| GET | /api/1801/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/1801/decisions.json | Management decisions (index) |
| GET | /api/1801/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/1801/executives.json | Executives |
| GET | /api/1801/shareholders.json | Major shareholders |
| GET | /api/1801/financials.json | Financial statements |
| GET | /api/1801/financials-longterm.json | Long-term results |
| GET | /api/1801/segments.json | Business segments |
| GET | /api/1801/regions.json | Sales by region |
| GET | /api/1801/workforce.json | Workforce |