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 Smoke Test |  Product Discovery Assumption 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 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 1-5 Tage | 45-60 min |
Participantsdifferent | 3-6 | 3-7 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation |