The archive · Work & Ways of Doing · Operational decision · 1950s–1978
Toyota's Five Whys: ask why again until the root cause, not the symptom, gets fixed
When machines kept failing, Taiichi Ohno had Toyota ask 'why' five times instead of swapping fuses — chasing each breakdown to a root cause that can't recur.
Toyota Motor Corporation
What it had to solve
As machine shop manager at Toyota in the 1950s, Taiichi Ohno watched the same breakdowns return again and again: his people fixed the first cause they found — swapped the fuse — and the failure came back. He trained himself and his teams to keep asking why until they reached a cause they could eliminate.
How it works
Taiichi Ohno built the Toyota Production System around the idea that problems are opportunities, and he had a blunt observation to prove it: as machine shop manager in the 1950s he saw machines break down, his people attach a Band-Aid — replace the fuse, restart the line — and the same failure come back. Stopping at the first level of cause guaranteed recurrence.
His invention was a discipline, not a device: whenever an abnormality occurred, ask 'why' five times, letting each answer feed the next question until the causal chain reached a root cause. In his classic example the machine stopped because a fuse blew; the overload came from an unlubricated bearing; the pump was not drawing lubricant; its shaft was worn and rattling; and the shaft wore out because metal chips entered the pump — there was no strainer. The fix was a strainer, and the failure could not return.
The specific number five was never the point. Ohno trained his people to follow the causal chain as far as it needed to go — sometimes three whys, sometimes eight — and to check the chain by running it backwards: because there was no strainer, chips damaged the shaft, the pump stopped drawing oil, the bearing starved, the machine overloaded and the fuse blew. The method spread with lean thinking and remains the standard first tool of root-cause analysis wherever quality problems are taught.
Why it lands
- It moves blame off people and onto process: the chain ends at a missing strainer, not at a careless worker.
- It converts a rare skill — root-cause thinking — into a repeatable routine any team can run in minutes at the place the failure happened.
- Because five is a prompt rather than a limit, the method stays honest: keep asking until the cause that lets the problem return is found and removed.
- It makes the fix cheap and the lesson permanent: a strainer costs less than a lifetime of blown fuses, and the countermeasure is the point of the whole exercise.
What it did
Five Whys became the root-cause habit of Toyota's problem-solving culture and the first lean method learners meet when a quality problem appears. Its endurance rests on being content-free — no statistics, no software, just a question repeated on the shop floor until the cause that lets failure recur is found and removed.
What you can take
Never fix the first cause you find: every 'why' buys one more layer of understanding, and only the final answer — the cause that lets the failure recur — deserves the countermeasure.
Since then
Five Whys travelled with Toyota's production system into lean manufacturing worldwide and into quality, safety and software teams that borrowed it. By 2007, Toyota managing director Teruyuki Minoura, who had trained under Ohno, warned publicly that the method was underperforming in many hands: teams answered from deduction rather than direct observation, reeling off invented causes. Toyota's answer was training — ask five whys again for each cause, grounded in observation. The tool stayed deliberately simple, which is why it still opens root-cause problem-solving beyond the factory.
Sources
- Clarifying the '5 Whys' Problem-Solving Method
- 5 Whys — What is it?
- Teruyuki Minoura (Toyota Exec) Talks About Problems with 5-Whys
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card