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
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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 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
HighMediumLowHigh
Timedifferent
2-6 h45-60 min20–45 min1-4 Wochen
Participantsdifferent
3-82-8Small cross-functional group1-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsAssumption map, Test backlog, Risk rankingRisk list, Mitigation plan, Assumption logExperiment results, Decision log, Learning summary
Tagsno overlap
RiskRoot causeSafety
AssumptionsRiskExperimentsValidation
RiskDecisionFailurePlanning
ExperimentsGrowthAnalyticsValidation
Add more methods