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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
LowMediumLowLow
Timedifferent
20-60 min30-90 min20–45 min10-20 min daily
Participantsdifferent
1-41-6Small cross-functional group1
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListRisk list, Mitigation plan, Assumption logDaily Plan, Time Estimates, Review Notes
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
RiskDecisionFailurePlanning
PlanningTime managementProductivityOperations
Add more methods