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
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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Purposedifferent
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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.
Complexitydifferent
HighMediumMedium
Timedifferent
0.5-2 TageAs needed1-3 h
Participantsdifferent
4-124-152-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Scenario Set, Strategic Implications, Robust OptionsIncident Log, Action Tracker, Stakeholder UpdatesGap Matrix, Action Plan, Risk Notes
Tagsno overlap
StrategyUncertaintyPlanning
IncidentOperationsReliability
StrategyAnalysisPlanning
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
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping