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 |  Growth A/B Testing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Risk Storming |
|---|---|---|---|---|
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 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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | High | High | Low |
Timedifferent | 1-5 Tage | 1-4 Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min |
Participantsdifferent | Nutzertraffic | 1-6 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation | ArchitectureQualityRiskTradeoffsStakeholders | RiskArchitectureWorkshopValidation |