View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Kano ModelCustomer Journey MappingSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Product Discovery Kano Model |  UX Research Customer Journey Mapping |  Architecture Software Architecture 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 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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 2-4 h | 1-2 h | 60-120 min |
Participantsdifferent | 10-50 | 4-10 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Journey Map, Pain-point List, Opportunity Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyServiceService design | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |