View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Product Discovery Opportunity Interview |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30–60 min per interview | 30-60 min je Interview | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 1 participant per interview | 5-12 Interviews | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Interview Notes, Opportunity Themes, Customer Quotes | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | QualitativeResearchCustomerDiscovery | DiscoveryInterviewsOpportunityCustomer | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |