Toyota Production System: Beyond Large-Scale Production
Ohno invented the Toyota Production System and this is his own account of how and why — not Liker writing about Toyota, but the man who built it describing the thinking underneath.
The book is short, conversational, and deceptively simple: just-in-time, autonomation (jidoka), the elimination of waste, the respect for people who do the work.
For product direction this is the primary source that Lean, Kanban, and most contemporary agile practices descend from, and reading the original clarifies how much has been lost in translation.
Ohno's Toyota is not about efficiency; it is about thinking.
Read alongside Liker for the codified version and Deming for the statistical-quality complement.
Central argument
Ohno argues that the Toyota Production System is not primarily a set of efficiency tools but a coherent philosophy of manufacturing grounded in two pillars: just-in-time delivery (producing only what is needed, when needed, in the quantity needed) and autonomation, or jidoka — machines and workers empowered to stop production the moment a defect appears. His central claim is that waste, in its many forms, is the enemy of productive capacity, and that eliminating it requires workers at every level to think, not merely execute. The system emerges from necessity — post-war scarcity forced Toyota to do more with less — and Ohno presents this constraint as the generative condition for the entire framework.
Critique
The book describes a system that functioned within a specific cultural, industrial, and historical context — a Japanese manufacturer with stable long-term employment, deep supplier relationships built over decades, and a workforce conditioned by norms of collective responsibility that Ohno largely takes for granted rather than argues for. The account is also unapologetically retrospective and success-biased: Ohno is explaining a system that worked, which means the failures, dead ends, and conditions under which TPS might not transfer are largely invisible. A thoughtful reader will notice that 'respect for people' is invoked as a principle but the human cost of relentless waste elimination and the pressure it places on workers receives almost no critical examination.
Why it matters for product
Ohno's concept of jidoka — stopping the line to surface a problem rather than passing defects downstream — has a direct structural analogue in product delivery: teams that are incentivised to ship velocity metrics will suppress signals of systemic failure, exactly the pathology TPS was designed to eliminate. For a CPO, the more consequential insight is Ohno's insistence that the system must be understood by the people doing the work, not just the people designing it, which challenges product organisations where discovery, prioritisation, and delivery are sequenced through handoffs rather than held in shared context. Reading the original also clarifies that Kanban as adopted in software is a stripped abstraction — the physical card system in Ohno's account is a mechanism for making inventory and flow visible across an entire value chain, a problem most digital product organisations have not seriously solved.