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 |  UX Research User Interviews |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 Tage | 30-60 min | 30–60 min per interview | 30-60 min je Interview |
Participantsdifferent | 10-50 | 1-5 | 1 participant per interview | 5-12 Interviews |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Interview Notes, Themes, Insight Summary | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | QualitativeResearchCustomerDiscovery | DiscoveryInterviewsOpportunityCustomer |