methodatlas
Method guideOperations

Causal Factor Analysis

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

ComplexityHigh
Time2-6 h
Participants3-10
FormatWorkshop + async
MaturityEstablished
Plan Causal Factor Analysis
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.

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

Preserved event data, timeline, events-and-causal-factors chart, evidence register, and cause classification

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Preserved event data, timeline, events-and-causal-factors chart, evidence register, and cause classification

People / roles

Investigation lead · people with event knowledge · evidence owner · system/process experts · action owners

Pre-read

Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.

Time needed

One to three working days for data collection and analysis; 90–180 minutes for joint chart review.

Setup

Prepare a workspace with Boundary · Sequence · Evidence · Factors · Classify; separate example from live data.

03

Core question

The one question this method answers

Which events and conditions demonstrably contributed to the undesired outcome, and how are they linked in time and causality?

04

Flow

Phases with goal, actions, output and pitfall

Causal factor analysis combines chronology with cause and effect to distinguish contributing from triggering factors. It keeps incidents from being reduced to a single moment when several small contributions shaped the outcome.

Causal Factor Analysis · working structure

Fictional example

Fictional values show the actual method fields.

Causal Factor Analysis · working structure
NodeTimeEventConditionsBarrierEvidenceCausal linkClassification
E1Add evidence and rationale.08:55Deployment completesShared pool; no load isolationArchitecture boundary missingDeploy and configuration logEnables later batch startContributing condition
E2Add evidence and rationale.09:08Batch starts72 pool connections heldAlert excludes batchScheduler and pool logDisplaces checkout connectionsDirect causal factor
E3Add evidence and rationale.09:12Checkout failures beginPool 95%; timeoutsResponse only at 09:18APM and incident logUndesired final eventFinal event

  1. 1. Time

    E1
    08:55
    E2
    09:08
    E3
    09:12

  2. 2. Event

    E1
    Deployment completes
    E2
    Batch starts
    E3
    Checkout failures begin

  3. 3. Conditions

    E1
    Shared pool; no load isolation
    E2
    72 pool connections held
    E3
    Pool 95%; timeouts

  4. 4. Barrier

    E1
    Architecture boundary missing
    E2
    Alert excludes batch
    E3
    Response only at 09:18

  5. 5. Evidence

    E1
    Deploy and configuration log
    E2
    Scheduler and pool log
    E3
    APM and incident log

  6. 6. Causal link

    E1
    Enables later batch start
    E2
    Displaces checkout connections
    E3
    Undesired final event

  7. 7. Classification

    E1
    Contributing condition
    E2
    Direct causal factor
    E3
    Final event

All values are fictional.

Reference · original teaching example

  1. 1

    Boundary

    Analysis frame

    Goal

    Analysis frame: Set final event, starting point, system boundary, and investigation question.

    Inputs for this step

    • Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.
    • Preserved event data, timeline, events-and-causal-factors chart, evidence register, and cause classification

    Actions

    • Set final event, starting point, system boundary, and investigation question.

    Output

    Analysis frame

    Set final event, starting point, system boundary, and investigation question.

    Quality check

    Are start, end, impact, and exclusions explicit?

    Pitfall

    Investigation starts at the alert and omits earlier conditions. Start before the first relevant change and justify exclusions.

    Timing: 30–45 minutes

  2. 2

    Sequence

    Event chart

    Goal

    Event chart: Record events in time order with sources; show persistent conditions separately between events.

    Inputs for this step

    • Analysis frame

    Actions

    • Record events in time order with sources; show persistent conditions separately between events.

    Output

    Event chart

    Record events in time order with sources; show persistent conditions separately between events.

    Quality check

    Are events represented as actions/state changes and conditions as persistent circumstances?

    Pitfall

    Opinions and causes are entered as events in the timeline. Code observable event, persistent condition, and interpretation separately.

    Timing: 2–6 hours

  3. 3

    Evidence

    Validated chart

    Goal

    Validated chart: Validate every node and connection with log, document, measurement, or corroborated account.

    Inputs for this step

    • Event chart

    Actions

    • Validate every node and connection with log, document, measurement, or corroborated account.

    Output

    Validated chart

    Validate every node and connection with log, document, measurement, or corroborated account.

    Quality check

    Does every relevant node have source, time, and confidence status?

    Pitfall

    Gaps are filled with a coherent story. Keep the gap visible and seek targeted evidence or a counterexample.

    Timing: 45–90 minutes

  4. 4

    Factors

    Causal factors

    Goal

    Causal factors: Mark an event or condition causal when its absence plausibly changes the course; state the mechanism.

    Inputs for this step

    • Validated chart

    Actions

    • Mark an event or condition causal when its absence plausibly changes the course; state the mechanism.

    Output

    Causal factors

    Mark an event or condition causal when its absence plausibly changes the course; state the mechanism.

    Quality check

    Is the counterfactual plausible and the mechanism evidenced?

    Pitfall

    Everything on the chart is labelled causal. Mark only factors that alter course or severity through an evidenced mechanism.

    Timing: 45–75 minutes

  5. 5

    Classify

    Cause path

    Goal

    Cause path: Distinguish direct, contributing, and root causes; derive controls with effectiveness evidence.

    Inputs for this step

    • Causal factors

    Actions

    • Distinguish direct, contributing, and root causes; derive controls with effectiveness evidence.

    Output

    Cause path

    Distinguish direct, contributing, and root causes; derive controls with effectiveness evidence.

    Quality check

    Are classification and action traceable to the chart and separate from containment?

    Pitfall

    The immediate technical cause automatically becomes the root cause. Test prevention, feasibility, and system control; set an effectiveness review.

    Timing: 45–75 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Causal Factor Analysis · Timeline and FactorsReconstruct events, mark contributing factors, and derive evidence-based actions
Causal Factor AnalysisAn event timeline is connected to contributing factors, evidence checks, and corrective actions.Separate events from contributing factorsReconstruct first, then test factors against evidence and derive effective actions.Fact timelineWhat demonstrably happened?Alarm10:04Decision10:16Workaround10:31Impact10:45Factor Asignal too lateFactor Bunclear roleFactor Cmissing checkvalidatederiveCheck evidenceevaluate logs, statements, and metrics separatelyprovenunclearassumptionCorrective Actionstie actions to causal factorsMonitoringearlier signalOwnerclarify role
Form

Events-and-causal-factors chart with evidenced sequence, conditions, barriers, direct and contributing factors, and action path.

Versioning / ownership

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

Tool alternatives
  • Event and condition chart
  • Source and evidence register
  • Factor and action log

causal-factor-analysis-working-template.md

Set subject, evidence, roles, flow, and review.

Causal Factor Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Whole initiative Time: One to three working days for data collection and analysis; 90–180 minutes for joint chart review.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Preserved event data, timeline, events-and-causal-factors chart, evidence register, and cause classification
  • Roles: Investigation lead · people with event knowledge · evidence owner · system/process experts · action owners
  • Advance information: Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.
  • Overall time needed: One to three working days for data collection and analysis; 90–180 minutes for joint chart review.
  • Setup: Prepare a workspace with Boundary · Sequence · Evidence · Factors · Classify; separate example from live data.

Prepare for the work steps

Boundary: Analysis frame

  • Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.
  • Preserved event data, timeline, events-and-causal-factors chart, evidence register, and cause classification

Sequence: Event chart

  • Analysis frame

Evidence: Validated chart

  • Event chart

Factors: Causal factors

  • Validated chart

Classify: Cause path

  • Causal factors

Causal Factor Analysis · working structure

NodeTimeEventConditionsBarrierEvidenceCausal linkClassification
E1
E2
E3
  • E1: Add evidence and rationale.
  • E2: Add evidence and rationale.
  • E3: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Boundary: Analysis frame

Expected artifact: Analysis frame

Set final event, starting point, system boundary, and investigation question.

Entry:

...

  • Are start, end, impact, and exclusions explicit?

Sequence: Event chart

Expected artifact: Event chart

Record events in time order with sources; show persistent conditions separately between events.

Entry:

...

  • Are events represented as actions/state changes and conditions as persistent circumstances?

Evidence: Validated chart

Expected artifact: Validated chart

Validate every node and connection with log, document, measurement, or corroborated account.

Entry:

...

  • Does every relevant node have source, time, and confidence status?

Factors: Causal factors

Expected artifact: Causal factors

Mark an event or condition causal when its absence plausibly changes the course; state the mechanism.

Entry:

...

  • Is the counterfactual plausible and the mechanism evidenced?

Classify: Cause path

Expected artifact: Cause path

Distinguish direct, contributing, and root causes; derive controls with effectiveness evidence.

Entry:

...

  • Are classification and action traceable to the chart and separate from containment?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/causal-factor-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.

causal-factor-analysis-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Causal Factor Analysis · working structure

NodeTimeEventConditionsBarrierEvidenceCausal linkClassification
E108:55Deployment completesShared pool; no load isolationArchitecture boundary missingDeploy and configuration logEnables later batch startContributing condition
E209:08Batch starts72 pool connections heldAlert excludes batchScheduler and pool logDisplaces checkout connectionsDirect causal factor
E309:12Checkout failures beginPool 95%; timeoutsResponse only at 09:18APM and incident logUndesired final eventFinal event
07

Pitfalls

Recognize symptoms and steer against them

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

  1. Analysis frameInvestigation starts at the alert and omits earlier conditions.View in phase
  2. Event chartOpinions and causes are entered as events in the timeline.View in phase
  3. Validated chartGaps are filled with a coherent story.View in phase
  4. Causal factorsEverything on the chart is labelled causal.View in phase
  5. Cause pathThe immediate technical cause automatically becomes the root cause.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Boundary: Are start, end, impact, and exclusions explicit?
Stop Sequence: Are events represented as actions/state changes and conditions as persistent circumstances?
Stop Evidence: Does every relevant node have source, time, and confidence status?
Stop Factors: Is the counterfactual plausible and the mechanism evidenced?
Stop Classify: Are classification and action traceable to the chart and separate from containment?

Where to go next?

Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis

Also models the contributing factors as logical AND/OR combinations.

Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving

Bundles the derived corrective actions into a structured 8D team process.

View in playbookLearn from IncidentMove from scattered logs and memories to timeline, learning points, and concrete improvements.

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