5 Whys Analysis: How to Uncover the True Cause
Table of Contents
- What is 5 Whys Analysis?
- Core Principles of 5 Whys
- Practical Case: From Surface to Root Cause
- Common Pitfalls and How to Avoid Them
- 5 Whys Analysis Template and Usage Tips
What is 5 Whys Analysis?
5 Whys analysis is a tool that involves repeatedly asking "why" to delve deeper into the root cause of a problem. Proposed by Sakichi Toyoda, the founder of the Toyota Production System, it is one of the most commonly used root cause analysis tools in lean manufacturing and quality management.
Core Concept
Phenomenon ≠ Cause. Addressing only the surface phenomenon will lead to recurring issues. Only by identifying the root cause can problems be resolved permanently.
Core Principles of 5 Whys
- Get to the Bottom of It: Continue asking "why" until a cause that can be addressed with a systemic solution is identified (usually a process, standard, or management issue).
- Fact-Based: Each "why" must be supported by facts, not assumptions.
- Avoid Blame: Do not attribute the cause to individuals; focus on systemic and process-level issues.
- Distinguish Between Root Cause and Proximate Cause: The proximate cause is the immediate event that leads to the problem, while the root cause is a systemic flaw.
Practical Case: From Surface to Root Cause
Case: Machine Downtime Analysis in a Factory
Problem Phenomenon: The machine suddenly stopped, causing a 2-hour production line shutdown.
Why1: Why did the machine stop? → The fuse burned out.
Why2: Why did the fuse burn out? → Excessive current.
Why3: Why was there excessive current? → The bearing was jammed, increasing the load.
Why4: Why was the bearing jammed? → Insufficient lubrication led to bearing wear.
Why5: Why was there insufficient lubrication? → The lubrication pump malfunctioned, and there was no record of regular inspections.
Root Cause: Lack of a maintenance process for the equipment—no regular inspection and maintenance procedures were established for the lubrication pump.
Immediate Action: Replace the fuse and bearing, add lubrication, and resume production.
Permanent Action: Establish a daily inspection system for the lubrication pump and integrate it into TPM management.
Case: Surface Scratch Issue in an Electronics Factory
Problem Phenomenon: The defect rate for surface scratches on products is 3%.
Why1: Why are there scratches? → The conveyor belt guard scratched the products.
Why2: Why did the guard scratch the products? → The edge of the guard had burrs.
Why3: Why did the guard have burrs? → The guard was not maintained over long-term use.
Why4: Why was it not maintained? → The equipment inspection checklist did not include the guard.
Why5: Why was the guard not included in the inspection checklist? → The equipment maintenance standard was incomplete, failing to identify risk points.
Root Cause: The equipment maintenance standard lacked a process for identifying key risk points.
Permanent Action: Update the equipment inspection checklist to include the guard; establish a PFMEA review mechanism to regularly identify risk points.
Common Pitfalls and How to Avoid Them
Pitfall 1: Stopping Too Early → Concluding after only 2-3 "whys." Countermeasure: Ask "why" until a systemic solution can be implemented (usually 5-7 layers).
Pitfall 2: Blaming Individuals → "Because of an employee's mistake." Countermeasure: Ask "why" the employee made a mistake—insufficient training? Unclear work instructions? Fatigue?
Pitfall 3: Guessing Instead of Fact-Finding → Using "possibly" or "probably" to guess the cause. Countermeasure: Each "why" must be supported by data or on-site evidence.
Pitfall 4: Confusing Multiple Causes → One "why" leading to multiple causes. Countermeasure: Use a fishbone diagram to list potential causes and verify them one by one.
Pitfall 5: Confusing Cause with Phenomenon → Using the phenomenon as the cause. Countermeasure: Each "why" must provide a "cause" and not repeat the phenomenon.
5 Whys Analysis Template and Usage Tips
5 Whys Analysis Template Structure
Problem Description: [Clearly describe the problem phenomenon, including 5W2H]
Why1: Why... → [Cause 1]
Why2: Why [Cause 1]... → [Cause 2]
Why3: Why [Cause 2]... → [Cause 3]
Why4: Why [Cause 3]... → [Cause 4]
Why5: Why [Cause 4]... → [Root Cause]
Immediate Action: [Immediate containment to protect the customer]
Permanent Action: [Solution addressing the root cause]
Action Verification: [How to verify the effectiveness of the actions]
Practical Tips
On-site, on-the-spot, in-reality—go to where the problem occurred, observe the actual items, and understand the real situation. 5 Whys is not about brainstorming in the office; it is about using facts from the field.
5 Whys Application Recommendations
- Cross-functional team participation for multi-perspective analysis.
- Update the analysis results to the FMEA and control plan.
- Build a 5 Whys case library for training materials.
- For complex issues, use in conjunction with a fishbone diagram.