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 for Smoke Test.
Product Discovery
Smoke Test
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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
LowHighMediumLow
Timedifferent
20–45 min1-4 Wochen2-4 h1-5 Tage
Participantsdifferent
Small cross-functional group1-62-6Nutzertraffic
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logExperiment results, Decision log, Learning summaryFamily Tree Diagram, Pattern Notes, Systemic MeasuresInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
RiskDecisionFailurePlanning
ExperimentsGrowthAnalyticsValidation
Root causePatternsIncidentSystemic
ValidationExperimentsDemandGrowth
Add more methods