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 | ![]() UX Design Customer Journey Canvas | ![]() Operations ABC Analysis | ![]() UX Design Service Blueprinting |
|---|---|---|---|---|
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. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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 a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-2 Tage | 1-3 h | 30-60 min | 0.5-2 Tage |
Participantsdifferent | 10-50 | 3-10 | 1-5 | 6-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | ABC Classification, Focus Rules, Control List | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | PrioritizationOperationsPortfolio | Service designOperationsJourneyBlueprint |



