Root Cause Analysis and the 5 Whys

Description

Iteratively asks why a problem occurred to move from symptoms to systemic causes, ideally with evidence at each step and multiple branches.

The 5 Whys asks 'why' repeatedly until reaching a cause that, if fixed, prevents recurrence. In disciplined form, each answer must be verified with evidence, branches are allowed when there are several causes, and the analysis stops at a cause within the organisation's control, usually a process or design decision rather than a person. Formal RCA (as in healthcare, per The Joint Commission) adds timeline reconstruction, cause-and-effect charting and action hierarchies that favour design changes over retraining. The method is vestigial in UX: teams ask 'why' five times in a meeting with no evidence, follow a single linear chain and stop at 'user didn't read'. Restoring the evidence and branching rules makes it rigorous.

Attributes

Loss type
Vestigial
Data
Mixed
Effort
Days

Steps

  1. State the problem precisely with measurable symptoms, scope and time window.
  2. Reconstruct a factual timeline from logs, recordings and interviews before any causal discussion.
  3. Ask why the problem occurred and record each candidate cause, requiring evidence (data, observation, reproduction) for every link.
  4. Allow branching where several causes contribute, and continue each branch until reaching a controllable process or design cause, typically 3-7 levels.
  5. Reject causes that blame individuals; reframe as 'why was this error possible and not caught'.
  6. Select corrective actions using an action hierarchy (forcing functions and automation stronger than warnings and training) and set a verification metric.

Sources

  • Ohno, Toyota Production System: Beyond Large-Scale Production (1988 English ed.)
  • Card, The problem with '5 whys' (2017), BMJ Quality & Safety
  • The Joint Commission, Framework for Root Cause Analysis and Corrective Actions

Also known as

  • RCA
  • 5 Whys
  • Five whys
  • Causal analysis
  • Ask why

Categories

  • Accessibility
  • Human Factors & Error