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
Paper illustration for Decision Framing Workshop.
Decision Making
Decision Framing Workshop
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins.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.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
HighMediumLowMedium
Timedifferent
Halber Tag60-120 min20-60 minAs needed
Participantsdifferent
5-204-101-44-15
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksDecision Frame, Decision Question, Criteria List, Evidence PlanRunbook, Checklist, Escalation PathIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ResilienceOperationsIncident
Decision framingAlignmentCriteriaOptions
OperationsReliabilityDocumentation
IncidentOperationsReliability
Add more methods