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 Solution Interview |  Product Discovery Wizard of Oz Test |  Product Discovery Outcome-Driven Innovation |  Innovation Design Thinking |
|---|---|---|---|---|
Purposedifferent | 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. | When a new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears. | 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. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 30-60 min je Interview | 2-10 Tage | Mehrere Wochen | 1 Tag bis mehrere Wochen |
Participantsdifferent | 5-10 Interviews | 5-20 Nutzer | 2-6 researchers plus sample | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Prototype Learnings, Manual Effort Notes, Risk List | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ValidationInterviewsPrototype | PrototypeValidationMVP | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch |