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 Research Tree Testing |  UX Design Customer Journey Canvas |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
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 navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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 user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-2 Tage | 1-3 h | 2-4 h |
Participantsdifferent | 10-50 | Based on research question | 3-10 | 4-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Findability Metrics, Path Analysis, Revised IA | Customer Journey Canvas, Pain Points, Experience Opportunities | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | SatisfactionPrioritizationCustomer | Information architectureNavigationFindability | JourneyCustomerService designCanvas | JourneyServiceService design |