How to Use 5 Whys Analysis: Step-by-Step Guide with Examples

1. What Is the 5 Whys Method?

The 5 Whys is a root cause analysis technique developed by Sakichi Toyoda and popularised through the Toyota Production System. The premise is simple: by repeatedly asking "why?" — typically five times — you move from the surface symptom of a problem to its underlying root cause.

It's used across industries for quality problems, process failures, equipment breakdowns, and workplace incidents. Its appeal is its simplicity: no special training required, no complex tools, and it can be done in minutes for simple problems.

Developed in the 1930s and formalised in Toyota's manufacturing processes through the 1970s, 5 Whys became a global standard through the lean manufacturing movement. Today it's used everywhere from Silicon Valley product teams to hospital safety departments to oil refineries.

"The basis of Toyota's scientific approach is to ask why five times whenever we find a problem." — Taiichi Ohno, Toyota Production System (1978)

2. How to Conduct a 5 Whys Analysis

Here is the step-by-step process for running an effective 5 Whys investigation:

Step 1: Define the Problem Precisely

The quality of your analysis depends entirely on how well you define the starting problem. A vague problem produces vague answers. Be specific:

• ❌ Vague: "The machine broke down"
• ✅ Specific: "Conveyor belt on Line 3 stopped at 14:32 on Monday, causing a 90-minute production halt"

Include: what happened, where, when, and what the impact was. The more precise your problem statement, the more useful your root cause analysis will be.

Step 2: Gather the Right People

5 Whys works best as a team exercise, not a solo activity. Include people who:

• Were present when the problem occurred
• Have technical knowledge of the process or equipment
• Can challenge assumptions without assigning blame

For workplace incidents, this means the affected workers and their supervisor, not just the safety manager at a desk.

Step 3: Ask "Why?" and Document the Answer

Ask why the problem occurred. Write down the answer. Be factual — base answers on evidence, not assumptions. Each answer becomes the new "problem" for the next why.

If you find yourself writing "because someone didn't follow the procedure," stop and ask why they didn't follow it. What made following the procedure difficult? That's where the real information is.

Step 4: Repeat Until You Reach a Root Cause

Keep asking why. You'll know you've reached a root cause when:

• The answer points to a process, system, or management decision — not a person
• Fixing this cause would prevent the problem from recurring
• Further "why" questions produce answers outside your control

It doesn't have to be exactly five. Some problems need three. Complex incidents may need seven. The "5" is a guideline, not a rule.

Step 5: Identify and Implement Corrective Actions

For each root cause identified, define a corrective action that addresses it. Assign an owner and a due date. Without these, the analysis has no value.

Step 6: Verify the Fix

After implementing corrections, confirm the problem hasn't recurred. If it has, return to your analysis — you may not have gone deep enough.

3. Real-World Examples

Example 1: Equipment Failure (Manufacturing)

Problem: CNC machine stopped mid-run, scrapping a batch of parts worth $4,200.

Corrective action: Mount tool change schedules on each machine. Implement a visual management system for maintenance tracking. Review all similar information-access gaps across the facility.

Example 2: Workplace Injury (Construction)

Problem: Worker sustained a laceration to the right hand while cutting conduit on a construction site.

Corrective action: Review and update SWMS for all cutting tasks. Add workholding equipment to the pre-task checklist. Implement task-specific toolbox talks before cutting operations.

Example 3: Process Failure (Mining — Haul Truck Collision)

Problem: Two haul trucks made contact at an intersection in the pit, causing $85,000 in damage. No injuries.

Corrective action: Update blasting procedure to include post-blast traffic management reinstatement as a mandatory step. Assign the blast crew supervisor as responsible for sign-off before traffic resumes.

4. Common Mistakes (and How to Avoid Them)

Mistake 1: Stopping at "Human Error"

The most common failure in 5 Whys. When you reach "the operator made a mistake" or "the worker didn't follow the procedure," the instinct is to stop. Don't. Ask why the person made that choice — what conditions made the error likely? What system allowed the error to happen? Human error is almost always a symptom, not a root cause.

Mistake 2: Asking Leading Questions

5 Whys is not an interrogation. The facilitator's job is to ask open questions and document honest answers, not guide the team toward a predetermined conclusion. "Why didn't he read the procedure?" is leading. "Why wasn't the procedure followed?" is open.

Mistake 3: Following Only One Chain

Real problems often have multiple contributing causes, not a single linear chain. If at any "why" you identify multiple contributing answers, document all of them. Run parallel chains when needed. A single-path 5 Whys often misses important causes.

Mistake 4: Guessing Instead of Evidencing

Each "why" answer should be supported by evidence — physical evidence, documents, witness accounts. If you're speculating, say so explicitly, then go verify. Speculative root causes produce speculative corrective actions that don't fix the real problem.

Mistake 5: No Corrective Actions

The analysis is worthless without action. Every root cause needs at least one corrective action with an owner and a due date. "We'll be more careful" is not a corrective action.

Mistake 6: Using It for Complex Incidents

5 Whys is a simple tool designed for simple-to-moderate problems. For serious incidents — fatalities, high-potential near misses, complex multi-factor events — it's not deep enough. You need a structured methodology like ICAM. More on this below.

5. When to Use 5 Whys — and When Not To

Use 5 Whys When:

• The problem is relatively simple with a clear causal chain
• You need a quick analysis — less than 30 minutes
• The incident is low-to-moderate severity (minor injuries, quality issues, process delays)
• You're dealing with recurring operational problems or equipment issues
• It's a first pass to decide if a deeper investigation is warranted

Don't Use 5 Whys Alone When:

• The incident involved a fatality or serious injury
• Multiple people, systems, or departments were involved
• The incident has regulatory reporting requirements
• You need to analyse organizational factors (management decisions, resource allocation, culture)
• The same type of incident has recurred despite previous 5 Whys investigations
• You're in a high-hazard industry with potential for fatal events (mining, construction, oil & gas)

6. 5 Whys vs ICAM: Choosing the Right Method

Both 5 Whys and ICAM are root cause analysis methods — but they're designed for different problems.

Dimension	5 Whys	ICAM
Best for	Simple, single-cause problems	Complex, multi-factor incidents
Time to complete	15 minutes to 2 hours	Hours to days
Organizational factors	Possible but often missed	Explicitly required
Structure	Minimal — depends on facilitator	Highly structured framework
Regulatory acceptance	Adequate for minor incidents	Gold standard for serious events
Training required	Minimal	Moderate (1–2 days)
Industries	All industries	Mining, oil & gas, construction, energy

Many organisations use both: 5 Whys for everyday problems and quality issues, ICAM for serious incidents and high-potential near misses. This tiered approach is practical and sensible.

To learn more about ICAM and when it's the right choice, read our Complete ICAM Investigation Guide. For a broader comparison of root cause analysis methods including Fishbone, Fault Tree Analysis, and SCAT, see our Root Cause Analysis Methods Guide.

7. 5 Whys Template & Worksheet

Here's a simple 5 Whys template you can use immediately. For a downloadable version with more RCA tools, see our Root Cause Analysis Templates.

For more complex incidents — especially in high-hazard environments — consider supplementing 5 Whys with the ICAM framework to ensure organizational factors are captured. InvestigatePro includes structured 5 Whys as part of its AI-guided investigation toolkit.

📥 Download the free 5 Whys Worksheet — interactive worksheet with worked example and corrective action tracker.

📋 Download the free RCA Template Pack — 4 templates in one: 5 Whys, Fishbone Diagram, ICAM-aligned RCA, and full Investigation Report. Fill in online or print.

Related Articles