Five Whys Trap

Deeper not better.

Overview

The Five Whys trap is recognising that linear root-cause analysis often misses the real systemic issues. The framework assumes a single causal chain; production incidents almost never have one. Going deeper down a single chain feels rigorous but tends to converge on a person rather than a system, which is usually wrong on both the analysis and the cultural axis.

• Linear-chain bias. Five Whys assumes one cause feeds the next. Real incidents have multiple parallel contributing factors.
• Convenient stopping point. The chain often ends at a person ("the engineer didn't notice X") rather than a system ("the alerting threshold did not catch X"). Wrong scope, wrong fix.
• Single-root-cause illusion. Picking one root cause hides the others. Recurrence comes from the unaddressed factors.
• Better tools available. Causal diagrams, fishbone, why-because graphs all surface multiple parallel factors. Match the tool to the actual shape of the failure.

The approach

Identify multiple contributing factors, draw a causal diagram, peer-review the analysis, stop at systems rather than people, document the team's RCA framework so reviewers can hold each other to it.

• Multiple contributing factors per PM. Surface every factor that meaningfully contributed. The fix list is then comprehensive rather than convenient.
• Causal diagram. Visual map of how factors interacted to produce the incident. Reveals leverage points the linear chain hides.
• Peer-reviewed RCA. Another senior reviewer reads the analysis before it lands. Catches the "stopped at the person" mistake before it becomes culture.
• Stop at systems plus documented framework. System-level root cause is the standard; team's RCA approach lives in writing so reviewers cite it explicitly.

Why this compounds

Each correctly analysed PM compounds the team's RCA muscle. Multi-cause thinking spreads to design reviews, to capacity planning, to architectural debates. By year two, "what are the contributing factors" is the team's first question rather than "what's the root cause."

• Better RCA. Multi-cause analysis produces real understanding. Fixes target the actual mechanism.
• Better culture. System-level analysis avoids blame. Retention follows.
• Better follow-through. Right root cause produces right action. Recurrence drops.
• Year-one investment, year-two habit. First multi-cause analysis is the investment; subsequent ones run on the framework.