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 Lean Startup |  Product Discovery Solution Interview |  Product Discovery Pretotyping |  Innovation Design Sprint |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 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 | Medium | Medium | Low | High |
Timedifferent | Wochen bis Monate je Lernzyklus | 30-60 min je Interview | Stunden bis wenige Tage | 4-5 Tage |
Participantsdifferent | 2-8 | 5-10 Interviews | 1-4 | 5-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Solution Feedback, Objection List, Validation Notes | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prototype, Test Findings, Decision Rationale |
Tags1 shared | LeanStartupValidationMVP | ValidationInterviewsPrototype | ValidationDemandMVP | Design sprintPrototypeValidationInnovation |