Definition
5-Why analysis is a root cause analysis technique that drills from a problem’s symptom to its underlying cause by asking ‘why?’ iteratively, typically five times. Developed by Sakichi Toyoda for Toyota and central to the Toyota Production System.
The number five is a heuristic, not a rule. The technique stops when further ‘why?’ questions stop producing meaningful information, usually around five iterations but sometimes three or seven depending on the problem. 5-Why is the most widely taught root cause analysis tool in lean and Six Sigma training.
A team starts with a clear problem statement and asks ‘why?’ to expose the immediate cause. They ask ‘why?’ again about that cause, and so on, until further questioning yields no useful information. The chain typically runs five layers deep, which gives the technique its name.
A canonical example from Taiichi Ohno’s Toyota Production System starts with a machine that stopped working:
The root cause is the worn pump shaft, so the corrective action targets pump maintenance rather than fuse replacement.
5-Why is the most accessible root cause analysis technique on the shop floor: it requires no software, no specialised training, and produces a documented chain of reasoning that an auditor or quality manager can review. It is the default analysis step inside the 8D methodology (D4), inside CAPA investigations, and inside lean A3 reports.
The American Society for Quality lists 5-Why among the most frequently used quality tools because of its low cognitive overhead and immediate visual output, and ISO 9001:2015 clause 10.2 recognises it as one acceptable method for determining the causes of a non-conformity.
Three patterns recur when 5-Why fails to find the true root cause. First, the chain stops at a human factor (‘the operator made a mistake’) rather than the system factor that allowed the mistake; a properly executed 5-Why drills past the human action to the missing control.
Second, the technique assumes one cause per layer, which misses problems with multiple contributing factors. Third, the depth of the analysis depends on the questioner’s process knowledge, so an analyst without that expertise will hit a ‘because that is how it works’ wall and stop short. Combining 5-Why with fishbone or fault-tree analysis mitigates the second and third pitfalls.
References