What Is 5 Why Analysis?

State the problem as a fact: identify the product or process, defect, timing, location and detection point. Ask why that fact occurred, then ask why each answer was possible. Every link should be a condition the team can inspect, measure or test—not an opinion or an explanation that simply renames the symptom.

The number five is a useful prompt, not a scientific rule. A meaningful chain may stop after three questions or require more than five. Stop when the next answer would be speculation, when the team has reached a controllable condition, or when the evidence shows the chain needs to branch.

A final assembly fails functional test because a connector is not fully seated. The team finds that the operator could not reliably confirm insertion, the work instruction relied on visual judgement, and the process had no verified seating control. The final statement is not proof by itself. The team must check records, observe the work, test the suspected control and confirm that the failure changes as predicted.

This is why a 5 Why chain should be read backwards before action is taken: each proposed cause must plausibly produce the effect above it. If one connection is unsupported, investigate that link rather than continuing deeper.

5 Why is a useful starting point when the event is bounded, a single causal path is plausible and the team can collect evidence for each link. It works well for a focused defect, an escaped inspection condition, a missed handover or a repeatable process deviation.

It is not a substitute for broader exploration when several functions, materials, settings or process steps may contribute. In that situation, use a Fishbone Diagram to map candidate cause families first, then use 5 Why to investigate a selected branch.

• Stopping at a symptom such as “operator error” instead of asking what made the error possible.
• Writing a desired action as though it were a cause.
• Forcing exactly five questions when evidence says the chain has ended or branched.
• Using a plausible narrative without records, observation, testing or controlled verification.
• Treating the final Why as a confirmed root cause before it has been tested.

5 Why helps a team formulate and examine a causal hypothesis. It does not perform containment, validate corrective action, prevent recurrence or close a customer complaint. For those broader responsibilities, use a structured 8D investigation.

Within 8D, 5 Why commonly supports D4 root-cause analysis. Read 8D vs 5 Why for the different scope of the two approaches, and use D4 Root Cause Analysis for the distinction between a candidate and a proven cause.