Skip to main content
Category: Methods
Type: Problem-Solving Technique
Origin: Sakichi Toyoda, 1930s, Japan
Also known as: 5 Whys, Why Analysis, Root Cause Analysis
Quick Answer — Five Whys is a simple yet powerful root cause analysis technique: when a problem occurs, ask “why” five times in succession to drill down from the immediate symptom to the fundamental cause. Developed at Toyota in the 1930s by founder Sakichi Toyoda, this method uncovers problems that surface-level fixes miss, leading to solutions that prevent recurrence rather than merely treating symptoms.

​
What is Five Whys?

Five Whys is an iterative questioning technique used to identify the root cause of a problem by repeatedly asking “why” until the fundamental issue is revealed. The premise is simple: surface-level solutions treat symptoms, while understanding the deeper cause enables permanent fixes. The technique typically follows this pattern: identify a problem, ask why it happened, identify the cause, ask why that happened, and repeat until you’ve reached the fifth “why” and uncovered the systemic root cause. The answer at this depth usually reveals a process flaw, organizational issue, or assumption that, if corrected, prevents the problem from recurring.
“Between stimulus and response there is a space. In that space is our power to choose our response. In our response lies our growth and our freedom.” — Viktor Frankl, echoing the reflective principle behind Five Whys
The method gained prominence through the Toyota Production System, where it became known as the “5 Whys” or “Toyota’s 5 Whys.” Unlike complex statistical methods, Five Whys requires no special tools—just a curious mind and willingness to challenge assumptions. Its simplicity is its power: any team member can use it immediately without training.

​
Five Whys in 3 Depths

  • Beginner: When facing any problem, ask “why” five times before proposing a solution. Write down each answer. The fifth answer usually reveals the systemic issue worth addressing.
  • Practitioner: Use Five Whys for both problems and opportunities. When something succeeds, asking why it succeeded reveals what to preserve and amplify, not just what to fix.
  • Advanced: Combine Five Whys with other analysis tools—fishbone diagrams, fault tree analysis—to visualize the causal chain and identify multiple root causes that interact.

​
Origin

Five Whys originated at Toyota Motor Corporation in the 1930s, credited to Sakichi Toyoda, the founder of the Toyota group. Toyoda developed the technique as part of his Toyota Production System, which emphasized continuous improvement (kaizen) and respect for people. The method became central to Toyota’s problem-solving culture. The technique was later popularized worldwide through the 1986 book “The Machine That Changed the World” by James Womack and Daniel Jones, which documented the Toyota Production System. In the 1990s, it became a standard practice in lean manufacturing and later spread to software development, healthcare, and management consulting. A key figure in spreading Five Whys was Taiichi Ohno, who formalized its use in Toyota’s problem-solving training. Ohno emphasized that asking “why” five times was not a rigid rule but a guideline—sometimes three whys reveal the root cause, sometimes seven are needed.

​
Key Points

1

Drill Past Surface Symptoms

The first “why” often points to immediate causes. Continue asking until you’ve moved from “what happened” to “why this system allows this to happen.”
2

Focus on Process, Not Blame

The goal is to improve systems, not assign blame. Frame answers around process failures rather than human errors to maintain psychological safety.
3

Answers Must Be Actionable

Each cause should point to something you can actually change. If your final answer is “because that’s human nature,” you haven’t gone deep enough.
4

Verify with Data When Possible

While Five Whys is a thinking tool, verify root causes with data when possible. Assumptions masquerading as causes lead to ineffective solutions.

​
Applications

Software Bug Resolution

When a bug is discovered, use Five Whys to determine not just how to fix it but why the testing process or code review didn’t catch it earlier.

Customer Complaint Analysis

Beyond addressing individual complaints, use Five Whys to identify systemic issues in product or service design that create recurring complaints.

Project Post-Mortems

After project failures, ask why execution, planning, or communication failed at a systemic level to improve future project outcomes.

Strategic Decision Making

Apply Five Whys to understand why a strategic initiative is needed, revealing whether the underlying assumption is valid.

​
Case Study

Toyota’s use of Five Whys became legendary in manufacturing. In one documented example from the 1970s, a machine at a Toyota plant stopped working. The first why asked why it stopped (overload). The second why asked why it was overloaded (insufficient lubrication). The third why asked why there was no lubrication (pump worn out). The fourth why asked why the pump was worn out (shaft was not checked). The fifth why asked why the shaft was not checked (no scheduled maintenance). The solution wasn’t simply to repair the machine—it was to implement scheduled maintenance. This systemic fix prevented not just this machine failure but all machines with similar pump issues. This pattern—treating root causes rather than symptoms—became a hallmark of Toyota’s operational excellence. In software, Etsy adopted Five Whys as part of their post-incident review process. Their 2014 blog post documenting the practice showed how asking why led to changes in deployment procedures, monitoring thresholds, and on-call training—far beyond the immediate technical fix.

​
Boundaries and Failure Modes

If you stop at an emotionally convenient answer rather than a verified one, you’ll solve the wrong problem. Always validate root causes with data when possible.
In organizations with blame culture, people hide systemic issues to avoid punishment. Five Whys only works in environments that separate failures from fault.
Five Whys finds one causal chain. Complex problems often have multiple contributing factors that require additional tools to identify.

​
Common Misconceptions

The number five is a guideline, not a rule. Some problems require three whys; others need seven. Stop when you’ve found a systemic cause you can address.
Five Whys works equally well for successes. Asking why something succeeded reveals what to preserve and amplify in your processes.
Fresh perspectives catch assumptions that the person closest to the problem misses. Five Whys is most powerful in collaborative sessions.
Five Whys connects to broader problem-solving and analytical thinking methods.

Root Cause Analysis

Root Cause Analysis is the broader discipline that Five Whys is one technique within.

Fishbone Diagram

Fishbone Diagram visualizes multiple potential causes in a structured format, often used alongside Five Whys.

First Principles Thinking

First Principles Thinking breaks problems to fundamental truths, similar to Five Whys’ depth of inquiry.

​
One-Line Takeaway

Don’t treat symptoms—ask why five times to find the systemic cause that, once fixed, prevents recurrence.