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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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 Root Cause Analysis.
Operations
Root Cause Analysis
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
HighMediumLowMedium
Timedifferent
2-6 hAs needed15-30 min1-4 h
Participantsdifferent
3-104-152-63-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Timeline, Causal Factor Chart, Cause List, Corrective ActionsIncident Log, Action Tracker, Stakeholder UpdatesRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tags1 shared
CausalityIncidentRoot causeTimeline
IncidentOperationsReliability
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods