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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.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.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.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
LowHighLowLow
Timedifferent
20–45 minHalber Tag30-90 min10-20 min daily
Participantsdifferent
Small cross-functional group5-202-81
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logSimulation Notes, Gaps List, Updated RunbooksConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RiskDecisionFailurePlanning
ResilienceOperationsIncident
ConstraintsDecisionPlanningOptions
PlanningTime managementProductivityOperations
Add more methods