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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
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 decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
20-60 min30-90 minAs needed2-8 h
Participantsdifferent
1-41-64-152-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListIncident Log, Action Tracker, Stakeholder UpdatesProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
IncidentOperationsReliability
Problem solvingRoot causeDecisionOperations
Add more methods