Operations Mapping tool

Family Tree Analysis

Family tree analysis compares related events through shared causes, barriers, and conditions.

Family tree analysis groups similar events using a transparent relationship criterion and compares event chains. Recurring factors are derived only from evidenced commonalities.

Core question

Which recurring condition connects related events, and which systemic action is missing?

Plan Family Tree Analysis Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 2-6
Time: 2-4 h

Family Tree Analysis uses form an event family using fixed attributes and compare common causal and barrier patterns. Assessments remain justified and context-bound.

Paper illustration of Family Tree Analysis with its method-specific working model.

Define family
Define family
Define comparison criterion, horizon, and population.
Map events
Map events
Normalise chronology, conditions, barriers, and consequences for each event.
Compare patterns
Compare patterns
Compare commonalities, differences, and counterexamples.
Correct system
Correct system
Address the common cause or barrier gap and measure effectiveness.

Update after new evidence or a material context change and retain the previous version.

A good fit when

For several similar incidents, near misses, or quality deviations over time.

Ideal for

Recurring incidents
Pattern analysis across incidents
Learning from near misses
Combination with Causal Factor Analysis

Not good for

One-off special cases unrelated to earlier events
Pure technical detail analysis
Quick operational fixes

Outputs

event family tree
event family tree with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for event family tree.

event family tree

Fictional worked example

form an event family using fixed attributes and compare common causal and barrier patterns as a precise working structure with a fictional example.

Family rule

Attribute · horizon · exclusion

Faulty data leave review; six months.

Event profile

Chain · conditions · barriers

Manual CSV; mandatory-field test missing.

Pattern

Commonality · n/N · counterexample

4/5 share transformation; one different cause.

Action

System change · exposure · effectiveness

Validator before export; errors per 100 exports.

The example demonstrates the domain logic of Family Tree Analysis; worksheets remain blank.

U.S. Department of Energy: Accident Investigation Program

First step

Start with the core question: Which recurring condition connects related events, and which systemic action is missing?

Open the method guide

Good to do first

Operations

Causal Factor Analysis

Supplies individual root cause analyses that are linked here into an event family.

Where to go next?

Operations

Root Cause Tree Analysis

Branches out the event family's shared pattern into deeper causes.

Operations

Fishbone Diagram

Visually sorts the event family's shared cause categories.

Deep dive

Purpose

For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.

How it works

Every event is traced back to its predecessors, triggers, and contributing factors. This produces a picture of recurring family resemblances instead of isolated individual cases. The structure helps recognize systemic patterns that are easily lost in individual reports.

In detail

Family Tree Analysis makes recurring incidents visible as related events instead of treating them in isolation. Triggers, precursors, and contributing conditions are compared across several cases. The method helps recognize shared patterns and derive systemic countermeasures.

Facilitation

Gather several comparable cases before claiming commonalities, and describe family traits as concretely as possible. The method gains strength when recurring patterns across events become clearer than the differences in the individual case. Close with a systemic theme, an observation indicator, and a hypothesis for the next check.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Root cause Patterns Incident Systemic

Sources

U.S. Department of Energy: Accident Prevention and Investigation Programenergy.govCurrent DOE program page linking to the accident analysis handbooks; workflow is original teaching material.

Artifact templates

Family Tree Analysis: WorksheetPlan Family Tree Analysis around its domain steps and the concrete decision question.

markdown

family-tree-analysis-working-template.md

Plan Family Tree Analysis around its domain steps and the concrete decision question.

Family Tree Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full workshop Time: 90–180 minutes

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

Preparation for this scope

Method setup

Materials: Event register, chronologies and causal analyses, taxonomy for comparison attributes, shared workspace, source links, and decision log.
Roles: Investigator · quality/safety analyst · process owner
Advance information: Collect Event register, chronologies and causal analyses, taxonomy for comparison attributes in advance and mark open assumptions.
Overall time needed: 90–180 minutes
Setup: Prepare form an event family using fixed attributes and compare common causal and barrier patterns visibly and calibrate assessment terms before starting.