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 |  Product Discovery Problem Interview |  Product Discovery Test Card |  Agile Example Mapping |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 30-60 min je Interview | 20-35 min | 30-60 min |
Participantsdifferent | 3-6 | 5-12 Interviews | 1-5 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Problem Evidence, Risk Notes, Customer Segments | Test Card with a pre-set threshold | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryHypothesis | Behavior-Driven DevelopmentRequirementsExamplesRefinement |