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 Context Canvas |  Product Discovery Experiment Canvas |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 45-90 min | 30-60 min | 1-5 Tage |
Participantsdifferent | 3-6 | 3-10 | 1-5 | Nutzertraffic |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Example Table, Acceptance Tests | Context canvas, Open questions, Shared context notes | Completed Experiment Canvas, Success Metric | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ContextFramingRequirementsCanvas | ExperimentsValidationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |