Root cause analysis
Definition
A structured problem-solving process that identifies the fundamental cause of a defect, failure, or incident, distinguishing root causes from proximate causes, so that corrective actions address the underlying issue rather than just the symptoms.
Root cause analysis is not a single method but a family of techniques united by the same goal: stop treating symptoms and find what actually needs to change. The proximate cause is what triggered the failure; the root cause is what made that trigger possible.
Common RCA methods:
- Five whys, iterative questioning to trace the causal chain.
- Fishbone (Ishikawa) diagram, maps multiple contributing causes across categories like People, Process, Equipment, and Environment.
- Fault tree analysis, top-down deductive approach using boolean logic gates.
- Pareto analysis, ranks causes by frequency to focus effort on the 20% of causes producing 80% of failures.
The RCA process (generic):
- Define the problem precisely, symptoms, scope, and impact.
- Collect data, logs, timelines, interviews.
- Identify possible causes, use a fishbone diagram or five whys to brainstorm.
- Identify the root cause, the cause that, if removed, prevents recurrence.
- Develop and implement corrective actions.
- Verify the fix, confirm the root cause is addressed and the problem doesn't recur.
On a whiteboard: Most RCA sessions start at a whiteboard. The problem goes in the center or at the right; causes radiate outward. The whiteboard is the working surface; the formal RCA document comes after. Snapping the board with BoardSnap gives you a structured draft of the cause map before the formal write-up.
Examples
- A payment processing team runs RCA after a 2-hour outage and traces the root cause to a missing rate limit on an upstream API dependency.
- A manufacturing line conducts RCA after a batch defect and discovers the root cause is a supplier calibration drift, not operator error.
- A product team runs RCA on a feature that launched with a critical bug, finding the root cause in a gap in the QA handoff process.
- A startup uses RCA after losing two enterprise deals to the same objection, identifying a gap in the sales narrative rather than a product deficiency.
Snap a root cause analysis. Ship its actions.
BoardSnap turns any whiteboard, including this one, into a summary and action plan.