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 Example Mapping |  Product Discovery Opportunity Solution Tree |  Agile Specification by Example |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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 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 | Medium | Medium | Medium |
Timedifferent | 30-60 min | 1-2 h Setup, laufend | 60-90 min pro Feature | 1-5 Tage |
Participantsdifferent | 3-7 | 2-6 | 3-6 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Opportunity Solution Tree, Experiment Backlog, Learning Log | Example Table, Acceptance Tests | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DiscoveryOutcomesExperimentsOpportunity | AgileRequirementsExamplesBehavior-Driven Development | ValidationExperimentsDemandDiscovery |