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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.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.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
LowHighLow
Timedifferent
20-60 minHalber Tag10-20 min daily
Participantsdifferent
1-45-201
Formatdifferent
AsyncWorkshopAsync
Outputdifferent
Runbook, Checklist, Escalation PathSimulation Notes, Gaps List, Updated RunbooksDaily Plan, Time Estimates, Review Notes
Tags1 shared
OperationsReliabilityDocumentation
ResilienceOperationsIncident
PlanningTime managementProductivityOperations
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Learning Review.
Operations
Learning Review