The 5 Whys Method
Sakichi Toyoda / Toyota Production System · 1930
"Repeatedly asking 'why' about a problem — typically five times — peels back surface symptoms to reach the actual root cause, preventing teams from implementing fixes that address symptoms while leaving the underlying issue free to resurface."
The first answer to 'why did this fail' is almost never the real cause. It's usually just the most visible symptom.
Originating in the Toyota Production System, the method is mechanically simple: state the problem, ask why it happened, then ask why that answer happened, repeating roughly five times until you reach a cause that's actually actionable — usually a process or systemic gap rather than an individual mistake. A car won't start → the battery is dead → the alternator isn't charging it → the alternator belt is broken → the belt was never replaced on schedule → there's no preventive maintenance schedule. The fix for that last answer prevents recurrence; the fix for the first answer (a jump-start) doesn't.
In the 5 Whys example (car won't start), why is fixing the alternator belt still an incomplete solution?
Read more about the topic
The explanation above is written with AI assistance. These are the originals — go to them to check it.
- 5 WhysInteraction Design Foundation
To Solve a Tough Problem, Reframe It
"Many 'unsolvable' problems are actually poorly framed ones — changing the question you're asking often surfaces a solution that was invisible under the original framing, making reframing a higher-leverage move than harder analysis of the original question."