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 Jobs to Be Done |  UX Research Contextual Inquiry |  Operations ABC Analysis |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | 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 work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-3 Wochen | 30-60 min | 1-2 Tage |
Participantsdifferent | 5-12 Interviews | 4-12 Beobachtungen | 1-5 | 10-50 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Field Notes, Workflow Insights, Pain Points | ABC Classification, Focus Rules, Control List | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | CustomerOutcomesNeeds | UX researchObservationContext | PrioritizationOperationsPortfolio | SatisfactionPrioritizationCustomer |