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 |  Operations ABC Analysis |  Product Discovery Problem Interview |  Product Discovery Concierge MVP |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 30-60 min | 30-60 min je Interview | 1-4 Wochen |
Participantsdifferent | 10-50 | 1-5 | 5-12 Interviews | 3-10 Kunden |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Problem Evidence, Risk Notes, Customer Segments | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | DiscoveryInterviewsValidation | MVPValidationServiceDiscovery |