Root Cause Analysis (RCA)
Root Cause Analysis (RCA) is a systematic process for identifying the underlying reasons why an event deviated from a plan, distinguishing between immediate, contributing, and root causes. It emphasizes looking beyond individual actions to understand systemic factors, using tools like the '5 whys', bowtie diagrams, and fault trees to prevent recurrence.
THE IDEA
Root Cause Analysis
Effective root cause analysis (RCA) relies on clearly distinguishing between immediate, contributing, and root causes. Root causes are the underlying reasons why something did not go according to plan, and they always depend on the specific context and facts of a situation. Rigorous fact-finding, the development of detailed timelines, and techniques such as the Bowtie diagram are fundamental to a proper investigation. The Bowtie diagram helps map out objectives and threats alongside the preventative, detective, and recovery measures designed to keep operations on track. Identifying root causes should guide changes that prevent a recurrence or limit its consequences.
A common temptation is to focus on the people involved when an incident occurs, but RCA encourages looking beyond the “who” to understand the “why” at a systemic level. This systemic perspective is a hallmark of High-Reliability Organisations (HROs), which put in place a deliberate range of controls to minimise the chance of adverse events. HROs also apply double-loop learning: they challenge underlying assumptions rather than simply correcting superficial errors, thereby avoiding the trap of perpetual firefighting.
The well-known “5 whys” technique is a popular RCA method, but it must be recognised that “why” can be asked in different ways—for instance, by probing prevention, detection, and recovery. This leads to the three-way five whys, a technique that examines several routes by which a failure could have been prevented, detected, or contained. Similarly, fault trees and other structured cause-and-effect diagrams are commonplace in RCA, with many variations available. In practice, problems and near misses almost always involve multiple hairline cracks across preventative, detective, and recovery measures; the search for a single, isolated root cause is rarely realistic.
Prioritise RCA where performance has departed substantially from plans, previous fixes have failed, or similar problems recur across units. Investigate the context and evidence before selecting a corrective action. Where regulators assess the quality of an investigation, retain a clear record of the facts, causal reasoning, and follow-up.
When to use it
Analyzing a product recall to identify why quality checks failed and how to redesign the process.
Investigating a safety incident in a hospital to prevent similar errors by addressing root causes like communication breakdowns or equipment issues.
Improving project management by conducting a post-mortem on a failed project, distinguishing between immediate delays and deeper planning or resource allocation root causes.
Examining a recurring customer complaint pattern to determine if it stems from a design flaw, training gap, or supply chain issue, and then implementing systemic solutions.
Investigating a significant drop in sales against an ambitious quarterly target.
Investigating a near miss to learn which controls worked and which failed before an injury or major loss occurs.
Comparing investigations across departments to identify a shared supplier, policy, or system dependency.
Preparing for a regulatory audit by evaluating the thoroughness of past root cause analyses.
FROM THEORY TO EVERYDAY LIFE
In practice
Manufacturing Defect Analysis
In a hypothetical case, a factory experiences repeated defects in a product line. Using RCA, the team identifies immediate causes (e.g., misaligned machinery), contributing causes (e.g., inadequate training), and root causes (e.g., lack of preventive maintenance schedules). They then implement corrective actions at each level, reducing defect rates by 80%.
Medical Error Investigation
After a patient receives the wrong medication, an RCA team examines the incident. They find immediate causes (nurse misread label), contributing causes (poor lighting, similar packaging), and root causes (no barcode scanning system, understaffing). Systemic changes are made, including improved labeling and mandatory scanning, to prevent recurrence.
Manufacturing Defect Investigation
A manufacturing plant experienced recurring defects in a product line. Using RCA, the team traced the root cause to a worn-out die in a stamping machine. Replacing the die eliminated the defect and saved costs.
Hospital Patient Safety Incident
A hospital noticed a pattern of patient falls in the same ward. Through RCA, they discovered that the flooring material became slippery after cleaning. Changing the cleaning protocol and flooring material reduced falls.
A MOMENT TO REFLECT
Put it to work.
Think of a recent failure or near-miss you experienced. What were the immediate, contributing, and root causes? How might they differ if you used the three-way five whys?
In your organization or daily life, where do you tend to stop at quick fixes (firefighting) rather than questioning underlying assumptions? What would a double-loop learning approach look like there?
Consider a time when a problem was attributed to an individual. What systemic factors (preventative, detective, recovery measures) might have been overlooked?
What evidence would distinguish your leading causal explanation from other plausible explanations?
How would you check whether a corrective action addressed the cause or merely suppressed the symptom?
Consider a problem that seems to affect multiple teams: what could a cross-unit RCA reveal?
Often confused with
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)