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
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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
LowLowHighLow
Timedifferent
20-60 min30-90 minHalber Tag10-20 min daily
Participantsdifferent
1-42-85-201
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
Runbook, Checklist, Escalation PathConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesSimulation Notes, Gaps List, Updated RunbooksDaily Plan, Time Estimates, Review Notes
Tagsno overlap
OperationsReliabilityDocumentation
ConstraintsDecisionPlanningOptions
ResilienceOperationsIncident
PlanningTime managementProductivityOperations
Add more methods