5 Why: Examples and a Free Template
- timothyferguson1
- Jun 13
- 4 min read
June 13, 2026
The 5 Whys is the simplest root cause analysis tool there is — you just keep asking “why?” — and that simplicity is exactly why it’s so easy to do badly. This post shows the method in action with worked examples, explains how to know when you’ve actually reached a root cause, and gives you a free template to run your own.
Want the full RCA process around it? See our Complete Guide to Root Cause Analysis. https://www.fsquaredconsultinggroup.com/post/root-cause-analysis-guide
What is the 5 Whys method?
The 5 Whys is a technique for getting from a symptom to its root cause by repeatedly asking “why does that happen?” — roughly five times — until the answer points to a systemic, fixable factor rather than another surface symptom. It was developed within the Toyota Production System and is a staple of Lean and quality work.
“Five” is a rule of thumb, not a law. Sometimes you reach the root in three whys; sometimes it takes seven. The number isn’t the point — reaching a cause you can actually change is.
How to run a 5 Whys in 4 steps
1. Start with a clear problem statement. Vague problem in, vague root cause out. How to write a problem statement. https://www.fsquaredconsultinggroup.com/post/how-to-write-a-problem-statement
2. Ask “why does that happen?” Write a fact-based answer.
3. Ask “why?” of that answer — and repeat. Each answer becomes the subject of the next why.
4. Stop at a systemic cause, then capture corrective actions with an owner and date.
Worked example 1 — a process problem
Problem: ~6% of Line 3 cartons ship with unsealed top flaps since the May changeover.
1. Why? The sealer isn’t reaching bonding temperature on some cycles.
2. Why? It isn’t given enough warm-up time after a changeover.
3. Why? The changeover is done from memory — there’s no standard that includes warm-up.
4. Why? The changeover procedure was never written down when the line was reconfigured.
5. Why? No one owns maintaining standard work for Line 3.
Root cause: No ownership of standard work for the line (a systemic/management factor) — not “the operator rushed.” Corrective actions: assign standard-work ownership; write a changeover standard that includes sealer warm-up; add a first-article check.
Notice how the early answers are events and the later ones become system factors. That shift is the signal you’re nearing a root cause.
Worked example 2 — a service/admin problem
Problem: 12% of customer invoices went out late last month.
1. Why? Invoices waited on approvals.
2. Why? Approvers didn’t know items were waiting.
3. Why? There’s no notification when an invoice is queued for approval.
4. Why? The workflow was set up manually and never automated.
5. Why? No one is accountable for the invoicing workflow end to end.
Root cause: Unclear ownership of the invoicing process. The fix isn’t “remind approvers” — it’s assigning ownership and adding a notification step.
When have you reached a root cause?
Stop asking “why” when the answer points to a process, standard, system, policy, or design factor you can change — not another event or, worse, a person. Two checks help:
• The systemic test: Can you fix this by changing a process or standard? If yes, you’re likely at a root cause. If the answer is “tell someone to try harder,” keep going.
• The reverse (“therefore”) test: Read the chain bottom-up: “No one owns standard work, therefore the procedure was never written, therefore…” If each step logically causes the one above, your chain holds.
Common 5 Whys mistakes
• Stopping at human error. “The operator made a mistake” is where blame ends analysis. Ask why the system allowed the error.
• Jumping straight to 5 Whys. Without exploring first, you can tunnel down one path and miss the real cause on another. Brainstorm with a fishbone first. https://www.fsquaredconsultinggroup.com/post/how-to-make-a-fishbone-ishikawa-diagram-step-by-step
• Confusing a solution with a cause. “Because we don’t have a checklist” is borderline — the cause is why there’s no checklist.
• Single-track thinking on complex problems. Real issues branch. Use branching 5 Whys, or the three-legged approach (Occurrence / Detection / Systemic) for serious quality and safety cases.
Linear, branching, or three-legged?
• Linear — one chain; fastest for straightforward problems.
• Branching — when a “why” has more than one valid answer, split into branches and pursue each.
• Three-legged — run three parallel 5 Whys: Occurrence (why it happened), Detection (why it escaped/wasn’t caught), and Systemic (why the system allowed it). This is the gold standard for incidents, because it fixes the escape point and the system, not just the event.
Run it free: The F Squared 5 Whys tool supports linear, branching, and three-legged modes, lets you import a cause straight from a fishbone, and (on Pro) uses AI to flag whether you’ve reached a true root cause and to draft countermeasures. Try it free →
Prefer paper? The free RCA Starter Kit includes a printable 5 Whys worksheet.
Frequently asked questions
Why is it called the “5 Whys”?
Because you typically ask “why?” about five times to get from a symptom to its root cause. Five is a guideline — use as many whys as it takes to reach a systemic, fixable cause.
How many times should I ask why?
Until the answer points to a process, standard, or design factor you can change rather than another symptom or a person. That might be three whys or seven.
What’s the difference between 5 Whys and a fishbone?
A fishbone explores many possible causes (breadth); 5 Whys drills one chosen cause to its root (depth). They work best together.
https://www.fsquaredconsultinggroup.com/post/fishbone-vs-5-whys-vs-a3-when-to-use-each
Can a 5 Whys have more than one root cause?
Yes. Complex problems often branch into multiple causes — use branching or three-legged 5 Whys to capture them rather than forcing a single chain.
When should I not use 5 Whys?
When you don’t yet have a candidate cause (start with a fishbone), or for highly complex, multi-factor failures that need more rigorous tools. For most everyday recurring problems, 5 Whys is ideal.
Comments