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
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
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
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.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.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.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
20-60 min15-45 minAs neededHalber Tag
Participantsdifferent
1-41-84-155-20
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathPERT Estimate, Expected Value, Risk NotesIncident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
OperationsReliabilityDocumentation
EstimationUncertaintyRisk
IncidentOperationsReliability
ResilienceOperationsIncident
Add more methods