View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Smoke Test |  Product Discovery Pretotyping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 1-5 Tage | Stunden bis wenige Tage | Several meetings plus preparation and analysis; total effort depends on scope | 45-60 min |
Participantsdifferent | Nutzertraffic | 1-4 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationExperimentsDemandGrowth | ValidationDemandMVP | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskExperimentsValidation |