Knowledge Base · Seeing Problems
When should I stop asking "why?" in a 5 Whys?
Stop when you reach the true root cause: an underlying, often systemic, cause that you can fix so the problem stops recurring. Five is a guide, not a rule. If your chain still ends in blaming a person or a single department, you have probably stopped too soon and are still looking at a symptom.
The book gives no fixed finishing number. It says you ask why repeatedly, usually about five times, and its practice instruction is direct: do not stop until you feel you have hit the true root cause. The goal of the exercise is that landing point, not the count.
The worked example shows what deep enough looks like. Late delivery led to a late shipment, a warehouse behind on packing, and a shortage of packing materials. None of those was the stopping point. The chain ended at a training gap in new procurement software, a systemic problem. The test the book applies is prevention: fixing that cause would prevent hundreds of future delays.
- Keep going while each answer is still a symptom of something underneath it.
- Treat an answer that blames a team or a person as a sign to ask why once more.
- Stop when the cause is specific, within your power to change, and fixing it would stop the problem coming back.
You might reach that point in three questions on a simple problem, or need more than five on a tangled one. Judge the depth of the cause, not the number of questions.
Run a 5 Whys in ClarionEX (free in Lite)
Related questions
- How do I run a 5 Whys analysis?
- What's the difference between a symptom and a root cause?
- What is root cause analysis?
Source: Continuous Improvement in the Workplace, Ch. 3 (Learning to See).