The Machine That Changed the World
by James P. Womack, Daniel T. Jones & Daniel Roos
The book that named lean — dated examples, but the operating ideas still hold.
- Status
- Read · September 2022
- Bought
- September 12, 2022
- For
- Engineering leads tightening delivery flow · Anyone managing WIP and queues · Ops and platform managers
Where it earned its place
The one-paragraph verdict
This is the MIT study that gave the world the term lean and made Toyota’s production system legible to everyone outside Japan. The strength is the rigor: five years of comparative data across global auto plants, not a guru’s hand-waving. The recurring praise — that it’s unusually readable for a research report — holds up. The recurring criticism does too: it’s a 1990 book steeped in automotive detail, repetitive in places, and some of its triumphalist predictions read as artifacts of their moment. You skim the assembly-line chapters and keep the operating model.
Who should read it
Read it if you lead delivery and want the source text behind WIP limits, pull, and flow rather than a secondhand summary. Engineering and ops managers get the most out of it. If you only want the modern, software-shaped distillation, start with The Phoenix Project or The Goal and come back here later — or not at all.
Where it earned its place
The one idea I actually used is queueing: large batches and high work-in-progress hide problems and stretch lead times. That’s the spine of Reducing WIP — limiting concurrent work so teams finish instead of starting, exactly the pull logic this book documents on the factory floor.
Skip it if…
Skip it if you want a tactical playbook for software teams — this is industrial history and economics, not a sprint guide. The principles transfer; the examples need translation.