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 |  Product Discovery Outcome-Driven Innovation |  Product Discovery Concierge MVP |  Innovation Design Sprint |
|---|---|---|---|---|
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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 30-60 min je Interview | Mehrere Wochen | 1-4 Wochen | 4-5 Tage |
Participantsdifferent | 5-12 Interviews | 2-6 researchers plus sample | 3-10 Kunden | 5-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Concierge Learnings, Service Blueprint, MVP Risks | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | DiscoveryInterviewsValidation | OutcomesInnovationResearchQuantitative | MVPValidationServiceDiscovery | Design sprintPrototypeValidationInnovation |