View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Product Discovery Smoke Test |  Product Discovery Fake Door Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 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 | Medium | Low | Medium | High |
Timedifferent | 60-90 min pro Feature | 1-5 Tage | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-6 | Nutzertraffic | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Async | Async | Async |
Outputdifferent | Example Table, Acceptance Tests | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision | Experiment results, Decision log, Learning summary |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery | ExperimentsGrowthAnalyticsValidation |