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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family 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
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 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.For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowHighMediumMedium
Timedifferent
20–45 min1-4 Wochen2-4 h45-60 min
Participantsdifferent
Small cross-functional group1-62-62-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logExperiment results, Decision log, Learning summaryFamily Tree Diagram, Pattern Notes, Systemic MeasuresAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskDecisionFailurePlanning
ExperimentsGrowthAnalyticsValidation
Root causePatternsIncidentSystemic
AssumptionsRiskExperimentsValidation
Add more methods