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 |  Architecture Architecture Communication 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 60-120 min |
Participantsdifferent | 10-50 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
