Manu's Vault

Five-Whys

4 min readStatus:Seedling

Five Whys

A root cause analysis technique that asks “why?” five times in succession to trace a surface-level symptom back to its systemic origin — and, critically, to make proportional investments in prevention at each causal level.

Origins

Taiichi Ohno developed Five Whys as a core tool of the Toyota Production System in the 1950s. The canonical example: a machine stops running.

  1. Why did the machine stop? — Fuse blew due to overload.
  2. Why was there an overload? — Lubrication was insufficient.
  3. Why was lubrication insufficient? — Pump wasn’t circulating oil properly.
  4. Why wasn’t the pump working? — Pump shaft was worn.
  5. Why was the shaft worn? — No mesh screen, so metal swarf got in.

The fix is not “replace the fuse.” The fix is “add a mesh screen.” Replacing the fuse is a temporary patch; the machine will stop again. The mesh screen prevents the entire causal chain from repeating.

Ries’s Proportional Investment Addition

Eric Ries adapts Five Whys for startups in The Lean Startup - Ries - 2011, adding a crucial principle: invest in prevention proportionally to the impact of the problem. For a minor, first-time failure, make a small investment. For a recurring severe failure, invest more substantially.

This keeps teams from two failure modes:

  • Under-investing: treating every problem as one-off bad luck, never fixing underlying systems
  • Over-investing: doing a full system rewrite in response to a minor issue

The proportional response is operationalized in the Build-Measure-Learn-Loop: each Five Whys session should produce one actionable process change, not a project roadmap.

The Five Blames Anti-Pattern

Teams new to Five Whys often degenerate into a blame session, focusing on whoever made the most recent mistake. Ries is direct: most problems are process failures, not people failures. The senior person in the room must redirect the diagnosis toward systems.

The mantra: “If a mistake happens, shame on us for making it so easy to make that mistake.”

This mirrors the psychological phenomenon of fundamental attribution error — the tendency to attribute others’ failures to character rather than context. Blameless postmortem culture, common in SRE and Continuous-Deployment teams, operationalizes this insight.

Implementation Requirements

  • Whole team present: Everyone affected by the problem must attend
  • Narrow scope: Start with specific, small symptom categories — not “fix our deployment process” but “fix this class of deployment failures”
  • Appoint a facilitator: A Five Whys master keeps the session diagnostic rather than adversarial
  • Tie to action: Each session must produce at least one concrete process change

Five Whys integrates naturally with Small-Batch-Production: smaller batch sizes surface failures faster, giving more frequent Five Whys opportunities and compounding the learning rate. This is also the mechanism by which adaptive organizations — as described in Learning-Organization — continuously self-correct.

Sources

  • Ohno, Taiichi (1988). Toyota Production System: Beyond Large-Scale Production. Productivity Press. ISBN: 978-0-915299-14-0.

    • Original articulation of Five Whys as part of TPS; the machine/fuse example appears in Chapter 1.

  • Ries, Eric (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Publishing. ISBN: 978-0-307-88791-7.

    • Chapter 11 (Adapt) — proportional investment principle and Five Blames anti-pattern; IGN Entertainment and IMVU case studies.

  • Argyris, Chris and Donald A. Schön (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley. ISBN: 978-0-201-00116-1.

    • Single-loop vs. double-loop learning: Five Whys creates double-loop learning by addressing root causes rather than just correcting the immediate outcome.

  • Card, A.J. (2017). “The problem with ‘5 whys’.” BMJ Quality & Safety, Vol. 26, No. 8, pp. 671–677. DOI: 10.1136/bmjqs-2016-005849.

    • Empirical critique of Five Whys in healthcare settings; highlights the risk of stopping prematurely or diverging to blame; supports the need for facilitation.

  • Dekker, Sidney (2006). The Field Guide to Understanding Human Error. Ashgate Publishing. ISBN: 978-0-7546-4825-5.

    • Theoretical foundation for why blame-oriented investigation fails and why systemic analysis (the “new view”) produces better outcomes; underpins the Five Blames critique.

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks