Purpose
When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Operations Analysis method
Root Cause Analysis
Separates events, evidence, confirmed causes, and appropriate actions so analysis supports learning rather than blame.
Observations, measurements, and patterns over time become hypotheses that are tested against evidence. The search narrows from many possibilities to causes with the strongest explanatory value. Subsequent actions address the underlying mechanism rather than the visible symptom.
Which evidenced system causes must change so this or a similar event does not recur?
- Participants
- 3-8
- Time
- One to five working days depending on evidence access and impact; 90–180 minutes for joint analysis.
Evidence building, analysis, and effectiveness review form a multi-stage initiative.
Problem
Testable problem statement
Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.
Evidence
Evidence-backed timeline
Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.
Causal chain
Tested causal chain
Connect direct and contributing factors; name mechanism and countercheck for each link.
Root causes
Justified root causes
Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.
Actions
Effectiveness plan
Target controls at root causes; set owner, date, effect signal, and review.
Add new evidence at review and version decisions with the prior state.
A good fit when
Wenn ein Problem wiederkehrt und die Ursache unklar bleibt, legt die Methode das zugrunde liegende Wirkgefüge frei. Sie trennt Symptom, Vermutung und belastbare Erklärung voneinander.
Ideal for
- Recurring operational problems
- Quality and service deviations
- Post-incident reviews
Not good for
- Trivial one-off errors
- Blame assignment
- Situations without solid data
Outputs
Effectiveness plan
Traceable RCA report with timeline, direct and contributing causes, justified root causes, and effectiveness-checked actions.
Root Cause Analysis · working structure
Fictional example
Fictional values show the actual method fields.
Testable problem statement
Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.
On 14 May from 09:12–09:47, 38% of checkouts failed; 214 customers affected; scope EU production.
Evidence-backed timeline
Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.
09:08 batch starts; 09:12 pool 95%; 09:18 restart; 09:31 batch paused; 09:47 stable.
Tested causal chain
Connect direct and contributing factors; name mechanism and countercheck for each link.
Batch and checkout shared a pool; batch held 72 connections; checkout exceeded timeout. Staging reproduction confirms it.
Justified root causes
Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.
RC1 no pool separation; RC2 monitoring excluded batch connections. Restart is a response, not a root cause.
Effectiveness plan
Target controls at root causes; set owner, date, effect signal, and review.
Separate pools by 21 May; alert total use at 70%; load test shows checkout failures below 1%; review 28 May.
All values are fictional.
First step
Define problem, impact, period, and system boundary; preserve evidence and record immediate containment separately.
Deep dive
How it works
Hypotheses are formed from observations, measurements, and patterns over time and tested against evidence. This narrows the search from many possibilities down to the causes with the strongest explanatory value. The resulting actions target not the visible symptom but the mechanism behind it.
In detail
Root Cause Analysis separates visible symptoms from the conditions that enable or trigger a problem. The method combines events, data, process steps, and human factors into a traceable causal logic. Many possible explanations are narrowed down to plausible causes before measures are defined. That creates a shift from quick repair to durable improvement.
Facilitation
Prepare the problem statement, data, timeline, and people involved in the process. Moderate in a fact-focused way and keep observation, interpretation, and hypothesis visibly separate. Do not stop at the first plausible cause and assign actions only to confirmed causes.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Root Cause Analysis: WorksheetSet subject, evidence, roles, flow, and review.markdown
Root Cause Analysis: WorksheetSet subject, evidence, roles, flow, and review.
markdownroot-cause-analysis-working-template.md
Set subject, evidence, roles, flow, and review.
Root Cause Analysis: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Whole initiative Time: One to five working days depending on evidence access and impact; 90–180 minutes for joint analysis.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Precise problem definition, event and measurement data, timeline, cause evidence register, and control/action plan
- Roles: Investigation lead · process and system experts · evidence owner · independent challenger · action owners
- Advance information: Define problem, impact, period, and system boundary; preserve evidence and record immediate containment separately.
- Overall time needed: One to five working days depending on evidence access and impact; 90–180 minutes for joint analysis.
- Setup: Prepare a workspace with Problem · Evidence · Causal chain · Root causes · Actions; separate example from live data.
Prepare for the work steps
Problem: Testable problem statement
- Define problem, impact, period, and system boundary; preserve evidence and record immediate containment separately.
- Precise problem definition, event and measurement data, timeline, cause evidence register, and control/action plan
Evidence: Evidence-backed timeline
- Testable problem statement
Causal chain: Tested causal chain
- Evidence-backed timeline
Root causes: Justified root causes
- Tested causal chain
Actions: Effectiveness plan
- Justified root causes
Root Cause Analysis · working structure
Testable problem statement
Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.
...
Evidence-backed timeline
Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.
...
Tested causal chain
Connect direct and contributing factors; name mechanism and countercheck for each link.
...
Justified root causes
Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.
...
Effectiveness plan
Target controls at root causes; set owner, date, effect signal, and review.
...
The blank worksheet contains prompts only.
Reference · original teaching example
Problem: Testable problem statement
Expected artifact: Testable problem statement
Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.
Entry:
...
- Does it state what, when, where, and how much without presuming a cause?
Evidence: Evidence-backed timeline
Expected artifact: Evidence-backed timeline
Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.
Entry:
...
- Does every event have time, source, and evidence status, with conflicts visible?
Causal chain: Tested causal chain
Expected artifact: Tested causal chain
Connect direct and contributing factors; name mechanism and countercheck for each link.
Entry:
...
- Is every causal link supported by mechanism and evidence rather than temporal proximity?
Root causes: Justified root causes
Expected artifact: Justified root causes
Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.
Entry:
...
- Does each root cause pass prevention, feasibility, and side-effect tests?
Actions: Effectiveness plan
Expected artifact: Effectiveness plan
Target controls at root causes; set owner, date, effect signal, and review.
Entry:
...
- Does every action address a cause and have an observable effectiveness signal?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/root-cause-analysis/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Operations
A3 Problem Solving
Instead of Root Cause Analysis, choose A3 Problem Solving when you want to run analysis, countermeasures, and follow-up on one compact sheet.
Operations
Kepner-Tregoe
Instead of Root Cause Analysis, choose Kepner-Tregoe when you want to handle problems and decisions with a strict separation of facts, causes, and options.
Operations
Root Cause Tree Analysis
Clarifies workflows, data, causes, and improvements by framing the problem precisely, branching possible causes, and defining countermeasures.
Operations
Scatter Diagram
Paired data points reveal whether two variables move together and where a suspected relationship needs deeper proof.
Operations
Family Tree Analysis
A recurring incident pattern links related cases across time so systemic causes become visible beyond one event.
Operations
8D Problem Solving
Coordinates team, immediate actions, root cause analysis, and prevention across eight steps to a verified solution.
Constraints and origin
MediumWorkshop + async1-4 h
Profile
- Method form
- Analysis method
- Participants
- 3-8
- Time
- 1-4 h
- Maturity
- Canonical
- Origin
- Quality Management Community
Next up: RAID Log