5 Whys

The method was originally developed by Sakichi Toyoda, the founder of Toyota Industries. It later became a cornerstone of the Toyota Production System, developed under the leadership of Taiichi Ohno. Ohno described the 5 Whys approach as the foundation of Toyota's scientific methodology, emphasizing that by repeating "Why?" five times, the nature of the problem as well as its solution becomes clear.

A classic example documented by Ohno illustrates how an unexpected machine stoppage is traced backward to its physical origin:

1. Why did the machine stop? An electrical overload blew the fuse. The investigator verifies this by checking the blown fuse in the control panel and inspecting the tripped circuit drive.
2. Why was there an overload? The bearing was not lubricated properly. The investigator checks the physical bearing, observing dry metal, heat discoloration, and scoring.
3. Why was the bearing not lubricated properly? The lubrication pump was not delivering enough oil. The investigator measures the oil flow at the delivery point against the pump's rated output.
4. Why was the pump delivery inadequate? The pump shaft was worn and rattling. The investigator removes the shaft from its housing and measures it with a micrometer.
5. Why was the shaft worn? There was no strainer attached, allowing metal scrap into the pump. The investigator inspects the empty filter housing and finds metal debris in the oil reservoir.

Although the structure consists of simple questions, the method relies entirely on factual verification. Each causal link must represent an observable, verified condition inspected at the gemba—the actual physical location where the work occurs. As one of the most accessible tools in root cause analysis, 5 Whys bridges the gap between identifying an immediate symptom and implementing a lasting countermeasure.

The technique applies equally well to administrative, service, and healthcare workflows. For instance, if a patient experiences a 40-minute delay for a hospital discharge summary, asking why reveals that the physician has not signed the document. Asking why further reveals that the physician is currently conducting morning ward rounds because the pharmacy review queue only delivers charts at 11am. The terminal answer identifies a scheduling convention that was intentionally designed and can therefore be redesigned.

If a causal chain reaches its root cause in three steps, forcing additional questions creates artificial complexity. Conversely, complex issues may require more than five steps. In a 2017 study published in BMJ Quality & Safety, Alan J. Card noted that "the arbitrary depth of the fifth why is unlikely to correlate with the root cause."

To determine whether an investigation is complete without relying on an arbitrary step count, three validation criteria should be applied:

1. The reverse logic test (the "therefore" test): Reading the completed chain in reverse order using the word "therefore" must form a logical causal sequence. For example: "A strainer was fitted, therefore metal scrap could not enter the pump, therefore the shaft did not wear down, therefore the pump delivered adequate oil, therefore the bearing remained lubricated, therefore the motor did not overload, therefore the fuse did not blow, therefore the machine continued running." If any step requires an unstated assumption to make sense, the causal logic is flawed.
2. Identification of a system or process decision: Physical failures are almost always the result of procedural, design, or organizational choices. Identifying that a strainer was missing points directly to an engineering specification or assembly validation step that was omitted.
3. Actionable sphere of influence: The terminal cause must represent a variable the team has the authority and ability to modify. When a contributing factor lies entirely outside the team's control—such as a statutory regulation or an upstream supplier's internal design—the team should establish countermeasures at the deepest point within its operational boundary.

This variability is mathematical. If an investigator considers three plausible hypotheses at each step of a five-step chain, there are 3 × 3 × 3 × 3 × 3 = 243 possible causal branches. Only one of these sequences accurately describes the physical events that occurred. Relying on conjecture in a meeting room gives a team roughly a 1 in 243 (0.4 percent) probability of selecting the true path purely by chance.

Teruyuki Minoura, former managing director of Toyota, highlighted this limitation by noting that ungrounded 5 Whys exercises lead to non-repeatable outcomes. The solution is empirical verification: at every step, investigators must inspect the physical workspace, collect data, and eliminate unverified branches before asking the next question.

Who invented the 5 Whys?

Sakichi Toyoda, who founded Toyota Industries, developed it. Taiichi Ohno spread it through the Toyota Production System and called it the basis of Toyota's scientific approach. The example everyone learns is Ohno's: a machine stopped, traced in five rungs to a missing pump strainer.

Why five whys and not four or six?

Five describes Ohno's machine example, where the causal path happened to be five links long. It is a count, not a stop rule. Stop instead when the chain reads back with "therefore" at every link, when the last rung is a decision somebody made, and when you still hold the lever to change it.

What is the difference between 5 Whys and a fishbone diagram?

A fishbone diagram maps width. It lists every category of cause that could contribute. A 5 Whys goes down one path in depth. Use the fishbone when several conditions had to line up, find the paths that carry real evidence, then run a why-chain down each of those.

Can two people run 5 Whys on the same problem and reach different causes?

Yes, and it is the method's best-known weakness. Teruyuki Minoura raised it from inside Toyota. If each why has three plausible answers, five rungs allow 243 different chains, and only one matches the evidence. The fix is to verify every rung where the work happens before you write it down.

Is 5 Whys the same as root cause analysis?

No. Root cause analysis is the discipline. 5 Whys is one of its simplest instruments. It sits inside larger methods, such as the analysis box of an A3 or the Check step of PDCA, instead of replacing them.