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 Outcome-Driven Innovation |  Innovation Design Thinking |  Product Discovery Problem Interview |  Product Discovery Solution Interview |
|---|---|---|---|---|
Purposedifferent | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. |
Complexitydifferent | High | High | Medium | Medium |
Timedifferent | Mehrere Wochen | 1 Tag bis mehrere Wochen | 30-60 min je Interview | 30-60 min je Interview |
Participantsdifferent | 2-6 researchers plus sample | 4-10 | 5-12 Interviews | 5-10 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings | Problem Evidence, Risk Notes, Customer Segments | Solution Feedback, Objection List, Validation Notes |
Tagsno overlap | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch | DiscoveryInterviewsValidation | ValidationInterviewsPrototype |