Design the fix to prevent recurrence, not just to recover from this instance
Ensure the root-cause fix eliminates the cause permanently, not just this occurrence.
Why it works
The goal of root cause analysis is durable prevention, not remediation of the current instance. A fix that addresses the symptom allows the root cause to produce the same failure again; a fix that addresses the root cause removes the mechanism of failure entirely. Toyota’s continuous improvement philosophy treats any recurrence of a previously analyzed problem as evidence that the root was not actually reached — an incentive structure that drives genuine depth.
How to do it
- For the identified root cause, design a countermeasure that makes the root cause impossible or significantly less likely — not just harder to ignore.
- Ask: "If this root cause were genuinely eliminated, would the chain of events above it be impossible?"
- Check that the fix does not just move the problem downstream.
- Set a review date to confirm that the problem has not recurred.
Evidence
Prevention-oriented root cause analysis is the standard in Toyota’s kaizen and in healthcare patient safety — the distinction between "fix this case" and "prevent this class of error" is foundational to both. The Institute of Medicine’s To Err Is Human argued the same point at a systems level: durable safety gains come from redesigning the conditions that generate a class of failures, not from resolving each incident after the fact. (anecdotal)
Some root causes cannot be fully eliminated — only the probability of the failure chain can be reduced. "Zero recurrence" is an aspiration; the realistic standard is measurable reduction.
Sources
- Ohno (1988), Toyota Production System — countermeasure design as the payoff of root cause analysis
- Kohn, L.T., Corrigan, J.M., & Donaldson, M.S. (Eds.) (2000). To Err Is Human: Building a Safer Health System. Institute of Medicine / National Academies Press, Washington, DC.
Common mistake
Designing a countermeasure that increases vigilance or retraining rather than changing the system structure — vigilance degrades over time; structural fixes do not.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Five Whys
- State the problem precisely before asking the first why
A vague problem statement produces vague root causes — be specific about what happened.
- Follow the causal chain until you reach a changeable cause
Keep asking "why?" until you reach something you can actually fix.
- Branch the chain when you find multiple causes
When a "why" has two or more true answers, follow each branch separately.
- Distinguish human error from system conditions
When a person is the proximate cause, ask why the system allowed the error to occur.
- Verify the root cause by tracing back up the chain
After reaching a root, work back up: does each "because" in the chain make logical sense?