The 5 Whys: root-cause analysis that actually works
The cheapest root-cause tool there is: a worked example, the rules that keep it honest, and the trap that ruins it.
Get the free PDF
One page, print-ready, free to share. No signup needed.
The 5 Whys is the cheapest root-cause tool there is: no software, no workshop, just the discipline of asking why until you hit something fixable. The trick is knowing what counts as a stopping point.
A worked chain
The dashboard shows wrong revenue. Ask why until you hit process:
- WHY 1: Numbers wrong? Duplicate rows in the sales table.
- WHY 2: Duplicates? The import job ran twice.
- WHY 3: Ran twice? A retry fired after a timeout.
- WHY 4: No guard? The job is not idempotent.
- WHY 5: Why not? There is no standard for pipeline jobs.
Five levels down, "the dashboard is wrong" became "we need a pipeline standard". That is the tool working: the symptom was data, the root cause was process.
The rules
- Stop at process, never at a person. "Human error" is a dead end.
- Verify each hop. Check the data before asking the next why; a guessed answer poisons the whole chain.
- Branch if needed. Two plausible causes? Follow both chains.
- Five is a guide. Stop when the answer is something you can fix.
The trap: stopping at a person
"Marc forgot to check" is where the analysis starts, not where it ends. "Be more careful" has never fixed anything.
Keep asking: why COULD he forget? No checklist, no alert, no validation step. The good ending is a system change that survives Marc's vacation.
Blameless analysis is not about being nice. Blame just ends the chain five whys too early.
5 Whys or fishbone?
| 5 Whys | Fishbone |
|---|---|
| One symptom, one chain | Messy multi-cause problems |
| Minutes, in any meeting | A workshop with the team |
| Linear cause suspected | Buckets: people, process, tools |
| Depth over coverage | Coverage over depth |
Chain for depth, fishbone for breadth. Most incidents deserve the chain first; reach for the fishbone when the chain keeps branching.
Frequently asked questions
- Does it have to be exactly five whys?
- No. Five is a guide, not a rule. Stop when the answer is something you can actually fix at the process level; sometimes that is three whys, sometimes seven.
- What is the difference between 5 Whys and a fishbone diagram?
- 5 Whys digs one chain deep from a single symptom and takes minutes. A fishbone (Ishikawa) diagram maps many possible causes across categories like people, process and tools, and works best as a team workshop. Chain for depth, fishbone for breadth.
- How do I run a 5 Whys session?
- Start from one precise symptom, ask why it happened, verify each answer with data before asking the next why, branch if two causes are both plausible, and stop at a process-level cause with an owner and an action.
- When does the 5 Whys method fail?
- When answers are guesses instead of verified facts, when the chain stops at a person instead of a process, or when the problem genuinely has many interacting causes, which is fishbone territory.
Get the free PDF
One page, print-ready, free to share. No signup needed.