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 Specification by Example |  Agile Example Mapping |  Product Discovery Opportunity Interview |  Product Discovery Problem Interview |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 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 | Medium | Low | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 30-60 min je Interview | 30-60 min je Interview |
Participantsdifferent | 3-6 | 3-7 | 5-12 Interviews | 5-12 Interviews |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation |