5 Whys: Asking "Why?" Five Times to Reach the Root Cause
Updated: 5 days ago
Before rushing to a solution, it’s worth understanding what really happened. The 5 Whys method offers a simple yet powerful way to uncover the root cause of a problem, instead of just treating the symptoms.
How does it work?
Start with the question: Why did the problem occur?
Dig into the answer, and ask again: Why did that happen?
Repeat the process until you reach the root cause.
Sometimes three questions are enough, sometimes it takes five - the goal is to go deep and avoid staying on the surface.
Why is it important?
Identifies the actual cause of the problem.
Prevents recurrence by treating the cause, not just the effect.
Drives insight-based decision making.
Improves processes and performance in a focused, effective way.
Where does it work best?
Work process flaws or inefficiencies.
Service or customer experience issues.
Investigating incidents or system failures.
Analyzing performance or communication gaps.
A worked example
Problem: A customer's order shipped three days late.
Why did the order ship late? The item wasn't in stock when the order came in.
Why wasn't it in stock? The reorder point hadn't been triggered.
Why hadn't it been triggered? The inventory system was still using last year's demand forecast.
Why was it using last year's forecast? Nobody owned the task of updating seasonal forecasts.
Why did nobody own it? There was no assigned owner for forecast maintenance after the last reorg.
The real fix isn't rushing the next shipment - it's assigning ownership of forecast updates. That's the difference between a Band-Aid and a fix that sticks.
Key Advantages:
Simple to implement - requires no complex tools.
Strengthens accountability and critical thinking.
Fosters an objective, non-judgmental dialogue.
Common mistakes to avoid
Stopping too early. Three whys can feel like enough, but the real root cause often sits one or two questions further down.
Blaming a person instead of a process. If an answer is "someone made a mistake," ask why the process allowed that mistake to happen and go uncaught.
Guessing instead of checking. Each "why" should be based on what actually happened, not on assumptions about what probably happened.
Treating it as a solo exercise. The people involved in the process usually know the real answers - involve them instead of guessing on their behalf.
Summary The 5 Whys isn’t just a method - it’s a mindset. Sometimes, a single question asked five times can prevent five future mistakes.
Want to put this into practice with your team? The Lean Management Kit includes ready-to-use templates for 5 Whys, Fishbone, and Gemba Walk analysis.
What is the 5 Whys technique?
The 5 Whys is a root cause analysis method where you ask "why" repeatedly - typically five times - until you move past symptoms and reach the underlying cause of a problem.
Does the 5 Whys always take exactly five questions?
No. Five is a guideline, not a rule. Some problems reveal their root cause in three questions, others take seven. Keep asking until the answer points to a process or system issue you can actually fix.
What's the difference between the 5 Whys and a Fishbone diagram?
The 5 Whys drills down one causal chain at a time, while a Fishbone diagram maps out many possible causes across categories at once. They work well together: use a Fishbone to generate candidate causes, then apply the 5 Whys to the most likely ones.
What's a common mistake when using the 5 Whys?
Stopping too early, or landing on "human error" as the final answer. Human error is usually a symptom of a process that allowed the error to happen and go uncaught.
Who should be involved in a 5 Whys session?
The people closest to the problem. They know what actually happened, which keeps the analysis grounded in fact rather than assumption.
Can the 5 Whys be used outside of manufacturing?
Yes. It works for service issues, customer complaints, missed deadlines, communication breakdowns, and any problem where the first explanation is probably not the real one.
Comments