View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Design Thinking | ![]() Product Discovery Problem Interview | ![]() Product Discovery Wizard of Oz Test | ![]() Innovation Design Sprint |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 | High | Medium | High | High |
Timedifferent | 1 Tag bis mehrere Wochen | 30-60 min je Interview | 2-10 Tage | 4-5 Tage |
Participantsdifferent | 4-10 | 5-12 Interviews | 5-20 Nutzer | 5-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Problem Evidence, Risk Notes, Customer Segments | Prototype Learnings, Manual Effort Notes, Risk List | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | InnovationPrototypeResearch | DiscoveryInterviewsValidation | PrototypeValidationMVP | Design sprintPrototypeValidationInnovation |



