5Why Analysis: How to Ask the Right Questions to Find the Root Cause
The surface cause of a problem is easy to identify, but the true cause often lies beyond the 5th "why."
Article Directory
1. What is 5Why Analysis?
5Why 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.
Phenomenon ≠ Cause. Solving only the surface phenomenon will lead to recurring issues. Only by identifying the root cause can the problem be completely resolved.
2. Core Principles of 5Why
- Get to the Root: Continue asking "why" until a cause that can be addressed is found (usually a process, standard, or management issue).
- Fact-Based: Each "why" must be based on facts, not assumptions.
- Avoid Blame: Do not attribute the problem to individuals; focus on systemic and process-level causes.
- Distinguish Between Root Cause and Immediate Cause: The immediate cause is the event that directly leads to the problem, while the root cause is a systemic defect.
3. Practical Case: From Surface to Root Cause
Problem Phenomenon: A 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 seized, increasing the load.
Why4: Why was the bearing seized?
→ Insufficient lubrication, leading 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 equipment maintenance procedures—no regular inspection and maintenance system for the lubrication pump was established.
Temporary Measures: Replace the fuse and bearing, add lubricating oil, and resume production.
Permanent Measures: Establish a daily inspection system for the lubrication pump and integrate it into TPM management.
Problem Phenomenon: 3% of products have surface scratches.
Why1: Why are there scratches?
→ The conveyor belt guard scratched the products.
Why2: Why did the guard scratch the products?
→ The edges 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?
→ The equipment maintenance standards were incomplete and did not identify risk points.
Root Cause: The equipment maintenance standards lack a process for identifying key risk points.
Permanent Measures: Update the equipment inspection standards to include the guard; establish a PFMEA review mechanism to regularly identify risk points.
4. Common Pitfalls and How to Avoid Them
- Pitfall 1: Stopping Too Early
→ Concluding after only 2-3 "whys." Countermeasure: Continue asking "why" until a systemic measure can be taken (usually 5-7 layers). - Pitfall 2: Blaming Individuals
→ "Because of employee error." Countermeasure: Ask "why" the employee made the error—insufficient training? Unclear work instructions? Fatigue? - Pitfall 3: Guessing Instead of Fact-Checking
→ 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 possible causes and verify them one by one. - Pitfall 5: Confusing Cause with Phenomenon
→ Using the phenomenon as the cause. Countermeasure: Each "why" must be answered with a "cause" and not repeat the phenomenon.
5. 5Why Analysis Template and Usage Tips
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]
Temporary Measures: [Immediate containment to protect the customer]
Permanent Measures: [Solution addressing the root cause]
Measure Verification: [How to verify the effectiveness of the measures]
Practical Tips: Go to the scene, observe the actual items, and understand the real situation. 5Why is not about brainstorming in the office but about using facts from the field.
- Involve cross-functional teams for multi-perspective analysis.
- Update the analysis results in FMEA and control plans.
- Build a 5Why case library for training materials.
- For complex issues, combine 5Why with a fishbone diagram.