methodatlas
Method guideOperations

Root Cause Analysis

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-4 h
Participants3-8
FormatWorkshop + async
MaturityCanonical
Plan Root Cause Analysis
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Define problem, impact, period, and system boundary; preserve evidence and record immediate containment separately.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

Precise problem definition, event and measurement data, timeline, cause evidence register, and control/action plan

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Precise problem definition, event and measurement data, timeline, cause evidence register, and control/action plan

People / roles

Investigation lead · process and system experts · evidence owner · independent challenger · action owners

Pre-read

Define problem, impact, period, and system boundary; preserve evidence and record immediate containment separately.

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.

03

Core question

The one question this method answers

Which evidenced system causes must change so this or a similar event does not recur?

04

Flow

Phases with goal, actions, output and pitfall

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.

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.

Reference · original teaching example

  1. 1

    Problem

    Testable problem statement

    Goal

    Testable problem statement: Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.

    Inputs for this step

    • 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

    Actions

    • Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.

    Output

    Testable problem statement

    Describe the undesired outcome with deviation, impact, time, and boundary; keep containment separate.

    Quality check

    Does it state what, when, where, and how much without presuming a cause?

    Pitfall

    Database failure caused by bad configuration presumes cause and solution. State only observed outcome, target, magnitude, time, and boundary.

    Timing: 30–45 minutes

  2. 2

    Evidence

    Evidence-backed timeline

    Goal

    Evidence-backed timeline: Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.

    Inputs for this step

    • Testable problem statement

    Actions

    • Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.

    Output

    Evidence-backed timeline

    Reconstruct chronology from logs, measures, documents, and accounts; mark conflicts and gaps.

    Quality check

    Does every event have time, source, and evidence status, with conflicts visible?

    Pitfall

    Memories become an exact timeline without corroboration. Label every statement by source and check against technical or documentary traces.

    Timing: 2–8 hours

  3. 3

    Causal chain

    Tested causal chain

    Goal

    Tested causal chain: Connect direct and contributing factors; name mechanism and countercheck for each link.

    Inputs for this step

    • Evidence-backed timeline

    Actions

    • Connect direct and contributing factors; name mechanism and countercheck for each link.

    Output

    Tested causal chain

    Connect direct and contributing factors; name mechanism and countercheck for each link.

    Quality check

    Is every causal link supported by mechanism and evidence rather than temporal proximity?

    Pitfall

    An event shortly before failure is automatically called causal. Describe the mechanism and test it by reproduction, comparison, or counterexample.

    Timing: 60–120 minutes

  4. 4

    Root causes

    Justified root causes

    Goal

    Justified root causes: Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.

    Inputs for this step

    • Tested causal chain

    Actions

    • Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.

    Output

    Justified root causes

    Test candidates for recurrence prevention, feasibility, and absence of harmful side effects.

    Quality check

    Does each root cause pass prevention, feasibility, and side-effect tests?

    Pitfall

    Analysis stops at operator error or failed component. Ask which technical or organisational control failed and apply the criteria explicitly.

    Timing: 45–90 minutes

  5. 5

    Actions

    Effectiveness plan

    Goal

    Effectiveness plan: Target controls at root causes; set owner, date, effect signal, and review.

    Inputs for this step

    • Justified root causes

    Actions

    • Target controls at root causes; set owner, date, effect signal, and review.

    Output

    Effectiveness plan

    Target controls at root causes; set owner, date, effect signal, and review.

    Quality check

    Does every action address a cause and have an observable effectiveness signal?

    Pitfall

    Actions say retrain the team without changing a control. Define a technical or organisational control with measure and verification.

    Timing: 45–75 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Root Cause AnalysisSeparate symptoms, facts, cause hypotheses, and confirmed root causes before deriving countermeasures
Root Cause AnalysisThe visual shows the path from a visible problem through evidence and cause hypotheses to a confirmed root cause and connected countermeasures.Work from symptom to evidenced causeRCA prevents premature fixes: causes are treated as hypotheses and translated into actions only after evidence.symptom isnot the causetesthypothesesevidence decidestrack effectivenessProblemdescribe the visible symptompreciselyFact baseseparate data, timeline, andobservationsCause Aplausible, but untestedCause Bcontributing factorCause Csystem conditionConfirmed root causeevidenced and controllableCountermeasuresconnect directly to confirmed cause
Form

Traceable RCA report with timeline, direct and contributing causes, justified root causes, and effectiveness-checked actions.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • Evidence and source register
  • Event and causal timeline
  • Cause and action register

root-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

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

root-cause-analysis-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Root Cause Analysis · working structure

Testable problem statement

On 14 May from 09:12–09:47, 38% of checkouts failed; 214 customers affected; scope EU production.

Evidence-backed timeline

09:08 batch starts; 09:12 pool 95%; 09:18 restart; 09:31 batch paused; 09:47 stable.

Tested causal chain

Batch and checkout shared a pool; batch held 72 connections; checkout exceeded timeout. Staging reproduction confirms it.

Justified root causes

RC1 no pool separation; RC2 monitoring excluded batch connections. Restart is a response, not a root cause.

Effectiveness plan

Separate pools by 21 May; alert total use at 70%; load test shows checkout failures below 1%; review 28 May.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Testable problem statementDatabase failure caused by bad configuration presumes cause and solution.View in phase
  2. Evidence-backed timelineMemories become an exact timeline without corroboration.View in phase
  3. Tested causal chainAn event shortly before failure is automatically called causal.View in phase
  4. Justified root causesAnalysis stops at operator error or failed component.View in phase
  5. Effectiveness planActions say retrain the team without changing a control.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Problem: Does it state what, when, where, and how much without presuming a cause?
Stop Evidence: Does every event have time, source, and evidence status, with conflicts visible?
Stop Causal chain: Is every causal link supported by mechanism and evidence rather than temporal proximity?
Stop Root causes: Does each root cause pass prevention, feasibility, and side-effect tests?
Stop Actions: Does every action address a cause and have an observable effectiveness signal?

Method after Quality Management Community. Curated with 1 sources.

Sources: Root Cause Analysis

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log

Enters the planned controls with owner and effectiveness signal into tracking.

Paper illustration for Kaizen Event.
Operations
Kaizen Event

Implements the root-cause-aligned controls in a focused improvement workshop.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods