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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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.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.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.
Complexitydifferent
LowMediumHigh
Timedifferent
20-60 min1-3 hHalber Tag
Participantsdifferent
1-42-85-20
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathGap Matrix, Action Plan, Risk NotesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
OperationsReliabilityDocumentation
StrategyAnalysisPlanning
ResilienceOperationsIncident
Add more methods

Often compared together

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

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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