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 Customer Journey Canvas |  Product Discovery Kano Model |  Architecture Software Architecture Canvas |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
Purposedifferent | 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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-2 Tage | 1-2 h | 2-4 h |
Participantsdifferent | 3-10 | 10-50 | 3-10 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Kano Matrix, Feature Classes, Priority Themes | Architecture Canvas, Goals, Constraints, Quality Attributes | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | JourneyCustomerService designCanvas | SatisfactionPrioritizationCustomer | CanvasArchitectureAlignmentWorkshop | JourneyServiceService design |