For consultants getting past the first answer
5 Whys Template With Worked Examples
A 5 whys worksheet for tracing a client's problem to a root cause they can fix, with evidence for every why and three worked examples.
How it works
What is the 5 whys, and when do you stop asking?
The 5 whys is a root cause method: ask why a problem happens, then ask why about each answer in turn, until you reach a cause you can fix. The aim, says the Lean Enterprise Institute, is to get beyond the obvious symptoms1 to the root cause. Start from a precise problem: what happens, where, since when and how big, against a target. Without that, warns Michael Ballé in the institute's Gemba Coach column, the whys can lead you just about anywhere2.
Back every answer with evidence (data, a document or something you saw), and treat a belief as a lead to check. Include the people who do the work: the Institute for Healthcare Improvement (IHI) notes that people who see different parts of a system may answer differently3. RCA2, a root cause guide from the National Patient Safety Foundation, says to avoid vague words such as "poor" and "inadequate"4 and describe what actually happened. When an answer names a person, ask why the process let it happen.
Stop when the answer is a cause the client can act on and control, and fixing it would keep the problem from coming back. If one answer has two causes, follow each in its own chain: IHI also notes there may be multiple root causes3. Each root cause then gets a countermeasure, one owner, a date and a measure. Prefer a process change, such as a form or a system setting: RCA2 ranks training and new policies among the weaker actions4, because they rely on people remembering.
How it works
How to run a 5 whys analysis
Download it or open it in River
Download the worksheet and examples free, or open them in River. If you paste the problem, River drafts a first chain to check.
State the problem precisely
Answer the worksheet's four questions, then write the problem in one sentence, with today's number against the target. Name no cause and no person.
Ask why, with evidence
Write each answer with how you know it. Branch when an answer has two causes, and stop at a cause the client controls.
Fix it and check
Give each root cause a process change, one owner and a date, then track the number from your problem statement.
5 whys · Quotes take six days to go out (example)
Promise: two days · evidence on every why
- 1Quotes wait four of the six days for engineeringHow we know: time stamps on 120 quotes
- 2Every quote goes to engineering, even standard modelsHow we know: the quoting procedure; 70% are standard
- 3Sales can't tell which configurations are standardHow we know: five of six sales reps; the quote screen
- 4Root cause: the standard list is engineering-onlyFix: put the list in the quote screen · sales operations
What you'll get
Five whys with evidence, a stop rule, branching and worked examples
- A problem statement test, so the chain starts from a fact
- Five whys, each with evidence, plus a rule for when to stop
- Three worked client examples and three broken chains fixed
Before and after
Your problem in. A first chain to check out.
Repair visits needing a second trip are up to 18% from 8% last year. Techs say they often don't have the part. Ops manager thinks the new models are the issue. Not sure who updates the van stock.
Problem: 18% of repair visits in [period] needed a second trip, against 8% last year. Why 1: The technician didn't have the part. How we know: what technicians report, per your notes. Checked: not yet. Why 2: Why didn't the technician have the part? Possible answers to check: the van stock list misses parts for the new models (the ops manager's view, per your notes), or used parts aren't restocked. To confirm with the client: who updates the van stock list, and when it last changed.
The chain stops where your evidence stops. Possible answers are marked to check, never written as facts.
What lands in your doc
What's inside the 5 whys template
- The problem, stated precisely
Four questions (what, where, since when, how big), plus a weak and a strong example to check yours against. - The why chain
Five rows of why, each with how you know the answer and whether it's checked, then a read-back test. - The stop rule and a mistakes check
Three checks for when to stop, and six for the common mistakes, from blame to a solution in disguise. - Branching for two causes
Two branch tables, so a second cause gets its own chain instead of being dropped. - Countermeasures and what to confirm
A fix, owner, due date and measure for each root cause, and a list of answers still to check. - 5 Whys Examples
A separate document: three worked client examples, plus three broken chains and how to fix them.
Questions consultants ask
Common questions
What is the 5 whys technique?
The 5 whys technique finds a problem's root cause by asking why it happened, then asking why again of each answer. The Institute for Healthcare Improvement attributes it to Taiichi Ohno3 of Toyota. In Ohno's example1, five whys lead from a stopped machine to a pump with no strainer, which let metal scraps in. Replacing the fuse or pump would have let it happen again.
Do you always ask why exactly five times?
No. The Lean Enterprise Institute says the specific number five is not the point1. Keep asking until the answer is a cause rather than a symptom, the client can change it, and the next why would lead outside their control. Some chains get there in three whys, and others need six or seven.
What are the most common 5 whys mistakes?
Watch for three: blaming a person, stopping at a symptom and building on a guess. The RCA2 root cause guide calls individual performance a symptom of larger systems-based issues4, so ask why the process allowed the error. "Deliveries are late" restates the problem rather than explaining it. And one unchecked answer can send four more whys the wrong way.
What if the problem has more than one cause?
Branch. When one answer has two causes, such as laptops that arrived late and accounts that weren't set up, give each cause its own chain. In the template's worked example, fixing only the late laptops would have solved 4 of the 11 cases. If many causes appear at once, start with the fishbone in the root cause analysis template.
When should you use the 5 whys?
Use the 5 whys when a process misses its standard, such as quotes promised in two days that take six. The Lean Enterprise Institute recommends it for these gap-from-standard problems1. For a broad question, such as why profit fell, start with an issue tree. If you don't know where the process breaks, map its steps in a SIPOC diagram and check each step's numbers.
Is this 5 whys template free?
Yes. Download both Word documents, the worksheet and the worked examples, free with no signup. Edit with AI opens them in a free River workspace instead. There you can fill in the worksheet yourself, or paste the problem for a first chain to check.
What does Edit with AI do?
Edit with AI opens the worksheet and the worked examples in River. If you've pasted the problem and your notes, River fills in the problem statement and the whys they support, marking opinions as unchecked. Where your notes stop, it suggests answers to check, and missing facts stay in brackets. Under River's privacy policy, nothing you paste is used to train AI models.
Your next step