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 Problem Interview |  Agile Specification by Example |  Product Discovery Dual-Track Agile |  Product Discovery Concierge MVP |
|---|---|---|---|---|
Purposedifferent | 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 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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 60-90 min pro Feature | Laufend, Wochen bis Monate | 1-4 Wochen |
Participantsdifferent | 5-12 Interviews | 3-6 | 4-10 | 3-10 Kunden |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | DiscoveryInterviewsValidation | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery | MVPValidationServiceDiscovery |