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 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 Fault Tree Analysis.
Operations
Fault Tree Analysis
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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
LowMediumHighHigh
Timedifferent
20–45 min45-60 min2-6 h1-4 Wochen
Participantsdifferent
Small cross-functional group2-83-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logAssumption map, Test backlog, Risk rankingFault Tree, Critical Paths, Cause Hypotheses, Control ActionsExperiment results, Decision log, Learning summary
Tagsno overlap
RiskDecisionFailurePlanning
AssumptionsRiskExperimentsValidation
RiskRoot causeSafety
ExperimentsGrowthAnalyticsValidation
Add more methods