Five Whys
Ask "why?" five times and you'll usually dig past the symptoms to the real cause of a problem, which is the one worth fixing.
When to Use ItWhenever a problem keeps coming back and you want to fix it for good. The Five Whys finds the root cause by asking "why?" over and over, peeling away layers of symptoms like the skin of an onion until you reach the core.
Here's how it plays out with something ordinary:
ProblemYour houseplant is dying.
- Why?- The leaves are turning yellow.
- Why?- The plant is getting too much water.
- Why?- The watering schedule doesn't suit the plant's needs.
- Why?- The care instructions weren't followed carefully.
- Why?- The instructions were lost and never replaced.
Root causeThe care instructions went missing, so the plant was watered the wrong way.
The yellow leaves were a symptom, and so was the overwatering. Fix either one on its own and you might be back here in a month. Fix the root cause, by finding proper care instructions and adjusting the watering schedule, and the problem stays solved.
It's a simple, practical tool, and a handy reminder that the problem you can see is often just the tip of the iceberg. When a problem has several tangled causes rather than one neat chain, pair it with an Ishikawa diagram so you can follow more than one branch.
The Five Whys is loved for its simplicity, and that simplicity is exactly what its critics, including some from inside Toyota, take aim at:
Real problems rarely have one rootThe method walks down a single chain of causes, so it tends to land on one neat "root cause". In complex settings like hospitals, failures usually come from several factors interacting. Alan Card, writing in BMJ Quality & Safety in 2017, argued that this makes the technique a poor fit for serious incident analysis in health care, because it oversimplifies how things go wrong. Thinking in terms of the Cynefin framework, it suits simple, ordered problems far better than complex ones.
Five is an arbitrary numberThe true cause might be two steps away or ten. A fixed count invites people to stop when they reach the fifth answer rather than when they reach something they can actually fix.
You only find what you already knowTeruyuki Minoura, a former Toyota managing director, criticised the method for letting investigators stop at symptoms, for giving little help in choosing the right answer to each "why", and for its inability to surface causes the team isn't already aware of. Different people can reach different root causes for the same problem, so the results aren't repeatable. That leaves plenty of room for confirmation bias to steer the chain towards whatever people expected.
The textbook example doesn't hold upCard pointed out that a much-repeated success story, usually told about deteriorating stone at the Washington Monument, actually concerned the Lincoln Memorial, and that the real causal chain was messier than the tidy version. The fix that came out of it, changing the lighting schedule, also had side effects visitors disliked, and was reversed.
Better tools exist for tangled problemsCritics suggest methods that map many causes at once, such as the Ishikawa (fishbone) diagram, or more formal root cause analysis frameworks.
In fairness, even Card sees value in the Five Whys as a teaching tool, a way to get people digging past the first answer. Used as a quick habit of curiosity it works well; used as the whole analysis of a complex failure, it can give false confidence.
Resources
The Five Whys is a problem-solving technique developed by Sakichi Toyoda, founder of Toyota Industries, and later built into the Toyota Production System (TPS) (Liker, 2004). The method is disarmingly simple: ask "why" about a problem, then ask "why" about the answer, and keep going, five times or until you hit a deeper underlying cause. Its power lies in refusing to stop at the first plausible explanation.
The technique links to several other principles and fields:
Root Cause Analysis (RCA)The Five Whys is a form of root cause analysis, the systematic search for the underlying causes of a problem rather than its symptoms (Latino & Latino, 2006). RCA is central to continuous improvement methodologies such as Lean and Six Sigma.
Causal Loop DiagramsThese diagrams map the interrelationships among variables in a system. Used together with the Five Whys, they help trace the chains of cause and effect that drive a problem (Sterman, 2000).
Plan-Do-Check-Act (PDCA) CycleThe Five Whys often appears inside the PDCA cycle, a continuous improvement loop of planning, implementing, evaluating and adjusting actions to fix problems and improve processes (Deming, 1986).
Ishikawa (Fishbone) Diagram: Ishikawa diagrams lay out and categorise the potential causes of a problem. Pairing them with the Five Whys gives a structured way to trace each branch down to its root (Ishikawa, 1982).
Cognitive biasesRepeatedly asking "why" can help counter biases such as confirmation bias, by pushing people to consider alternative explanations and look for underlying factors they might otherwise miss (Kahneman, 2011).
Used alongside these methods, the Five Whys helps experts find and fix the real causes of problems, supporting continuous improvement and better decisions.
References
- Deming, W. E. (1986). Out of the Crisis. Cambridge, MA: MIT Press.
- Ishikawa, K. (1982). Guide to Quality Control. Tokyo, Japan: Asian Productivity Organization.
- Kahneman, D. (2011). Thinking, Fast and Slow. New York, NY: Farrar, Straus and Giroux.
- Latino, R. J., & Latino, K. C. (2006). Root Cause Analysis: Improving Performance for Bottom-Line Results. Boca Raton, FL: CRC Press.
- Liker, J. K. (2004). The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer. New York, NY: McGraw-Hill.
- Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Boston, MA: Irwin/McGraw-Hill.