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 Opportunity Solution Tree |  Product Discovery Test Card |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 1-2 h Setup, laufend | 20-35 min | 1-5 Tage |
Participantsdifferent | 3-6 | 2-6 | 1-5 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Example Table, Acceptance Tests | Opportunity Solution Tree, Experiment Backlog, Learning Log | Test Card with a pre-set threshold | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | DiscoveryOutcomesExperimentsOpportunity | ExperimentsValidationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |