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 |  Product Discovery Dual-Track Agile |  Agile Example Mapping |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | Laufend, Wochen bis Monate | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 Interviews | 4-10 | 3-7 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Example Map, Acceptance Criteria, Open Questions | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | AgileDiscoveryDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DiscoveryOutcomesExperimentsOpportunity |