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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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
LowHighLowLow
Timedifferent
20–45 min1-4 Wochen15-45 min1-5 Tage
Participantsdifferent
Small cross-functional group1-61-3Nutzertraffic
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logExperiment results, Decision log, Learning summaryADR File, Decision Log, RationaleInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
RiskDecisionFailurePlanning
ExperimentsGrowthAnalyticsValidation
ArchitectureRationaleDocumentationGovernance
ValidationExperimentsDemandGrowth
Add more methods