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 Assumption Mapping |  Growth A/B Testing |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 45-60 min | 1-4 Wochen | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 1-6 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Assumption map, Test backlog, Risk ranking | Experiment results, Decision log, Learning summary | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | AssumptionsRiskExperimentsValidation | ExperimentsGrowthAnalyticsValidation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |