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
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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h45-90 minAs needed10-20 min daily
Participantsdifferent
2-83-84-151
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Gap Matrix, Action Plan, Risk NotesImpact Map, Outcome Hypotheses, Delivery OptionsIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
StrategyAnalysisPlanning
OutcomesStrategyBehaviorPlanning
IncidentOperationsReliability
PlanningTime managementProductivityOperations
Add more methods