Five Whys Without the Theater
A practical root cause analysis approach that works on the shop floor, not just in post-mortem meetings.
The Five Whys is a simple tool. The hard part is using it without turning it into blame theater.
Keep it on the process
Each “why” should point to a process gap, not a person:
- Bad: “Why did the defect happen? Because John wasn’t paying attention.”
- Better: “Why wasn’t the check standard visible at the point of work?”
Stop at the actionable cause
You don’t always need exactly five whys. Stop when you reach a cause you can change with a countermeasure—a poka-yoke, a visual standard, a training update, or a layout fix.
Document lightly
A one-page A3 or a short log entry is enough. The goal is faster recurrence prevention, not a binder full of RCA forms nobody reads.
Applied IE means tools that get used where the work happens. Five Whys works when it’s quick, honest, and tied to a fix you can verify on the next shift.