methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
LowMediumHighLow
Timedifferent
20-60 min60-180 min2-6 h15-30 min
Participantsdifferent
1-43-103-102-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsRoot cause notes, Countermeasures
Tagsno overlap
OperationsReliabilityDocumentation
IncidentTimelineSite Reliability Engineering
CausalityIncidentRoot causeTimeline
Root causeIncidentLeanProblem solving
Add more methods