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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.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.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
LowMediumHighMedium
Timedifferent
20-60 min15-45 minHalber TagAs needed
Participantsdifferent
1-41-85-204-15
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathPERT Estimate, Expected Value, Risk NotesSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
EstimationUncertaintyRisk
ResilienceOperationsIncident
IncidentOperationsReliability
Add more methods