View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Product Discovery Dual-Track Agile |  Product Discovery Opportunity Interview |  Product Discovery Problem Interview |
|---|---|---|---|---|
Purposedifferent | 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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | Laufend, Wochen bis Monate | 30-60 min je Interview | 30-60 min je Interview |
Participantsdifferent | 3-7 | 4-10 | 5-12 Interviews | 5-12 Interviews |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileDiscoveryDelivery | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation |