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 Test Card |  Agile Example Mapping |  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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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 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 | 20-35 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 5-12 Interviews | 1-5 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Test Card with a pre-set threshold | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ExperimentsValidationDiscoveryHypothesis | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |