View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Operations ABC Analysis |  Product Discovery Jobs to Be Done |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30–60 min per interview | 30-60 min | 1-3 Wochen | 1-2 Tage |
Participantsdifferent | 1 participant per interview | 1-5 | 5-12 Interviews | 10-50 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | ABC Classification, Focus Rules, Control List | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | PrioritizationOperationsPortfolio | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer |