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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
LowHighHigh
Timedifferent
20–45 minHalber Tag1-4 Wochen
Participantsdifferent
Small cross-functional group5-201-6
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logSimulation Notes, Gaps List, Updated RunbooksExperiment results, Decision log, Learning summary
Tagsno overlap
RiskDecisionFailurePlanning
ResilienceOperationsIncident
ExperimentsGrowthAnalyticsValidation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for ALPEN Method
Operations
ALPEN Method