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 Opportunity Solution Tree |  Agile Example Mapping |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 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 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 | 30-60 min je Interview | 1-2 h Setup, laufend | 30-60 min | 1-5 Tage |
Participantsdifferent | 5-12 Interviews | 2-6 | 3-7 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Opportunity Solution Tree, Experiment Backlog, Learning Log | Example Map, Acceptance Criteria, Open Questions | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DiscoveryOutcomesExperimentsOpportunity | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ValidationExperimentsDemandDiscovery |