What is the Five Whys — and when to stop asking.
Short answer
The Five Whys is a root cause analysis technique where you ask "Why?" repeatedly — typically five times — to move from a surface symptom to an underlying systemic cause. Developed by Sakichi Toyoda and central to the Toyota Production System, it's used in post-mortems, process improvement, and product problem-solving. The goal is a root cause that's actionable and preventive, not a person to blame.
The Five Whys was developed by Sakichi Toyoda, founder of Toyota Industries, and became a cornerstone of the Toyota Production System (TPS) in the 1950s. It was popularized in lean manufacturing and later adopted across software engineering, healthcare, and service operations.
How it works. Start with a problem statement — the symptom as observed. Ask why it happened. Take the answer and ask why again. Repeat until you reach a cause that is systemic and actionable rather than individual and surface-level. The number five is a guideline, not a rule — some problems reach root cause in three whys; complex incidents may take seven or eight.
Example: production outage.
- Why did the site go down? — A database query timed out.
- Why did the query time out? — It was running on a table with 50M rows and no index.
- Why was there no index? — The migration that added the table didn't include an index.
- Why didn't the migration include an index? — The migration was written by a developer who didn't know the table would grow to that size.
- Why didn't they know? — There's no process for estimating table growth during migration review.
Root cause: no process for growth estimation in migration review. Preventive action: add a growth estimate checklist to the migration review template. This is systemic and preventable — it applies to the next developer writing a migration, not just the person who wrote this one.
The branching five whys. Complex problems often have multiple "Why" threads. The branching approach acknowledges that a single "Why?" may have 2–3 independent answers, each worth following. Draw the tree on a whiteboard: problem at the top, branches diverging at each multi-cause step.
When to stop. Stop when the answer to "Why?" is a systemic gap you can address — a missing process, a design flaw, a resource constraint. Stop when the cause is outside your control (an earthquake, a vendor's infrastructure failure). Stop when further drilling produces tautologies ("Why is the process missing? Because no one created it.").
Common mistakes. Stopping too early (surface cause, not root cause). Blaming a person as the root cause ("because John didn't test it" — that's not actionable systemically). Following only one branch when there are multiple contributing causes.
Five Whys is most effectively done at a whiteboard where the team can see the branch structure and contribute branches they know about. Snap the whiteboard with BoardSnap and the AI reads the why chain and produces a structured root cause summary.
Frequently asked
Who invented the Five Whys?
Sakichi Toyoda, founder of Toyota Industries, developed the technique in the early 20th century. It became central to the Toyota Production System under Taiichi Ohno and was popularized globally through the lean manufacturing movement. Eric Ries later included it in *The Lean Startup* for software product development.
Is it always exactly five whys?
No. Five is a heuristic, not a rule. Some problems are solved in three whys; complex systemic issues may take seven or eight iterations. The goal is to reach a root cause that's genuinely preventable — not to reach exactly five questions regardless of where you are in the chain.
What's the difference between Five Whys and fishbone diagrams?
Five Whys is a linear or branching chain of cause-and-effect questions. A fishbone (Ishikawa) diagram categorizes potential causes along predefined branches (People, Process, Technology, Environment) before exploring each branch. Five Whys is faster and more conversational; fishbone is more structured and useful when you want to ensure no category of cause is overlooked.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.