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
Scenario Planning method illustration showing its working structure
Business Strategy
Scenario Planning
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.Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path.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
LowHighMedium
Timedifferent
20-60 min0.5-2 TageAs needed
Participantsdifferent
1-44-124-15
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathScenario Set, Strategic Implications, Robust OptionsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
StrategyUncertaintyPlanning
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis