Problem Solving & Quality · Root Causes

Three-Path Whys

Run three separate why-chains: why it occurred, why it was not detected, and why the system allowed both. Each path gets its own countermeasure.

Time1 h
FormatTeam
StageRoot Causes

Three-Path Whys: what it is and why it works

Three-Path Whys runs three separate why-chains for the same problem. The occurrence path asks why the defect or failure was created, down to a technical root cause. The non-detection path asks why the controls in place (inspection, test, alarm) did not catch it before it reached the customer or caused harm. The system path asks why the management system (FMEA, standards, training, change control) allowed both gaps. Each path ends in its own countermeasure with its own owner.

A single why-chain almost always follows the occurrence path: the machine, the tool, the material. That fixes today's cause but leaves open the detection weakness and the system gap that will let the next, different defect escape the same way. Splitting the analysis makes those gaps explicit and gives three levers instead of one. The approach is common in automotive supplier quality and fits the 8D logic, where customers expect escape points and systemic causes to be addressed alongside the technical cause. The non-detection countermeasure is often the fastest to put in place and can protect the customer while the occurrence fix is engineered. The system countermeasure usually lands in the control plan, the FMEA or a procedure.

What you need

A verified deviation statement and the point where the defect was found
The control plan or inspection plan in force
The process FMEA and relevant procedures such as change control and training
Results of a single why-chain or fishbone, if already done
A team covering production, quality and engineering

What you get

An occurrence root cause and its countermeasure
A non-detection root cause and its countermeasure
A systemic root cause and its countermeasure
Identified updates to the control plan, FMEA or procedures
An owner and due date for each of the three actions

When to use it

When the analysis stops at the machine and never asks why inspection let the defect through.

How to do it, step by step

Draw three columns: Occurrence, Non-detection, System.
Occurrence: ask why the defect or failure was created, down to a technical root cause.
Non-detection: ask why the controls in place — inspection, alarm, test — did not catch it.
System: ask why the management system — FMEA, standard, training, change control — allowed both gaps.
Assign one countermeasure per column, with an owner, so the fix covers creation, escape and system.

Worked example: Missing O-ring in a fuel-line connector

Illustrative scenario — figures are realistic but not from a real company.

A tier-2 automotive supplier ships quick-connect fuel-line fittings that each carry two O-rings. The customer's leak test finds three fittings with the second O-ring missing in a 10,000-piece shipment, and the customer requests an 8D with all escape points addressed.

Occurrence: the O-ring feeder bowl had jammed, and during manual recovery the operator skipped one groove. The jam traced to a new O-ring source with a slightly different surface finish, and no recovery method was defined.
Non-detection: the vision system checked only the first groove. The second-groove check had been dropped from the camera program during a part modification two years earlier, and the edit was never validated against the control plan.
System: the process FMEA had no failure mode for manual recovery after a feeder jam, and the change-control procedure covered neither vision-program edits nor changes of component source.
Countermeasures: occurrence, a modified feeder track plus a written recovery procedure with a post-recovery check; non-detection, the two-groove vision check restored and validated with master parts; system, the PFMEA updated for recovery modes and change control extended to vision programs and component sources.

Result. The restored vision check went live within two days and protected the customer immediately, while the feeder modification followed three weeks later. No escapes were recorded in the following six months. The team noted that fixing the occurrence cause alone would have repaired the feeder but left a half-blind camera waiting for the next defect.

Open it in the FieldKit Problem Solving app → Get the Problem Solving template pack — join the waitlist

Common pitfalls and how to avoid them

Collapsing the three paths into one.Keep three columns and require a verified answer in each before closing.
Blaming inspectors on the non-detection path.Ask what made the defect hard to detect (method, equipment, criteria, sampling), not who missed it.
A system path that ends in 'retrain everyone'.Find the missing or weak element of the system, such as FMEA coverage, a standard or change control, and fix that element.
Countermeasures without owners.Assign one owner and one date per path and track the three actions separately.

Frequently asked questions

What is a 3-legged 5 Why?

It is a 5 Whys analysis split into three legs: why the problem occurred, why it was not detected, and why the quality or management system allowed it. Each leg is followed to its own root cause and gets its own corrective action. The approach is widely used in automotive supplier quality to deal with escapes and systemic weaknesses, not just the technical cause.

Why analyze non-detection separately?

Because the cause that created a defect and the cause that let it escape are usually different. Fixing only the occurrence cause leaves the detection gap open for the next, different defect. Analyzing detection on its own often reveals a quick way to protect the customer, such as a restored check or a better test point, while the longer-term occurrence fix is engineered.

What counts as a systemic root cause?

A weakness in how the organization manages its processes that allowed the problem to happen and to escape: a failure mode missing from the PFMEA, a change-control procedure that did not cover a type of change, an unclear standard, or a training system that does not confirm skills. A systemic cause could usually produce other problems too, which is why fixing it has wider value.

Origin

Separate occurrence / non-detection / systemic analysis — automotive quality practice (often called “3-legged” or “3×5 Why”); no single author.

Used in these playbooks

Customer complaint closure 4 weeks

Four weeks to answer a complaint the way customers expect: a structured 8D, a clean problem statement, causes of occurrence and escape, an error-proof fix and deployment to sister lines.

Related methods

More in “Root Causes”

List the possible causes, dig down the chains and prove the real one before acting.