How to Do a 5 Whys Analysis That Actually Finds Root Causes
A press operator slips on fluid near a machine. The incident report: "operator lost footing — needs to watch where they walk." Investigation closed.
Three weeks later, the same thing happens to a different operator on a different shift.
This is what happens when an investigation stops at symptoms instead of causes. The fluid on the floor wasn't the problem — it was a sign of one. The 5 Whys technique exists precisely for moments like this: to push past the obvious and find what actually needs to change.
This guide walks through how to run a 5 Whys analysis correctly, step by step — with real examples from manufacturing and construction, and the most common places teams go wrong.
What Is the 5 Whys Technique (and Where It Comes From)
The 5 Whys is an iterative questioning method that traces a problem back to its root cause by asking "Why?" repeatedly — typically five times, though the number varies. Each answer becomes the subject of the next question, creating a cause-and-effect chain that leads from symptom to systemic failure.
The technique was developed by Sakichi Toyoda in the 1930s and became central to the Toyota Production System under Taiichi Ohno, who described it as the basis of Toyota's scientific approach to problem-solving. It spread from automotive manufacturing into quality management, construction safety, healthcare, and IT operations — and today it's a standard tool in ISO 9001 corrective action procedures and OSHA-recommended incident investigation methodology.
OSHA's guidance on incident investigation explicitly states that investigations must look beyond the immediate cause: "It is far too easy, and often misleading, to conclude that carelessness or failure to follow a procedure alone was the cause of an incident." The 5 Whys is one of the primary methods OSHA references for achieving that deeper analysis.
When to Use the 5 Whys
The 5 Whys works well for:
- Workplace safety incidents — injuries, near misses, property damage
- Quality defects — nonconformities, customer complaints, production failures
- Equipment breakdowns — unplanned downtime, recurring maintenance issues
- Process failures — missed deadlines, repeated errors, compliance gaps
It is most effective for problems with a clear, identifiable cause chain. For complex problems with multiple interacting factors — such as a major chemical release or a systemic culture issue — consider supplementing with a fishbone diagram or fault tree analysis to capture parallel cause branches.
The 5 Whys Process: Step by Step
Step 1: Assemble the Right Team
A 5 Whys analysis done solo almost always misses something. Bring together 3–6 people who have direct knowledge of the process where the problem occurred. That means frontline workers, not just supervisors. The operator who was there, the maintenance tech who services the equipment, the team lead who knows the workflow.
Designate a facilitator — someone who keeps the discussion moving and ensures questions stay focused on the process, not the people. The facilitator's job is to ask "Why?" without leading the team toward a predetermined answer.
Management can participate, but the session should feel psychologically safe. If workers believe they'll be blamed, they'll give shallow answers.
Step 2: Define the Problem as a Specific Statement
Vague problem statements produce vague analysis. "We have a safety issue" tells you nothing. "An operator sustained a laceration on their right hand while unloading a steel coil from Line 3 at 7:40 AM on March 2" gives you something to work with.
A good problem statement answers:
- What happened
- Where it happened
- When it happened
- Who or what was involved
Write it down and make sure everyone in the room agrees it accurately describes the problem before asking the first "Why."
Step 3: Ask "Why?" — and Demand Evidence
This is where most analyses fail. Teams ask "Why?" and accept the first plausible answer without checking whether it's actually true.
For each "Why," push for evidence:
- "How do we know that?"
- "Can we verify that with data?"
- "Has anyone observed this directly?"
The answer to each "Why" should be a fact — something you can confirm through observation, records, or measurement — not a guess or assumption.
Avoid answers that blame individuals. If "Why?" leads you to "because the operator wasn't paying attention," that's a dead end. Push further: Why was the operator in a position where attention lapse could cause harm? What in the system allowed that vulnerability to exist?
Step 4: Follow the Cause Chain to Systemic Level
Continue asking "Why?" until you reach a cause you can actually fix — meaning a system, process, procedure, training, or design issue that can be changed.
You've likely reached the root cause when:
- Further questioning leads to factors outside your organization's control
- You've identified a broken or missing system, procedure, or standard
- The cause explains why the problem could happen to anyone in that situation, not just this specific person on this specific day
The "5" in 5 Whys is a guideline, not a rule. Some problems take three iterations. Complex incidents may take seven or eight. Stop when you reach a cause that is both actionable and explains the original problem.
Step 5: Document the Full Chain
Write down every step — the problem statement, each "Why," each answer, and the evidence or logic behind each answer. This chain is your audit trail and your communication tool.
A well-documented 5 Whys analysis shows:
- The logic that connects the incident to the root cause
- Where the corrective action targets
- Why previous fixes didn't prevent recurrence
Under ISO 9001 and ISO 45001, this documentation supports CAPA (corrective and preventive action) requirements and demonstrates that your investigation addressed the systemic level.
Step 6: Identify and Assign Corrective Actions
For each root cause identified, define:
- What action will be taken
- Who owns it
- By when it will be completed
- How completion will be verified
Corrective actions should address the root cause, not the symptom. If the root cause is "no written procedure for equipment servicing," the corrective action is to create and train on that procedure — not to put a sign on the machine.
Step 7: Follow Up and Verify Effectiveness
A corrective action that nobody checks is a corrective action that often doesn't happen. Set a follow-up date — typically 30–90 days after implementation — to verify that the action was completed and that the problem has not recurred.
Track the incident type over time. If similar incidents continue after the corrective action, the analysis may have stopped at a symptom rather than the actual root cause.
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.
Run Your 5 Whys Analysis in WhyTrace Plus
WhyTrace Plus guides your team through each step of the 5 Whys process with AI assistance — from structuring the cause chain to generating corrective actions. Free to start, no installation required.
Start your first analysis | See how it works
Two Real-World Examples
Example 1: Machine-Related Laceration in an Assembly Plant
Problem: An operator sustained a laceration on their right hand while clearing a jam on a conveyor line.
| # | Why? | Answer |
|---|---|---|
| 1 | Why did the operator get cut? | Their hand contacted a moving belt while clearing the jam. |
| 2 | Why was their hand near a moving belt? | The operator reached into the machine without stopping it first. |
| 3 | Why didn't the operator stop the machine? | There is no lockout/tagout procedure posted for this equipment. |
| 4 | Why is there no LOTO procedure posted? | The equipment was added six months ago and the procedure was never created. |
| 5 | Why was no procedure created when equipment was added? | There is no formal onboarding checklist for new equipment that includes LOTO documentation. |
Root cause: No equipment onboarding checklist requiring LOTO documentation before a new machine goes into service.
Corrective action: Create an equipment commissioning checklist that requires LOTO procedure development, signage, and operator training before any new equipment begins production use. Assign ownership to the EHS manager. Complete within 30 days.
This is a significantly different outcome than "operator needs retraining on LOTO." The retraining might help this operator — but the next piece of equipment added to the line will have the same gap.
Example 2: Fall Incident at a Construction Site
Problem: A subcontractor worker fell from a 6-foot platform on Level 2 of a commercial building project, sustaining a fractured wrist.
| # | Why? | Answer |
|---|---|---|
| 1 | Why did the worker fall? | There was no guardrail on the open side of the platform. |
| 2 | Why was there no guardrail? | It had been removed two days earlier to move materials and was not replaced. |
| 3 | Why wasn't the guardrail replaced after material handling? | No one was assigned responsibility for restoring fall protection after temporary removal. |
| 4 | Why is no one assigned that responsibility? | The subcontract agreement does not specify fall protection restoration protocols. |
| 5 | Why don't subcontract agreements include that specification? | The general contractor's subcontractor safety requirements were last updated in 2019 and do not reflect current site conditions or scope. |
Root cause: Subcontractor safety requirements are outdated and do not include temporary fall protection removal and restoration protocols.
Corrective action: Revise subcontract safety requirements to include explicit fall protection protocols. Add a daily pre-shift platform inspection to the site safety checklist. Complete before any new subcontractor mobilizes on site.
Again, the obvious fix — retrain the subcontractor crew — would not prevent the same gap from appearing with the next crew on the next project.
Common Mistakes That Undermine the Analysis
Stopping at Operator Error
"Human error" is not a root cause. It's a starting point. If your 5 Whys chain ends with "the worker made a mistake," ask one more question: what in the work environment, training, procedure, or design made that mistake possible or likely?
OSHA's guidance is direct on this point: investigations that conclude with worker carelessness "fail to discover the underlying or root causes of the incident, and therefore fail to identify the systemic changes and measures needed to prevent future incidents."
Accepting Assumptions as Facts
"The machine probably wasn't maintained properly" is an assumption. "Maintenance records show the last scheduled service was 14 months ago, versus the recommended 6-month interval" is a fact. Base each step of the chain on verifiable evidence, not what seems plausible.
Conducting the Analysis Alone or in Management Only
The people closest to the work know things that managers don't. A 5 Whys session without frontline workers regularly misses the practical realities of how work actually gets done — versus how it's supposed to get done on paper.
Asking "Who" Instead of "Why"
The question "Who forgot to replace the guardrail?" takes you to a person. The question "Why was there no system to ensure the guardrail was replaced?" takes you to a fixable process. Keep the framing on systems and processes throughout.
Jumping to Solutions Too Early
Teams sometimes identify a plausible root cause in the second or third iteration and immediately start discussing fixes. This short-circuits the analysis. Finish the cause chain before moving to corrective actions.
Writing Vague Corrective Actions
"Improve training" or "increase awareness" are not corrective actions. They cannot be verified as complete, and they rarely address a root cause. A corrective action specifies: what will change, who is responsible, and by when it will be done and verified.
How Many "Whys" Is Enough?
There is no universal answer. The technique is named "5 Whys" because that's approximately how many iterations are needed in most cases before reaching a systemic cause. In practice:
- Simple, single-cause problems may reach a root cause in 3 iterations
- Standard workplace incidents typically take 4–6
- Complex or multi-factor incidents may need 7–8, or may benefit from branching into multiple cause chains
You've gone far enough when you've reached a cause that is both actionable and sufficient to explain the original problem. You've gone too far when further "Whys" lead to factors your organization cannot influence.
Connecting 5 Whys to Your CAPA and Compliance Process
Under ISO 9001 and ISO 45001, organizations must demonstrate that corrective actions address root causes — not just symptoms. The 5 Whys provides a documented cause chain that satisfies this requirement. Auditors reviewing CAPA records expect to see the logical path from incident to root cause to corrective action.
For US facilities, OSHA's PSM standard (29 CFR 1910.119) requires incident investigation for covered processes, and OSHA broadly recommends root cause methodology for all significant incidents. OSHA's published guidance cites 5 Whys specifically as an appropriate investigation technique.
Maintaining investigation records — including the full 5 Whys chain, evidence supporting each step, and corrective action status — is both a compliance requirement and a practical asset. Organizations that build a body of investigation records over time can identify recurring root causes, prioritize systemic fixes, and make a measurable case for process improvements.
Track Your Corrective Actions in WhyTrace Plus
After the analysis, WhyTrace Plus keeps your corrective actions visible, assigned, and trackable — so nothing falls through the cracks between the investigation and the fix.
Key Takeaways
- Define the problem specifically before asking the first "Why" — vague statements produce vague analysis
- Every answer in the chain should be supported by evidence, not assumption
- Stop when you reach a systemic cause: a broken or missing process, procedure, training, or design
- "Human error" is a starting point, not a root cause
- Corrective actions must be specific, assigned, and verifiable — not general improvement goals
- Document the full cause chain to support ISO 9001/45001 CAPA requirements and OSHA compliance
- Follow up to confirm corrective actions were implemented and effective
The 5 Whys is not complicated. The challenge is discipline: asking one more question when the obvious answer looks good enough, insisting on evidence when assumptions feel obvious, and writing corrective actions that actually change the system.
That discipline is what separates investigations that prevent recurrence from investigations that simply close the ticket.
Related Resources
| Resource | Description | Best For |
|---|---|---|
| 5 Whys Complete Guide | Comprehensive overview with templates | Understanding the full 5 Whys framework |
| 5 Whys vs Fishbone vs Fault Tree | Choosing the right RCA method | Deciding which tool fits your situation |
| OSHA Incident Investigation Guide | Step-by-step OSHA compliance walkthrough | US regulatory investigation requirements |
| ISO 45001 Incident Investigation | OHS management requirements and best practices | ISO 45001 CAPA documentation |
| RCA Report Writing Guide | Writing investigation reports that get action | Communicating findings to management |