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 |  Delivery RAID Log |  Product Discovery Fake Door Test |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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 | 30 min Setup, dann laufend | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 1-3 maintaining, briefing for everyone | Nutzertraffic | 1-6 |
Formatsame | Async | Async | Async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | RAID Log, Status Report Source | Click Data, Interest Signal, Learning Decision | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandDiscovery | ExperimentsGrowthAnalyticsValidation |