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 Dual-Track Agile |  Product Discovery Problem Interview |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | Laufend, Wochen bis Monate | 30-60 min je Interview | 30-60 min |
Participantsdifferent | 3-6 | 4-10 | 5-12 Interviews | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Problem Evidence, Risk Notes, Customer Segments | Completed Experiment Canvas, Success Metric |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryHypothesis |