ControlStandard.Tools Get a free report

Glossary

The 5 Whys

The 5 Whys is a root-cause technique: you ask "why?" about five times in a row, tracing a problem back from its visible symptom to the underlying cause, so you fix what actually broke instead of the surface effect. Developed at Toyota, it suits single-cause problems and pairs well with a fishbone diagram.

The 5 Whys is a simple root-cause technique: when something goes wrong, you ask "why did that happen?" — then ask "why?" of each answer, roughly five times, until you reach a cause you can actually fix. It moves you from the symptom you noticed to the condition that produced it.

The method was developed by Sakichi Toyoda and became part of the Toyota Production System, where Taiichi Ohno described it as the basis of Toyota's scientific approach: "by repeating why five times, the nature of the problem as well as its solution becomes clear."1

A worked example

  1. The client deadline slipped. Why? The build wasn't approved in time.
  2. Why? The approver only saw it the day it was due.
  3. Why? It sat in their inbox with no deadline attached.
  4. Why? We never set a decision date when we sent it.
  5. Why? Our hand-off has no step for agreeing when a reply is needed.

The surface problem was a late approval. The root cause was a missing step in the hand-off — and that is the thing worth fixing, because it would have caused the same slip again.

When it works, and when it doesn't

The 5 Whys is fast, needs no tools, and is ideal for a single, well-defined problem with one dominant cause. It is weaker when a problem has several causes at once, or when "why?" invites guesswork rather than evidence — chains can drift toward whoever is in the room to blame. For tangled, multi-cause problems, map the possibilities with a fishbone diagram first, then run the 5 Whys down the branch that matters most.

Five is a guide, not a rule: stop when you reach a cause you can change. The 5 Whys is one tool inside a wider root cause analysis, and it earns its keep only when the answer ends in a change that has an owner and a date — otherwise it is just a neat explanation of a problem that comes back anyway.

  1. Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988). See also the American Society for Quality's overview of the 5 Whys. ↩

Frequently asked

Why is it called the 5 Whys if you don't always ask five times?
Five is a rule of thumb, not a fixed count. Sakichi Toyoda found that asking 'why?' roughly five times usually reaches a cause you can change, but the real stopping point is the cause itself: stop sooner if you reach it, keep going if you haven't. The name marks the typical depth, not a quota.
Is the 5 Whys the same as root-cause analysis?
No. Root-cause analysis is the broader practice of finding the underlying cause of a problem, and the 5 Whys is one technique used inside it. The 5 Whys drills into a single cause; a full root-cause analysis may also map many causes with a fishbone diagram and prioritise them before drilling.
When does the 5 Whys not work?
The 5 Whys struggles when a problem has several causes acting at once, or when each 'why?' invites opinion rather than evidence. In those cases the chain can drift toward blaming whoever is in the room. Map the causes with a fishbone diagram first, then run the 5 Whys down the branch that matters most.

Related

Term

Root Cause Analysis (RCA)

Root cause analysis (RCA) is a structured way to find the underlying cause of a problem — not just its symptoms — so a fix stops it coming back. It uses tools like the 5 Whys, fishbone diagrams and Pareto analysis to move from "what happened" to "why", and ends in a change with a named owner and a date.

 Term

Fishbone Diagram (Ishikawa)

A fishbone diagram — also called an Ishikawa or cause-and-effect diagram — is a visual tool that sorts the possible causes of a problem into categories, so a team can see every contributing factor at once instead of fixing the first thing they notice. Created by Kaoru Ishikawa, it is a staple of root-cause analysis.

 Term

After-Action Review (AAR)

An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.

← Back to the glossary