Five Whys
What are the Five Whys?
The Five Whys is a root cause analysis method from Toyota in which a team keeps asking why a problem happened, using each answer as the next question, until it finds a cause it can fix. Five is a guideline, not a rule.
Updated November 2026 · 3 min read
The Five Whys is a root cause analysis technique in which a team asks "why?" repeatedly, starting from a problem, until it reaches an underlying cause that can be fixed to stop the problem from recurring. Each answer becomes the subject of the next question. Five is a rule of thumb rather than a requirement: some problems reach a useful cause in three steps, others need more.
The technique comes from Toyota. It is associated with Sakichi Toyoda, the inventor whose loom company Toyota grew out of, and was built into the Toyota Production System by Taiichi Ohno, who described it as the basis of Toyota's scientific approach to problems. It spread through lean manufacturing and later into software, operations and product teams, where it is often used in incident reviews and retrospectives.
How to run a five whys analysis
- Assemble the right people. Include those closest to the problem and the process involved. Diverse views reduce guesswork.
- Write a specific problem statement. State what happened, where and when, with facts. "Checkout failed for 18% of users on Tuesday" is better than "checkout is broken."
- Ask why the problem occurred. Record an answer based on evidence, not opinion.
- Ask why again, of that answer. Keep going, checking each answer against data or logs where possible.
- Stop at an actionable cause. Stop when the answer points to a process, system or decision that the team can change, and that would prevent recurrence.
- Define countermeasures. Agree on actions, owners and dates, and check later that they worked.
Five whys example
Consider a hypothetical subscription software company where 340 customers were charged twice in one billing run.
| Question | Answer |
|---|---|
| Why were customers charged twice? | The billing job ran twice for the same billing period. |
| Why did the job run twice? | The scheduler retried it after a timeout, although the first run had completed. |
| Why did the retry not detect the completed run? | The job does not check whether invoices for the period already exist. |
| Why is there no such check? | The job was written when billing ran manually once a month, and the risk of double runs was not considered when it was automated. |
| Why was the risk not considered? | The team's change review checklist does not cover retry behavior for jobs that move money. |
The countermeasures address several levels: refund the 340 customers, make the billing job safe to rerun by checking for existing invoices, and add retry behavior to the change review checklist for payment-related jobs. Stopping at the second why would have led only to a longer timeout, leaving the real weakness in place.
Five whys vs. other root cause methods
- Fishbone diagrams map many possible causes across categories such as people, process and tools. They suit problems with several contributing factors, and teams often run Five Whys on the most likely branches.
- Fault tree analysis uses formal logic to model how combinations of failures cause an event, common in safety-critical engineering.
- Blameless postmortems provide the setting for analysis after incidents. Five Whys is one technique used within them.
Limitations of the five whys
The Five Whys follows a single chain, but many problems have several causes that combine. Results depend on the knowledge of the people in the room, and different groups can reach different root causes for the same problem. The method also has no built-in way to verify answers. Use evidence at each step, and branch the analysis when a "why" has more than one valid answer.
Common pitfalls
- Stopping at human error. "Someone made a mistake" is rarely a root cause. Ask why the system allowed the mistake.
- Blaming individuals. Blame makes people defensive and hides information. Focus on processes and systems.
- Guessing instead of checking. Unverified answers can lead the chain in the wrong direction.
- Counting to five mechanically. Stop when you reach a fixable cause, whether that takes three whys or seven.
- No follow-through. An analysis without owned countermeasures changes nothing.
The Five Whys is a staple of continuous improvement and kaizen, and it fits within the PDCA cycle and problem management practices.
Frequently asked questions
Who invented the five whys technique?
The five whys comes from Toyota. It is associated with Sakichi Toyoda, the inventor whose loom company Toyota grew out of, and Taiichi Ohno built it into the Toyota Production System, describing it as the basis of Toyota's scientific approach to problems. It later spread through lean manufacturing into software, operations and product teams.
When should you stop asking why in a five whys analysis?
Stop when the answer points to a process, system or decision the team can change to prevent the problem from recurring, whether that takes three whys or seven. Stopping too early, such as at human error or a longer timeout, usually treats a symptom. Then agree countermeasures with owners and dates, and check later that they worked.
What are the weaknesses of the five whys method?
The five whys follows a single chain of causes, while many problems have several causes that combine. Results depend on who is in the room, so different groups can reach different root causes, and the method has no built-in way to verify answers. Check each step against evidence and branch the analysis when a why has several valid answers.