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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Purposedifferent
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.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.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.
Complexitydifferent
MediumHighLowMedium
Timedifferent
As neededHalber Tag30-90 min30-90 min
Participantsdifferent
4-155-202-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated RunbooksConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesDecision Tree, Option Map, Assumption List
Tagsno overlap
IncidentOperationsReliability
ResilienceOperationsIncident
ConstraintsDecisionPlanningOptions
DecisionTreeOptions
Add more methods