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 Design Service Blueprinting | ![]() Product Discovery Jobs to Be Done | ![]() Operations ABC Analysis | ![]() Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | 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 | High | Medium | Low | Medium |
Timedifferent | 0.5-2 Tage | 1-3 Wochen | 30-60 min | 1-2 Tage |
Participantsdifferent | 6-12 | 5-12 Interviews | 1-5 | 10-50 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Job Stories, Outcome Statements, Opportunity List | ABC Classification, Focus Rules, Control List | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | Service designOperationsJourneyBlueprint | CustomerOutcomesNeeds | PrioritizationOperationsPortfolio | SatisfactionPrioritizationCustomer |



