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 Concierge MVP |  Product Discovery Kano Model |  Product Discovery Hypothesis Prioritization Canvas |  Product Discovery Test Card |
|---|---|---|---|---|
Purposedifferent | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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. | When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | 1-2 Tage | 60-90 min | 20-35 min |
Participantsdifferent | 3-10 Kunden | 10-50 | 3-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Concierge Learnings, Service Blueprint, MVP Risks | Kano Matrix, Feature Classes, Priority Themes | Prioritization Canvas, Hypothesis Backlog | Test Card with a pre-set threshold |
Tagsno overlap | MVPValidationServiceDiscovery | SatisfactionPrioritizationCustomer | ExperimentsPrioritizationDiscoveryHypothesis | ExperimentsValidationDiscoveryHypothesis |