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 Interview |  Agile Example Mapping |  Product Discovery Opportunity Solution Tree |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min | 1-2 h Setup, laufend | 60-90 min pro Feature |
Participantsdifferent | 5-12 Interviews | 3-7 | 2-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Example Map, Acceptance Criteria, Open Questions | Opportunity Solution Tree, Experiment Backlog, Learning Log | Example Table, Acceptance Tests |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DiscoveryOutcomesExperimentsOpportunity | AgileRequirementsExamplesBehavior-Driven Development |