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
Paper illustration for Learning Review.
Operations
Learning Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
20-60 min30-90 min1-3 hAs needed
Participantsdifferent
1-41-63-104-15
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListLearning Review Notes, System Factors, Improvement ActionsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
LearningRetrospectiveIncidentOperations
IncidentOperationsReliability
Add more methods