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 Opportunity Solution Tree |  Agile Example Mapping |  Agile Specification by Example |  Product Discovery Dual-Track Agile |
|---|---|---|---|---|
Purposedifferent | 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 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 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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h Setup, laufend | 30-60 min | 60-90 min pro Feature | Laufend, Wochen bis Monate |
Participantsdifferent | 2-6 | 3-7 | 3-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery |