Purpose
For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Operations Mapping tool
Causal Factor Analysis
Causal factor analysis reconstructs an event chain, marks factors, and derives testable causes and corrective actions.
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.
Which events and conditions demonstrably contributed to the undesired outcome, and how are they linked in time and causality?
- Participants
- 3-10
- Time
- One to three working days for data collection and analysis; 90–180 minutes for joint chart review.
Evidence building, analysis, and effectiveness review form a multi-stage initiative.
Boundary
Analysis frame
Set final event, starting point, system boundary, and investigation question.
Sequence
Event chart
Record events in time order with sources; show persistent conditions separately between events.
Evidence
Validated chart
Validate every node and connection with log, document, measurement, or corroborated account.
Factors
Causal factors
Mark an event or condition causal when its absence plausibly changes the course; state the mechanism.
Classify
Cause path
Distinguish direct, contributing, and root causes; derive controls with effectiveness evidence.
Add new evidence at review and version decisions with the prior state.
A good fit when
Bei einem Ereignis mit kompliziertem Verlauf zerlegt die Methode die wirkenden Faktoren entlang der Zeit. Sie zeigt, wie Bedingungen, Entscheidungen und Reaktionen zusammen einen Verlauf erzeugen.
Ideal for
- Incident reviews
- Accident and event analysis
- Complex process deviations
Not good for
- Very simple single causes
- Problems without an event sequence
- Pure solution finding
Outputs
Cause path
Events-and-causal-factors chart with evidenced sequence, conditions, barriers, direct and contributing factors, and action path.
Causal Factor Analysis · working structure
Fictional example
Fictional values show the actual method fields.
| Node | Time | Event | Conditions | Barrier | Evidence | Causal link | Classification |
|---|---|---|---|---|---|---|---|
| E1Add evidence and rationale. | 08:55 | Deployment completes | Shared pool; no load isolation | Architecture boundary missing | Deploy and configuration log | Enables later batch start | Contributing condition |
| E2Add evidence and rationale. | 09:08 | Batch starts | 72 pool connections held | Alert excludes batch | Scheduler and pool log | Displaces checkout connections | Direct causal factor |
| E3Add evidence and rationale. | 09:12 | Checkout failures begin | Pool 95%; timeouts | Response only at 09:18 | APM and incident log | Undesired final event | Final event |
1. Time
- E1
- 08:55
- E2
- 09:08
- E3
- 09:12
2. Event
- E1
- Deployment completes
- E2
- Batch starts
- E3
- Checkout failures begin
3. Conditions
- E1
- Shared pool; no load isolation
- E2
- 72 pool connections held
- E3
- Pool 95%; timeouts
4. Barrier
- E1
- Architecture boundary missing
- E2
- Alert excludes batch
- E3
- Response only at 09:18
5. Evidence
- E1
- Deploy and configuration log
- E2
- Scheduler and pool log
- E3
- APM and incident log
6. Causal link
- E1
- Enables later batch start
- E2
- Displaces checkout connections
- E3
- Undesired final event
7. Classification
- E1
- Contributing condition
- E2
- Direct causal factor
- E3
- Final event
All values are fictional.
First step
Set undesired outcome, investigation window, and system boundary; preserve sources and keep containment separate.
Deep dive
How it works
The analysis connects chronology with cause and effect, making visible which factors were merely accompanying and which were triggering. This keeps the incident from being reduced to a single moment. The structure is especially strong when several small contributions combine to tip the balance.
In detail
Causal Factor Analysis combines timeline work with cause evaluation. First it makes clear what happened, then it marks conditions, decisions, gaps, and system factors that influenced the course of events. The method distinguishes between trigger event, contributing factor, and deeper cause. That creates a solid bridge from reconstruction to improvement measures.
Facilitation
Collect logs, statements, metrics, and decisions beforehand. Draw the chronology first before judging causes, otherwise memory errors and hindsight bias will dominate. Ask participants to label facts and interpretations separately.
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
Causal Factor Analysis: WorksheetSet subject, evidence, roles, flow, and review.markdown
Causal Factor Analysis: WorksheetSet subject, evidence, roles, flow, and review.
markdowncausal-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
| Node | Time | Event | Conditions | Barrier | Evidence | Causal link | Classification |
|---|---|---|---|---|---|---|---|
| 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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Operations
Fault Tree Analysis
Instead of Causal Factor Analysis, choose Fault Tree Analysis when you want to break down a failure top-down through logical links and failure paths.
Operations
Root Cause Tree Analysis
Instead of Causal Factor Analysis, choose Root Cause Tree Analysis when you want to trace causes as a branched tree with clear root causes.
Operations
Change Analysis
Compares an outlier with a stable case and filters out the differences that explain the deviation.
Operations
MORT Analysis
A structured accident tree separates management controls, barriers, and events so serious incidents become auditable.
Operations
Barrier Analysis
Hazards, targets, and failed barriers are mapped so controls can be strengthened at the point of exposure.
Operations
Family Tree Analysis
A recurring incident pattern links related cases across time so systemic causes become visible beyond one event.
Constraints and origin
HighWorkshop + async2-6 h
Profile
- Method form
- Mapping tool
- Participants
- 3-10
- Time
- 2-6 h
- Maturity
- Established
- Origin
- Praxisgemeinschaft
Next up: Fault Tree Analysis