Mitsuya Kishida becomes president, and the shift to collective leadership (2024)
Choosing to hand over by system, not by reproducing the charismatic founder
The heart of this managerial decision was neither a response to financial crisis nor investment in a new business, but the design of succession — how to hand to the next generation a decision-making that had been concentrated, for half a century, in the founder as an individual. After a run of short-lived departures by executives brought in from outside to reproduce his own way of running the company, Shigenobu Nagamori let go of the idea of seeking a single “second Nagamori” and switched to a selection that set five vice-presidents in competition and to a collective leadership built around Mitsuya Kishida. In shifting his footing from reproducing an exceptional individual toward running the company by a system in which several executives support one another, one glimpses a rare posture of self-relativisation for a succession led by a charismatic manager.
Yet the two-headed structure, with a founder who retained representative authority running alongside, carried to the end the question of how much discretion to allow the successor president. That question moved toward resolution in an unforeseen form — the improper accounting that surfaced in 2025 and the subsequent resignation of Shigenobu Nagamori as a representative director — and real managerial power converged on Mitsuya Kishida. That the company had confronted early the task of loosening its dependence on the founder, while the problems rooted in that very corporate culture erupted midway through the handover, shows just how hard the succession of charismatic management is. The verdict on this decision — an attempt to open a concentration in one person into a system — appears to rest on how far the Kishida regime can achieve both the rebuilding of governance and continued growth.
Revenue and net margin, FY2019–FY2026
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2024 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 Nidec
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
Nidec’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/6594/manifest.json | Resource index |
| GET | /api/6594/history.json | History overview |
| GET | /api/6594/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/6594/decisions.json | Management decisions (index) |
| GET | /api/6594/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/6594/executives.json | Executives |
| GET | /api/6594/shareholders.json | Major shareholders |
| GET | /api/6594/financials.json | Financial statements |
| GET | /api/6594/financials-longterm.json | Long-term results |
| GET | /api/6594/segments.json | Business segments |
| GET | /api/6594/regions.json | Sales by region |
| GET | /api/6594/workforce.json | Workforce |