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 |  UX Design Service Blueprinting |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 0.5-2 Tage | 45-90 min |
Participantsdifferent | 10-50 | 3-10 | 6-12 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | Service Blueprint, Fail Points, Ownership Map | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | Service designOperationsJourneyBlueprint | LeanProblem solvingCoachingOperations |