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 Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.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.
Complexitydifferent
LowHighMediumLow
Timedifferent
20–45 minHalber Tag1-3 h30-90 min
Participantsdifferent
Small cross-functional group5-203-82-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logSimulation Notes, Gaps List, Updated RunbooksFailure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
ResilienceOperationsIncident
FailureResilienceRisk
ConstraintsDecisionPlanningOptions
Add more methods