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
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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 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.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
20–45 min1-3 hHalber Tag30-90 min
Participantsdifferent
Small cross-functional group3-85-202-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logFailure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsSimulation Notes, Gaps List, Updated RunbooksConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
FailureResilienceRisk
ResilienceOperationsIncident
ConstraintsDecisionPlanningOptions
Add more methods