What the 5 Whys is
The 5 Whys is a root-cause technique developed at Toyota: when something goes wrong, you ask "why?" and then ask "why?" of the answer, repeating until you reach a cause that, if removed, would stop the problem recurring. "Five" is a rule of thumb, not a law — sometimes it's three, sometimes seven — but the number is a reminder to keep going past the first plausible answer, which is almost always a symptom rather than a cause.
A worked example
Symptom: the monthly report went out late.
- Why? The data arrived late from finance.
- Why? Finance re-keys it by hand every month.
- Why? The two systems don't exchange data.
- Why? The integration was never built.
- Why? No one owns it.
Stop at the first "why" and you chase finance every month forever. Follow the chain and the fix is structural and permanent: give the integration an owner. The depth is the whole point.
How to run one well
- State the problem precisely — a vague symptom produces a vague chain.
- Base each answer on fact, not opinion. "Why do we think…" is a guess; go and look.
- Stay on one chain. If a "why" has two real causes, split into two chains rather than blurring them.
- Stop at a cause you can act on — a root cause is one within your control to remove.
- Test the logic backwards: read the chain bottom-up with "therefore" — if it holds, your causality is sound.
Traps that give a wrong answer
- Stopping too early — the first answer is comfortable and usually wrong.
- Jumping to a solution — "why? because we need a new tool" smuggles an answer into the diagnosis.
- Single-track blindness — real problems often have more than one root; one chain can miss a parallel cause.
When five isn't enough
The 5 Whys is a linear tool — brilliant for a problem with one dominant cause, weaker when several causes combine. When the problem is tangled, reach for root cause analysis with a fishbone (Ishikawa) diagram, which maps causes across several categories at once. The 5 Whys is often how you dig within each branch of a fishbone.
Describe a process. Get the whole analysis.
LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.
Build your first map free →Keep learning in the Garage
Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.
Common questions
What is the 5 Whys technique?
A root-cause method from Toyota: when something goes wrong, you ask 'why?' and then ask 'why?' of each answer, repeating until you reach a cause that, if removed, stops the problem recurring. 'Five' is a rule of thumb to keep going past the first, symptom-level answer.
Does it have to be exactly five whys?
No. Five is a reminder, not a law — sometimes three is enough, sometimes you need seven. You stop when you reach a root cause you can actually act on to remove the problem, not at a fixed count.
What's a common mistake with the 5 Whys?
Stopping at 'human error'. That's a symptom, not a root cause — keep asking why the mistake was possible and why nothing caught it. Other traps are stopping too early, smuggling a solution into an answer, and following only one chain when the problem has several causes.
When should I use a fishbone diagram instead?
When a problem has several causes that combine rather than one dominant cause. The 5 Whys is linear; a fishbone (Ishikawa) diagram maps causes across categories at once. Often you use the 5 Whys to dig within each branch of a fishbone.
Related guides: Root cause analysis · The 8 wastes (TIMWOODS) · Kaizen