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 |  Architecture Architecture Decision Record |  Product Discovery Riskiest Assumption Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-5 Tage | 15-45 min | 1-2 Wochen pro Iteration | 1-5 Tage |
Participantsdifferent | Nutzertraffic | 1-3 | 2-6 | Nutzertraffic |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | ADR File, Decision Log, Rationale | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationExperimentsDemandGrowth | ArchitectureRationaleDocumentationGovernance | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery |