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
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
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
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.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.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
20-60 minAs needed1-3 h45-90 min
Participantsdifferent
1-44-152-83-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathIncident Log, Action Tracker, Stakeholder UpdatesGap Matrix, Action Plan, Risk NotesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
OperationsReliabilityDocumentation
IncidentOperationsReliability
StrategyAnalysisPlanning
OutcomesStrategyBehaviorPlanning
Add more methods