5-Why Analysis
5-Why is a root cause analysis technique that asks 'Why?' repeatedly until the fundamental cause of a problem is uncovered. Simple, fast, and effective for most process problems.
The 5-Why method was inspired by Sakichi Toyoda's questioning approach and later popularized by Taiichi Ohno as a core practice at Toyota. The principle: When a problem occurs, ask 'Why did this happen?' Then ask 'Why?' again for each answer, typically five times, until you reach the root cause.
The power of 5-Why lies in preventing symptom treatment. Most organizations fix the immediate symptom and move on -- only to see the problem return. 5-Why forces you past the symptoms to the underlying systemic issue.
Five is a guideline, not a rule. Some problems need only 3 whys to reach the root cause; others need 7 or more. The point is to keep asking until you reach a cause that, if eliminated, would prevent recurrence.
A common pitfall: The chain of whys can branch in multiple directions. When this happens, follow the branch with the strongest evidence. Better yet, combine 5-Why with data analysis to verify each step rather than relying on assumptions.
Practical Example
Problem: Machine stopped. Why? Fuse blown. Why? Motor overloaded. Why? Bearing seized. Why? Insufficient lubrication. Why? No preventive maintenance schedule. Root cause: Missing PM schedule. Fix: Implement a maintenance schedule with lubrication intervals. Cost: minimal. Impact: Eliminates the class of failures, not just this one instance.
How Leanshift Helps
Leanshift's coaching questions naturally guide through the 5-Why logic: 'What did you expect? What actually happened? Why is there a gap?' This structured reflection ensures root causes are found, not just symptoms.
Frequently Asked Questions
Why exactly five whys?
Five is a rule of thumb, not a strict requirement. Taiichi Ohno observed that five levels of questioning usually reach the root cause. Stop when you find a cause you can act on and that would prevent recurrence.
What if different people give different answers?
This is common and actually valuable -- it reveals different perspectives. Verify each chain with data. The correct path is the one supported by evidence from the actual process, not by opinion or hierarchy.
Can 5-Why be used for complex problems?
For simple cause-effect chains, 5-Why works excellently. For complex problems with multiple interacting causes, combine it with Ishikawa diagrams or fault tree analysis to cover all branches systematically.
Related Terms
Kaizen
Kaizen means 'change for the better' and describes the philosophy of continuous, incremental improvement by all employees -- every day, everywhere.
PDCA Cycle
PDCA (Plan-Do-Check-Act) is the fundamental improvement cycle: Plan, Execute, Verify, Standardize. It structures every improvement process into four clear phases.
Ishikawa / Fishbone Diagram
The Ishikawa diagram organizes potential causes of a problem into categories along a fish-bone structure. It ensures systematic root cause analysis instead of jumping to conclusions.