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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
LowHighMediumLow
Timedifferent
20–45 minHalber Tag45-60 min45-90 min
Participantsdifferent
Small cross-functional group5-202-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logSimulation Notes, Gaps List, Updated RunbooksAssumption map, Test backlog, Risk rankingAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
RiskDecisionFailurePlanning
ResilienceOperationsIncident
AssumptionsRiskExperimentsValidation
AssumptionsRiskDecisionDiscovery
Add more methods