5 Whys Analysis: Complete Guide with Examples and Templates
A machine stops on the production floor. The maintenance tech fixes the motor. Three weeks later, the same machine stops again. This time, a different tech replaces the same motor. Nobody asks why the motor failed in the first place.
That cycle — fix, repeat, fix again — is what the 5 Whys technique was designed to break. It's a deceptively simple method: ask "why" five times in sequence, and you'll reach the root cause of almost any problem. Used correctly, it converts reactive firefighting into permanent fixes.
This guide covers how the 5 Whys works, where it fits into a broader investigation process, and how to avoid the common mistakes that make it produce useless answers.
What Is the 5 Whys Technique?
The 5 Whys is an iterative questioning method that traces a problem back to its origin by asking "why" at each step in the causal chain. The name comes from the observation that five rounds of questioning is usually enough to get past symptoms and surface conditions to reach an underlying systemic failure.
Sakichi Toyoda developed the approach in the early days of Toyota's manufacturing operations. Taiichi Ohno, the architect of the Toyota Production System, described it this way: "By repeating why five times, the nature of the problem as well as its solution becomes clear." Toyota's lean manufacturing model helped spread the technique globally through the 1980s and 1990s, and it's now embedded in quality management systems, OSHA investigation guidelines, ISO 45001, and Six Sigma frameworks worldwide.
The method works because most incidents don't have a single cause — they have a chain of causes. The chain matters. Fix only the last link (the visible symptom), and the chain reassembles itself. Fix the first link (the root cause), and the problem stops recurring.
When to Use the 5 Whys
The 5 Whys is best suited for:
- Workplace incidents and near-misses — equipment failures, slip-and-fall injuries, chemical exposures
- Quality defects — recurring nonconformances, customer complaints, production rejects
- Process breakdowns — missed deadlines, order errors, delivery failures
- IT and service incidents — system outages, performance degradation, security events
It's less effective for highly complex failures with many interacting variables (a large-scale chemical plant explosion, for example), where fault tree analysis or a fishbone diagram with quantitative data may be more appropriate. For most day-to-day incident investigations, though, it's the right starting point.
How to Conduct a 5 Whys Analysis Step by Step
Running a proper 5 Whys takes about 30 to 60 minutes for a typical workplace incident. Here's the process.
Step 1: Define the Problem Statement Clearly
Vague problem statements produce vague answers. "There was an accident" tells you nothing. "Employee sustained a laceration to the right hand while operating the slitting machine at 2:15 PM on March 3" gives you something to investigate.
A good problem statement answers: What happened, to whom, where, and when? Add measurable impact if available — "resulting in 4 lost workdays" or "causing a 200-unit production shortfall."
Step 2: Assemble the Right People
The person conducting the analysis needs direct knowledge of the process or equipment involved — ideally the operator, their supervisor, and a maintenance or quality representative. An outside facilitator (a safety manager or quality engineer) helps keep the questioning objective and prevents the group from stopping too early.
Avoid conducting a 5 Whys analysis as a solo desk exercise. The best answers come from people who were present or who work with the process daily.
Step 3: Ask "Why" Sequentially — and Document Each Answer
Start with the problem statement and ask why it occurred. Take the first answer as the next starting point, then ask why again. Repeat until you reach a root cause — typically a policy gap, design flaw, training failure, or systemic management issue rather than an individual's action.
Write each question and answer down. A documented chain is the deliverable, not just the final answer.
Step 4: Verify the Causal Chain
Read the chain backward to check logical consistency. "Because of A, B occurred. Because of B, C occurred..." If any link doesn't hold, revisit that step. A logical gap usually means you missed an intermediate cause or took a wrong branch.
Step 5: Identify Corrective Actions at the Root
Once you reach the root cause, assign a specific corrective action with an owner and a due date. The action should address the systemic issue — not just retrain the individual involved.
5 Whys Example: Manufacturing Incident
Here's how the analysis looks in practice.
Problem Statement: An operator sustained a laceration to the right hand while loading material into the packaging line.
| Step | Why? | Answer |
|---|---|---|
| Why 1 | Why did the operator sustain a laceration? | The operator's hand contacted an unguarded blade during a manual feed operation. |
| Why 2 | Why was the blade unguarded at the point of contact? | The blade guard had been removed to clear a jam earlier that shift and was not reinstalled. |
| Why 3 | Why was the guard not reinstalled after clearing the jam? | There is no lockout/tagout procedure requiring guard reinstallation before restart. |
| Why 4 | Why is there no LOTO step for guard reinstallation? | The current LOTO procedure was written before the blade guard was added to the machine design. |
| Why 5 | Why wasn't the LOTO procedure updated when the machine was modified? | There is no formal process for reviewing and updating safety procedures after equipment modifications. |
Root Cause: No management system for reviewing safety procedures following equipment changes.
Corrective Action: Establish a formal change management review process that includes a mandatory safety procedure audit whenever equipment is modified, with Engineering, EHS, and Operations sign-off before the machine returns to production.
Notice that "operator error" — the most common first answer to workplace injury investigations — doesn't appear as the root cause. It appeared in Why 1, but it wasn't the root cause. The system failed the operator, not the other way around.
Run Your Own 5 Whys Analysis
WhyTrace Plus guides you through each step of the 5 Whys with AI-assisted prompts, automatic causal chain documentation, and corrective action tracking — all in one place. No spreadsheets required.
5 Whys Template: Three Formats
The format matters less than the discipline of the questioning. That said, different teams prefer different templates.
Format 1: Linear Chain (Simple Problems)
Best for straightforward incidents with a clear single cause chain.
Problem: [Statement]
Why 1: [Answer]
Why 2: [Answer]
Why 3: [Answer]
Why 4: [Answer]
Why 5: [Answer]
Root Cause: [Summary]
Corrective Action: [Action] | Owner: [Name] | Due: [Date]
Format 2: Table Format (Standard Investigation)
Best for formal incident reports and regulatory documentation.
| Step | Question | Answer |
|---|---|---|
| Problem | What happened? | |
| Why 1 | Why did [problem] occur? | |
| Why 2 | Why did [Why 1 answer] occur? | |
| Why 3 | Why did [Why 2 answer] occur? | |
| Why 4 | Why did [Why 3 answer] occur? | |
| Why 5 | Why did [Why 4 answer] occur? | |
| Root Cause | ||
| Corrective Action | Owner: |
Format 3: Branching Tree (Complex Problems)
For incidents with multiple contributing factors, a single linear chain may miss parallel causes. In a branching analysis, each "why" step can produce multiple answers, each of which gets its own chain. This produces a tree structure that's more thorough — and more useful for systemic problems.
Branching analyses are harder to run manually on a whiteboard or in a spreadsheet. Most teams use software when they need this level of depth.
Try AI-Powered Why-Why Analysis
Now that you understand the concepts, try our AI-powered root cause analysis tool. Simply enter an incident and the AI will automatically dig into the causes.
Common Mistakes That Undermine the Analysis
Stopping at Symptoms
The most common mistake is treating "operator error," "distraction," or "carelessness" as a root cause. These are behavioral descriptions of the symptom, not explanations of why that behavior was possible or likely. Ask why the operator was able to make that error. What training, procedure, or engineering control was missing?
Leading Questions
"Isn't it because the operator didn't follow procedure?" is not a why question — it's an accusation framed as a question. Leading questions shut down honest investigation. Keep questions neutral: "Why was the guard not in place at that point in the process?"
Single-Path Thinking
Real incidents almost always have multiple contributing factors. A machine fails AND the operator was covering a double shift AND the maintenance log hadn't been reviewed in six months. A single-chain 5 Whys may miss two of those three factors. Consider branching, and ask participants explicitly: "Is there anything else that contributed to this step in the chain?"
No Verification Step
Documenting five answers and calling it done isn't analysis — it's guessing with extra steps. Read the chain back to verify logical consistency. If you can't connect "because of A, B occurred," you've missed something.
Corrective Actions That Don't Address the Root Cause
"Retrain all operators" is the default corrective action in too many investigations, even when the root cause was a management system failure. Training addresses knowledge gaps. It doesn't fix missing procedures, inadequate equipment, or absent management controls. Match the action to the actual root cause.
The Stakes: Why Getting This Right Matters
According to the Bureau of Labor Statistics, there were 5,070 fatal work injuries in the United States in 2024 — a 4% decline from 2023, but still nearly 14 worker deaths per day (BLS Census of Fatal Occupational Injuries, 2024, released February 2026). Employers also reported 2.5 million nonfatal workplace injuries and illnesses that year, down 3.1% from 2023.
The National Safety Council estimates the total cost of work injuries in 2023 at $176.5 billion, including $36.8 billion in medical expenses, $53.1 billion in wage and productivity losses, and $59.5 billion in administrative expenses (NSC Injury Facts). The average cost per medically consulted injury was $43,000.
On the regulatory side, OSHA's current maximum penalties reach $16,550 per serious violation and $165,514 per willful or repeat violation (OSHA Penalties, 2025). A facility with recurring incidents and inadequate investigation documentation faces compounding risk on both fronts.
A proper 5 Whys analysis — one that reaches actual root causes and generates corrective actions that stick — directly reduces the recurrence rate of incidents that drive these costs. The analysis itself is not the point. Preventing the next incident is the point.
Track Every Investigation in One Place
WhyTrace Plus stores your 5 Whys analyses, corrective action deadlines, and incident history in a searchable knowledge base — so patterns surface before they become injuries.
Start your first analysis free | See pricing
Frequently Asked Questions
Does the problem always require exactly five "whys"?
No. Five is a guideline, not a rule. Some problems reach a root cause at three levels. Complex systemic issues may require seven or more. Stop when you reach a cause that is actionable and fundamental — where a management system, process design, or organizational decision is the explanation. Taiichi Ohno framed the number five as a minimum discipline to get past surface-level symptoms, not as a literal count.
What's the difference between a root cause and a contributing factor?
A root cause is a fundamental condition — a missing policy, a design flaw, a training gap — that, if corrected, prevents the problem from recurring. A contributing factor is a condition that made the incident more likely or more severe, but correcting it alone wouldn't prevent recurrence. In a thorough investigation, you document both. Your corrective actions should address the root cause first, then the contributing factors.
How does the 5 Whys fit with fishbone diagrams?
They're complementary, not competing tools. A fishbone diagram (also called an Ishikawa or cause-and-effect diagram) maps all possible contributing causes across categories like machine, method, material, and man. The 5 Whys then drills down into the most likely causes to find the root. Many investigators use the fishbone to brainstorm during the analysis, then apply the 5 Whys to the highest-priority branches.
When should we use a different RCA method instead?
For high-complexity, multi-system failures — a large-scale process industry incident, a major software outage with many interacting components — fault tree analysis or a more structured method like FMEA may be more appropriate. The 5 Whys works best when a causal chain is identifiable and the problem scope is bounded. If your team is spending more than two hours on a single chain and still can't identify a clear root cause, shift to a method with more structured data collection.
Does OSHA require 5 Whys analysis?
OSHA does not mandate a specific root cause analysis method. OSHA's General Duty Clause requires employers to provide a workplace free from recognized hazards, and investigation of incidents is part of meeting that standard. OSHA's voluntary Incident Investigation guidelines recommend identifying root causes as part of any thorough investigation. ISO 45001, the international standard for occupational health and safety management systems, explicitly requires root cause determination as part of incident investigation (clause 10.2). For ISO-certified facilities, the 5 Whys is a well-accepted method for meeting that requirement.
Key Takeaways
- The 5 Whys traces a problem through a causal chain to reach a root cause — a systemic issue that, when corrected, prevents recurrence.
- "Operator error" is almost never a root cause. It's a starting point. Keep asking why.
- A proper analysis requires direct knowledge from people in the process, documented chain logic, and corrective actions matched to the root cause — not the symptom.
- The technique fits naturally within ISO 45001 incident investigation requirements and OSHA's investigation guidance, though neither mandates a specific method.
- For complex problems with multiple contributing factors, a branching 5 Whys or fishbone diagram may produce a more complete picture than a single chain.
- The goal isn't a completed form — it's preventing the next incident.
Related Resources
| Resource | Description | Best For |
|---|---|---|
| How to Do a 5 Whys Analysis | Detailed step-by-step walkthrough with practice exercises | Teams new to structured RCA |
| 5 Whys vs Fishbone vs Fault Tree | Side-by-side comparison of the three most common RCA methods | Choosing the right method for your incident type |
| OSHA Incident Investigation Guide | Step-by-step OSHA compliance for US EHS managers | Meeting regulatory documentation requirements |
| Free 5 Whys Template | AI-guided analysis with automatic causal chain documentation | Running your first digital analysis |
| 4M vs 5M1E vs SHELL vs SRE Framework Comparison | When the 5 Whys isn't enough: alternative frameworks explained | Complex or multi-factor incidents |