Five Whys
Chase the problem down to its root.
The Five Whys is the simplest tool in the kit and the most often skipped. Ask why five times and you stop treating symptoms. Most teams never get past Why 2. The root cause is usually a system, incentive, or assumption — not the event that triggered the conversation.
How to run this
- State the problem as a specific observable event — something you can point to.
- Ask "why did this happen?" and write the first answer. Resist the urge to jump to solutions.
- Ask "why?" to that answer. Repeat until you reach Why 5.
- Circle the answer that could be changed to prevent recurrence.
- Check: if you fix the root cause, does the chain above it go away?
Five Whys
Sakichi Toyoda · Toyota Production System · 1930sStopping at Why 2 — the first answer is usually a symptom, not a cause. Push deeper until you hit a system, a decision, or an assumption.
Root cause identifies something fixable: a process, a policy, a missing check. Not a person. "John didn't review it" is not a root cause.
When fixing the root cause would prevent the original problem from ever happening again — not just this time.
Try it interactively with WAiDE
WAiDE will guide you through the Five Whys — asking the right follow-up questions at each level, and helping you distinguish symptoms from root causes. You'll leave with a completed analysis and a session report.