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 Example Mapping |  Product Discovery Learning Card |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-60 min je Interview | 30-60 min | 25-40 min | 20-40 min pro Story |
Participantsdifferent | 5-12 Interviews | 3-7 | 1-5 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Example Map, Acceptance Criteria, Open Questions | Learning Card with evidence and next action | Acceptance Criteria, Story Update |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ExperimentsValidationDiscoveryLearning | AgileRequirementsRefinementBehavior-Driven Development |