Something breaks. You fix the symptom. It breaks again. You were solving the wrong problem. The Five Whys is a technique for drilling past symptoms to the root cause - the thing that, if fixed, prevents the whole chain.
Every symptom has a cause. Every cause has a cause.
Ask "why" until the answer is something you can change.
Example: The Late Deployment
The fix: Not "test faster" - but "add spec sign-off to the process."
How To Do It
Start With The Problem
State the problem clearly and specifically. "The deployment was late" is better than "things are slow." Precision matters.
Ask Why - Literally
For each answer, ask "Why did that happen?" Don't accept the first response. Push for the mechanism. How did that cause this?
Five Is A Guideline, Not A Rule
Sometimes you hit root cause in three. Sometimes it takes seven. Stop when you reach something actionable - a process, a policy, a decision that can be changed.
Avoid Blame, Seek Systems
"Because John screwed up" is not a root cause. Why was John able to screw up? What system allowed the error? Root causes live in structures, not individuals.
Common Mistakes
Stopping At Symptoms
"Why was it late? Because we didn't have time." That's not a cause - it's a restatement. Push harder. Why didn't you have time?
Going Too Abstract
"Because the company doesn't value quality." Too vague to fix. What specific decision or process reflects that? Stay concrete.
Single Threading
Most problems have multiple causes. The Five Whys traces one chain - but there may be others. Run it multiple times from different starting points.
Skipping Verification
You found "the root cause." Are you sure? Test it. If you fix this, does the problem actually go away? Hypotheses need validation.
Best Applications
Post-Incident Analysis
Something went wrong. Before fixing, understand why. The Five Whys turns incidents into systemic improvements.
Recurring Problems
If you've "fixed" this before and it came back, you fixed a symptom. Go deeper.
Before Big Decisions
You think you know the problem. Question your framing. Is this the real problem, or a symptom of something else?
When You're Stuck
Progress stalled. Why? Keep asking. The block is rarely what it appears to be.
The technique is simple. The discipline is hard. You have to resist the urge to stop at the first plausible answer. The first answer feels true - but it's usually just the most visible symptom.
Toyota invented this. They used it to build the most reliable manufacturing process in the world. Simplicity, relentlessly applied.
Keep asking why. The root cause is waiting.