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
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Purposedifferent
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
60-180 min20-45 min15-30 min2-6 h
Participantsdifferent
3-101-82-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Incident Timeline, Evidence Log, Delay Analysis, Improvement ActionsOwnership Reflection, Action Commitment, Coaching NotesRoot cause notes, CountermeasuresEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
IncidentTimelineSite Reliability Engineering
ResponsibilityLeadershipTeam
Root causeIncidentLeanProblem solving
CausalityIncidentRoot causeTimeline
Add more methods