View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Agile Example Mapping |  Product Discovery Dual-Track Agile |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30–60 min per interview | 30-60 min | Laufend, Wochen bis Monate | 30-60 min je Interview |
Participantsdifferent | 1 participant per interview | 3-7 | 4-10 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Example Map, Acceptance Criteria, Open Questions | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileDiscoveryDelivery | DiscoveryInterviewsOpportunityCustomer |