A critical distinction for this KB: the five-lean-principles are an abstraction of TPS, not a description of it. Understanding this distinction clarifies both the principles' power and their limitations.
Abstraction vs. Description
A description of TPS would catalog what Toyota actually does: kanban cards, andon cords, the A3 process, standardized work, the chief engineer system, supplier development programs, quality circles, and hundreds of specific practices embedded in organizational routines.
An abstraction of TPS extracts the underlying logic — the why behind the practices — and presents it in domain-independent form. The five-lean-principles do exactly this:
Each principle is a generalization of multiple specific Toyota practices. This is what makes the principles portable — and what makes them incomplete.
What Abstraction Enables
The five principles work as an entry point. A hospital administrator cannot implement kanban cards on a ward, but she can ask: "What does our patient value? What is the patient's value stream? Where does the patient's care stop flowing?" The principles provide a thinking framework for domains far from automotive manufacturing — which was exactly james-p-womack and daniel-t-jones's goal.
The abstraction also enables value-stream-mapping: the diagnostic tool works because the value stream concept is abstract enough to apply to any process, not tied to specific manufacturing configurations.
What Abstraction Loses
Simultaneity. TPS practices interlock. Just-in-time doesn't work without jidoka (if you produce just in time but don't catch defects immediately, one defect shuts down the entire line). The five principles are presented sequentially — Value first, then Value Stream, then Flow, then Pull, then Perfection — implying you can implement them in order. TPS does not work sequentially; it is a system, not a sequence.
Mechanism. The principles tell you what to think about but not how to do it. "Create flow" is a principle; reducing changeover time from 4 hours to 10 minutes (SMED, developed by shigeo-shingo) is a mechanism. TPS is rich in mechanisms; the five principles are mechanism-free. This is why learning-to-see and the LEI workbook series were necessary — they added the mechanisms back.
Culture. TPS is inseparable from Toyota's organizational culture: lifetime employment, consensus decision-making, deep investment in worker training, and the expectation that every employee is a problem-solver. The five principles are culture-free — they can be applied in any organizational culture. But whether they work in any culture is a different question, and one that lean-critique-literature takes seriously.
The Framework's Design
The five principles have the structure of a good management framework: they are sequential (telling managers where to start), memorable (five items), and comprehensive (covering the full arc from customer need to continuous improvement). Compared to TPS's sprawling complexity, the five principles are elegant.
This elegance is both their greatest asset (accessibility) and their greatest risk (oversimplification). The history of lean implementation is partly a history of organizations adopting the framework without the depth — implementing the abstraction and mistaking it for the thing itself.
The relationship between the five principles and TPS is analogous to the relationship between a map and a territory. The map is useful precisely because it is simpler than the territory. But you cannot live on the map.