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 |  Innovation Lean Startup |  Innovation Design Sprint |  Product Discovery Pretotyping |
|---|---|---|---|---|
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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 30-60 min je Interview | Wochen bis Monate je Lernzyklus | 4-5 Tage | Stunden bis wenige Tage |
Participantsdifferent | 5-10 Interviews | 2-8 | 5-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Prototype, Test Findings, Decision Rationale | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tags1 shared | ValidationInterviewsPrototype | LeanStartupValidationMVP | Design sprintPrototypeValidationInnovation | ValidationDemandMVP |