Definition
5-Why Analysis is a root cause investigation technique that traces a problem back to its fundamental cause by repeatedly asking “why?” When a problem occurs, you ask why it occurred. The answer becomes the next problem statement, and you ask why again. You continue until you reach a root cause that, if addressed, would prevent the problem from recurring.
The number five is a guideline, not a rule. Some problems require three whys. Others require seven. The point is not to count questions but to keep asking until you reach a cause that is actionable and fundamental — one that, if addressed through a countermeasure, would prevent recurrence.
Taiichi Ohno described 5-Why as the basis of Toyota’s scientific approach. In his 1978 book, he gave the classic example:
Problem: A machine has stopped.
- Why? — There was an overload and the fuse blew.
- Why? — The bearing was not sufficiently lubricated.
- Why? — The lubrication pump was not pumping sufficiently.
- Why? — The shaft of the pump was worn and rattling.
- Why? — There was no strainer and metal scrap got in.
Without asking why repeatedly, a maintenance worker would replace the fuse (addressing the symptom). The machine would fail again. By asking five times, you reach the root cause — the lack of a strainer — and the countermeasure (installing a strainer) prevents recurrence.
Japanese Origin
なぜなぜ分析 (nazenaze bunseki) is the formal Japanese name:
- なぜ (naze) — “why?” (repeated twice for emphasis: なぜなぜ = “why-why”)
- 分析 (bunseki) — analysis
The repetition of なぜ gives the technique its name: not a single “why” but a persistent, iterative “why-why-why” that refuses to stop at surface explanations. In Japanese, the repetition conveys both the method and its relentless character.
At Toyota, the phrase なぜを5回繰り返せ (naze wo gokai kurikaese, “repeat ‘why’ five times”) is attributed to Ohno and has become one of the most quoted TPS principles.
History at Toyota
Ohno developed 5-Why analysis as a practical discipline on the shop floor during the 1950s-60s. It was not derived from academic methodology — it was born from Ohno’s insistence that supervisors and workers truly understand why problems occur rather than accepting surface-level explanations.
The technique reflects Ohno’s broader philosophy: problems are treasures, but only if you understand their root causes. A problem that is patched without understanding is a problem that will recur. A problem whose root cause is identified and addressed permanently is an opportunity that makes the system stronger.
5-Why became embedded in Toyota’s problem-solving hierarchy:
- Daily problems — team leaders and supervisors use 5-Why on the spot, at the genba, when abnormalities are detected
- A3 problem solving — the root cause analysis section of an A3 typically includes a 5-Why chain
- TBP Step 4 — the root cause analysis step of Toyota Business Practice uses 5-Why as the primary investigation technique
- QC circles — small groups use 5-Why alongside cause-and-effect diagrams to investigate quality problems
How It Actually Works
5-Why is deceptively simple. Asking “why” is easy. Asking “why” well is difficult.
Rules for effective 5-Why:
Each answer must be based on fact, not assumption. The answer to each “why” must be verified through direct observation, measurement, or data — not through opinion, experience, or plausible-sounding explanations. This is the most violated rule. Teams frequently build chains of speculation: “Why? Because it probably…” This produces a logical-sounding chain that reaches a plausible but incorrect root cause.
Go to the genba for each “why.” At Toyota, 5-Why analysis is conducted at the place where the problem occurred, looking at the actual situation. It is not a conference room exercise. Each “why” should drive you to look more closely at the physical reality.
Stay on one causal chain. When you ask “why,” there may be multiple contributing causes. Choose the most significant one and follow it. Do not branch into multiple paths simultaneously — this dilutes focus and produces analysis paralysis. If multiple causes are significant, run separate 5-Why analyses for each.
Stop at a root cause you can act on. The analysis is complete when you reach a cause that is (a) fundamental enough that addressing it prevents recurrence, and (b) within your ability to change. Continuing beyond this point reaches causes that are philosophical (“why do machines wear out?”) or outside your control (“why does the supplier use that material?”).
The countermeasure must address the root cause, not the symptom. If your 5-Why identifies the root cause as “no strainer on the pump,” the countermeasure is installing a strainer — not replacing the fuse, not lubricating the bearing, not repairing the pump shaft. Each of those addresses an intermediate cause, not the root cause.
Common Mistakes
Accepting assumptions as answers. The single most common failure. “Why did the part get scratched?” — “Because the operator wasn’t paying attention.” This is not a verified fact; it is a blame statement. A factual answer requires going to the genba, observing the process, and understanding what physically caused the scratch.
Stopping too early. Replacing the fuse solves the immediate symptom. Lubricating the bearing solves the proximate cause. Installing the strainer solves the root cause. Most organizations stop at the fuse (first why) or the bearing (second why) because those are quick, comfortable fixes. The root cause requires more investigation and often a systemic change.
Branching into multiple chains. “Why? Because of A, B, and C.” Following all three simultaneously produces a tree diagram, not a 5-Why analysis. The discipline is to identify the primary cause and follow it. Secondary causes can be investigated in separate analyses.
Using 5-Why in a conference room. If the team is debating “why” without looking at the actual process, they are guessing. 5-Why requires genba, genbutsu (the actual thing), and genjitsu (the actual facts). Every “why” should be answered with something observed or measured, not something assumed.
Blaming people instead of the system. If the 5-Why chain ends at “the operator made an error,” the analysis is incomplete. Why was the operator able to make that error? Is there a poka-yoke that could prevent it? Is the standardized work unclear? Is the training insufficient? Ohno’s philosophy is that the system should prevent errors, not that people should be blamed for making them.
Treating “five” as a magic number. Some problems need three whys. Others need eight. The number five is a heuristic that pushes teams past the shallow answers they would normally accept. If you have truly reached a root cause in three whys, stop. If you have not reached one after five, keep going.