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 Acceptance Criteria Workshop |  Agile Example Mapping |  Product Discovery Problem Interview |
|---|---|---|---|---|
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 needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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 | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 20-40 min pro Story | 30-60 min | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 3-6 | 3-7 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DiscoveryInterviewsValidation |