Home › The Garage › The 5 Whys
Lean

The 5 Whys

Most fixes treat the symptom and the problem comes back. The 5 Whys is the simplest tool in Lean for getting past the symptom to the cause that, once removed, actually ends it.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What the 5 Whys is
  2. A worked example
  3. How to run one well
  4. Traps that give a wrong answer
  5. When five isn't enough
  6. Common questions
Symptom: the report went out late. Why? The data arrived late from finance. Why? They re-key it by hand each month. Why? The two systems don't talk to each other. Why? No one owns the integration. ← root cause Fixing the symptom (chase finance) solves nothing. Fixing the root (own the integration) ends it.
Each "why" steps one level deeper, from the symptom you see to the cause you can remove.

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.

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

  1. State the problem precisely — a vague symptom produces a vague chain.
  2. Base each answer on fact, not opinion. "Why do we think…" is a guess; go and look.
  3. Stay on one chain. If a "why" has two real causes, split into two chains rather than blurring them.
  4. Stop at a cause you can act on — a root cause is one within your control to remove.
  5. Test the logic backwards: read the chain bottom-up with "therefore" — if it holds, your causality is sound.

Traps that give a wrong answer

The "human error" dead end
If a chain ends at "someone made a mistake," keep going — that's a symptom, not a root cause. Why was the mistake possible? Why did nothing catch it? Blaming a person ends the inquiry exactly where the useful part begins: the system that let the error through.

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