Five Whys vs Fishbone: When Each Wins

Two root cause techniques. The decision rule by incident type.

Five Whys

Five Whys is the linear root-cause technique. Best for incidents with clear cause-and-effect chains: service down, database unreachable, connection pool exhausted, etc. Each “why” deepens until the chain reaches an actionable cause.

• Linear causal chain. “Service down, DB unreachable, pool exhausted” walkback. Each “why” deepens.
• Best for clear cause and effect. Single-failure-mode case per incident. Linear technique fits linear failures.
• Documented chain per investigation. Captured why-by-why log per investigation. Supports later review.
• Named stopping point. “This is actionable” terminus per investigation. Catches over-chaining into philosophy.

Fishbone

Fishbone (Ishikawa) fits multi-factor incidents where people, process, technology, and environment all contributed. The diagram captures the tangle visually and resists the temptation to oversimplify into a single root cause.

• Multiple contributing factors. People, process, technology, environment branches. Each carries factors.
• Best for complex incidents. Many-factor case per incident. Fishbone resists oversimplification.
• Facilitated session. Named facilitator per fishbone. Supports cross-functional contribution.
• Published diagram. Visual artefact per fishbone. Broader audience review without re-reading the postmortem.

Limits

Both techniques have limits. Five Whys can stop too early or chain into philosophy; Fishbone resists single-cause clarity even when one cause genuinely dominates. The discipline is picking the technique that matches the incident shape.

• Five Whys stops at five. Depth limit per investigation. Some chains need more; some need fewer.
• Fishbone is exploratory. No-single-root expectation per investigation. Do not expect convergence.
• Documented technique choice. “Why this technique” note per incident. Catches mismatched techniques.
• Postmortem section. Explicit technique reference per postmortem. Supports replication across teams.