View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Growth Growth Experiment |  Product Discovery Fake Door Test |  Product Discovery Smoke Test |
|---|---|---|---|---|
Purposedifferent | 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 growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 Wochen | 1-5 Tage | 1-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | 1-6 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Experiment card, Result summary, Next bet | Click Data, Interest Signal, Learning Decision | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | MarketingGrowthExperimentsLearning | ValidationExperimentsDemandDiscovery | ValidationExperimentsDemandGrowth |