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 Research Customer Journey Mapping | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 1-3 h | 2-4 h | 1-2 h |
Participantsdifferent | 10-50 | 3-10 | 4-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | Journey Map, Pain-point List, Opportunity Backlog | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | JourneyServiceService design | AlignmentArchitectureCanvas |



