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 |  Product Discovery Pretotyping |  Product Strategy Lean Canvas |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 Tage | Stunden bis wenige Tage | 45-90 min |
Participantsdifferent | 10-50 | 1-4 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | SatisfactionPrioritizationCustomer | ValidationDemandMVP | StartupLeanAssumptionsBusiness model |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
