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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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 Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
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.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.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
HighMediumMediumLow
Timedifferent
Halber Tag30-90 minAs needed30-90 min
Participantsdifferent
5-201-64-152-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksDecision Tree, Option Map, Assumption ListIncident Log, Action Tracker, Stakeholder UpdatesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
ResilienceOperationsIncident
DecisionTreeOptions
IncidentOperationsReliability
ConstraintsDecisionPlanningOptions
Add more methods