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 Kano Model |  Innovation Lean Startup |  Product Strategy Lean Canvas |  Product Discovery Pretotyping |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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 | Medium | Low |
Timedifferent | 1-2 Tage | Wochen bis Monate je Lernzyklus | 45-90 min | Stunden bis wenige Tage |
Participantsdifferent | 10-50 | 2-8 | 1-6 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Lean Canvas, Core Assumptions, Experiment Backlog | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanStartupValidationMVP | StartupLeanAssumptionsBusiness model | ValidationDemandMVP |