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 ARID (Active Reviews for Intermediate Designs) |  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. | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | Low | Medium | High |
Timedifferent | 1-5 Tage | Stunden bis wenige Tage | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 1-4 | Designers, developers as users, and facilitation | 1-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Experiment results, Decision log, Learning summary |
Tags1 shared | ValidationExperimentsDemandGrowth | ValidationDemandMVP | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsGrowthAnalyticsValidation |