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 Pretotyping |  Product Discovery Problem Interview |  Innovation Design Thinking |  Product Discovery Solution Interview |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. | 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 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 | Low | Medium | High | Medium |
Timedifferent | Stunden bis wenige Tage | 30-60 min je Interview | 1 Tag bis mehrere Wochen | 30-60 min je Interview |
Participantsdifferent | 1-4 | 5-12 Interviews | 4-10 | 5-10 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Problem Evidence, Risk Notes, Customer Segments | Problem Statement, Prototype, Test Learnings | Solution Feedback, Objection List, Validation Notes |
Tagsno overlap | ValidationDemandMVP | DiscoveryInterviewsValidation | InnovationPrototypeResearch | ValidationInterviewsPrototype |