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 Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline 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 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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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 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
HighLowMediumLow
Timedifferent
2-6 h30-60 min60-180 min15-30 min
Participantsdifferent
3-102-83-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Event Timeline, Causal Factor Chart, Cause List, Corrective ActionsFishbone Diagram, Cause Categories, Investigation BacklogIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsRoot cause notes, Countermeasures
Tagsno overlap
CausalityIncidentRoot causeTimeline
Root causeQualityOperations
IncidentTimelineSite Reliability Engineering
Root causeIncidentLeanProblem solving
Add more methods