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 |  UX Research Surveys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth A/B Testing |
|---|---|---|---|---|
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. | When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. | 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 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 | Low | Medium | High | High |
Timedifferent | 1-5 Tage | 3-14 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 50+ | Evaluation team, architects, and relevant stakeholders | 1-6 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Survey Results, Charts, Segment Insights | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | QuantitativeResearchValidation | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsGrowthAnalyticsValidation |