How post-war constraints led to a revolution in manufacturing—and thinking.
Lean didn't emerge from abundance. It emerged from scarcity.
Post-World War II Japan faced devastating constraints: limited capital, limited raw materials, limited factory space. American-style mass production—make huge batches, store inventory, push products to market—simply wasn't possible. Toyota couldn't afford to tie up capital in inventory or produce cars nobody wanted.
Taiichi Ohno, a Toyota engineer, saw this as an opportunity. If you can't afford waste, you have to eliminate it. If you can't store inventory, you have to produce just what's needed, when it's needed. If you can't absorb defects, you have to build quality in from the start.
The Toyota Production System (TPS) emerged from these constraints over decades. It wasn't designed in a boardroom—it was evolved on the factory floor through relentless experimentation and observation.
The Core Insight
Constraints force innovation. Toyota didn't succeed despite scarcity—they succeeded because of it. This is why artificially limiting WIP can drive improvement.
The American manufacturing model was Just-in-Case (JIC): build up inventory buffers everywhere to protect against uncertainty. If a machine breaks down, you have inventory to keep the line running. If demand spikes, you have stock to sell.
Toyota flipped this to Just-in-Time (JIT): produce only what's needed, only when it's needed, only in the amount needed.
This sounds risky. What if something goes wrong?
That's exactly the point. In a JIC system, problems hide. The inventory buffers mask issues—a defective batch, a slow supplier, an unreliable machine. You don't feel the pain until the buffer runs out.
In a JIT system, problems surface immediately. There's nowhere to hide. A machine breakdown stops the line. A quality issue halts production. This visibility is a feature, not a bug—it forces you to fix root causes instead of working around symptoms.
Software parallel: Code sitting in branches is inventory. Unreleased features are inventory. A large backlog is inventory. All of it masks problems and delays feedback.
TPS rests on two foundational pillars:
1. Just-in-Time: Flow work through the system based on actual demand. Produce what's needed, when it's needed, in the quantity needed. This minimizes inventory, exposes problems, and creates flow.
2. Jidoka (Autonomation): Build quality in by stopping and fixing problems as they occur. Don't pass defects downstream. Every worker has the authority—and responsibility—to stop the line when they spot a problem.
These pillars support each other. JIT creates visibility by removing buffers. Jidoka ensures that visibility leads to action. Together, they create a system that continuously improves because problems can't hide.
Shigeo Shingo, another Toyota engineer, contributed critical innovations including Single-Minute Exchange of Dies (SMED)—reducing changeover times from hours to minutes. This made small batches economically viable, enabling JIT to work.
In Software Terms
JIT = continuous integration and deployment. Jidoka = stopping to fix bugs rather than piling them in a backlog. Both require the courage to slow down now to go faster later.