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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumHighLow
Timedifferent
20-60 min30-90 minHalber Tag30-90 min
Participantsdifferent
1-41-65-202-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListSimulation Notes, Gaps List, Updated RunbooksConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
ResilienceOperationsIncident
ConstraintsDecisionPlanningOptions
Add more methods