Verify the root cause by tracing back up the chain
After reaching a root, work back up: does each "because" in the chain make logical sense?
Why it works
Five Whys chains can drift from the actual causal sequence into plausible-sounding but incorrect reasoning. The verification test is simple: read the chain upward using "therefore": "root cause X, therefore level-4 condition, therefore level-3 condition, ... therefore the original problem." If each "therefore" is logically sound and empirically plausible, the chain is valid. If any step requires a leap or an assumption, the chain needs refinement.
How to do it
- Write the completed why-chain from root to problem.
- Read it in reverse using "therefore": "[root] therefore [next level] therefore … therefore [problem]."
- At each step, ask: "Is this a necessary and plausible consequence of the preceding step?"
- Where the chain breaks, restart the why-chain from that break point.
Evidence
Reverse chain verification is an internal consistency check used in formal root cause analysis (RCA) processes in healthcare and engineering. It applies basic logic: if the causal claim is valid, it should run in both directions. (mechanistic)
Logical coherence does not guarantee empirical accuracy; a chain can be internally consistent but wrong if any factual premise is incorrect. Verification should include empirical checks, not just logical ones.
Common mistake
Skipping the verification step because the chain "feels right" — chains that feel right are exactly the ones most likely to have a motivated bias built in.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Five Whys
- State the problem precisely before asking the first why
A vague problem statement produces vague root causes — be specific about what happened.
- Follow the causal chain until you reach a changeable cause
Keep asking "why?" until you reach something you can actually fix.
- Branch the chain when you find multiple causes
When a "why" has two or more true answers, follow each branch separately.
- Distinguish human error from system conditions
When a person is the proximate cause, ask why the system allowed the error to occur.
- Design the fix to prevent recurrence, not just to recover from this instance
Ensure the root-cause fix eliminates the cause permanently, not just this occurrence.