Five Whys

Purpose

The Five Whys is a root-cause analysis technique that peels away successive layers of symptoms by repeatedly asking “Why?”. Originally from the Toyota Production System, it helps teams stop treating surface-level symptoms and instead identify — and fix — the underlying cause of a problem.

At a glance

• Group size: 3–10
• Duration: 20 minutes
• Difficulty: Beginner
• Facilitation style: Guided questioning
• Setting: In-person or virtual

How to run

1. State the problem (2 min). Write the problem statement clearly. Be specific: “Customer churn increased 15% last quarter.”
2. Ask Why #1 (3 min). Why did this happen? Capture all answers.
3. Ask Why #2 (3 min). For each answer, ask why again. Begin narrowing to the most likely causal chain.
4. Continue asking Why (9 min). Repeat for Why #3, #4, and #5. The number 5 is a guideline — stop when the group reaches a cause they can act on.
5. Identify the root cause and actions (3 min). Agree on the root cause. Define one or two corrective actions.

Materials needed

• Whiteboard or shared document
• Markers
• Problem statement prepared in advance

Pitfalls & common mistakes

• Stopping at symptoms. “We didn’t have enough staff” is a symptom. Keep asking: Why didn’t we have enough staff?
• Branching too wide. If multiple causal chains emerge, follow the most likely one first. You can explore others later.
• Blame rather than systems. Direct ‘why’ at processes and systems, not individuals. Never let it become “Why did you...”
• Exactly five. Five is a rule of thumb. Sometimes three is enough; sometimes seven is needed.

Inclusion & accessibility

• Record each ‘why’ level visually so everyone can follow the chain.
• Encourage quieter team members to propose their own ‘why’ answers.
• Ensure psychological safety — the exercise must feel blame-free.

Variations

• Fishbone + Five Whys: Use a fishbone (Ishikawa) diagram to explore multiple causal branches, then Five Whys on each.
• Five Whys for success: Ask “Why did this succeed?” to identify replicable conditions.
• Written Five Whys: Each participant writes their own chain, then the group compares.

When NOT to use this

• For complex, multi-causal problems where a single root cause doesn’t exist — use systems thinking or causal loop diagrams.
• When the problem is well-understood and the team needs solutions, not more analysis.

Source & further reading

• Ohno, T. (1988). *Toyota Production System: Beyond Large-Scale Production.* Productivity Press.
• Serrat, O. (2009). The Five Whys Technique. *Asian Development Bank Knowledge Solutions.*