The Five Whys
A rapid questioning technique that pushes past surface symptoms to explore the deeper root cause of a problem
8 min · Sakichi Toyoda / Toyota Production System
What is this framework?
The Five Whys is a technique where you ask "why" repeatedly, roughly five times, about a problem until you move from a surface symptom to a deeper underlying cause. Each answer becomes the subject of the next "why", forming a chain that reveals what's really driving the issue.
Developed within the Toyota Production System, the Five Whys was originally used on factory floors to stop workers fixing the same faults repeatedly without ever addressing what caused them. The number five is not fixed — sometimes three whys reveal enough, sometimes it takes seven — but the discipline of not stopping at the first answer is the whole point.
For entrepreneurs, the technique is powerful during customer discovery because customers often describe symptoms, not causes. A student saying "the canteen queue is too long" is a symptom; repeated whys might reveal the real driver is a bottleneck at a single payment counter, not a lack of food stalls.
The technique works best as an exploratory conversation starter rather than a rigid formula. Each 'why' should be answered honestly based on evidence or a plausible hypothesis, and the chain should be checked with real users rather than assumed from an armchair.
What problem does it help solve?
- Move past symptoms to explore what might really be driving a problem
- Avoid designing a solution that only patches a surface-level complaint
- Structure a customer interview or team discussion around root causes
- Reveal underlying constraints, incentives, or process failures
- Generate hypotheses that can then be tested with real customers
The framework
Every part explained
Problem statement
Start with a clear, specific observed problem, not a vague complaint.
Ask: What exactly is going wrong?
Example: The lunch queue at the campus canteen regularly takes over 20 minutes.
Why 1
Ask why the problem happens and answer based on evidence or observation.
Ask: Why does this happen?
Example: Because there is only one working payment counter at peak hours.
Why 2
Ask why that first cause exists.
Ask: Why is that the case?
Example: Because the second counter's card machine is broken.
Why 3
Continue probing the cause behind the cause.
Ask: Why hasn't that been fixed?
Example: Because maintenance requests go through a slow, manual paperwork process.
Why 4 and 5
Keep asking until you reach a cause that feels foundational, structural, or systemic rather than incidental.
Ask: Why does that deeper condition exist?
Example: Because the canteen management has no dedicated budget or staff for quick equipment repairs.
Root cause
The underlying driver the chain points to, which becomes a candidate for the real opportunity.
Ask: What is the most useful root cause to address, given what we found?
Example: Slow repair processes and single points of failure in payment infrastructure, not a shortage of food.
Worked example — CampusEats
The CampusEats team used the Five Whys to dig into student complaints about long lunch queues before designing their app.
Problem
Students say the campus canteen lunch queue takes over 20 minutes.
Why 1
Why? Because only one of two payment counters is working during peak hours.
Why 2
Why? Because the second counter's card machine has been broken for weeks.
Why 3
Why? Because repair requests go through a slow manual approval process.
Why 4
Why? Because the canteen has no dedicated maintenance budget or staff.
Why 5
Why? Because canteen operations are managed part-time alongside other facilities duties.
Root cause (hypothesis)
Structural under-resourcing of canteen operations, not a shortage of food stalls, is driving the queue problem.
Implication for CampusEats
A pre-order and pre-payment app that bypasses the physical counter entirely could address the real bottleneck.
How to use it
- 1Write down the specific problem you have observed or been told about.
- 2Ask 'why does this happen?' and record an honest, evidence-based answer.
- 3Take that answer and ask 'why' again, treating it as the new problem.
- 4Repeat for roughly five rounds, or until you reach a cause that feels foundational.
- 5Check each answer against real evidence or user conversations, not just guesswork.
- 6Identify which point in the chain represents the most useful opportunity to act on.
- 7Validate the root-cause hypothesis with further customer discovery before designing a solution.
Try it yourself
Trace your own problem through five rounds of why.
Five Whys chain
Your work stays on this device. Nothing is uploaded, so use the same browser to come back to it.
When to use it
- When a customer complaint feels like a symptom rather than the real issue
- During early problem discovery, before committing to a solution direction
- When a team keeps proposing quick fixes that don't stick
- As a structured way to run a root-cause discussion in a team meeting
When not to rely on it
This framework does not prove:
- • It explores a possible chain of causality but does not prove it scientifically
- • Different people can produce different chains from the same starting problem
- • It can oversimplify problems that have multiple interacting causes rather than one linear chain
- • Its usefulness depends entirely on the honesty and evidence behind each answer
Common mistakes
- Guessing answers from your own assumptions instead of checking with real users
- Stopping at the first or second why because the answer feels satisfying
- Treating the final answer as proven fact rather than a hypothesis to validate
- Following only one chain of causes when a problem may have several parallel causes
Connections
Related concepts
Related frameworks
Quick check
What is the main limitation of the Five Whys technique?
Remember this
The first answer to 'why' is rarely the real reason — keep asking until you reach something you can actually act on.