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 |  Facilitation Consensus Workshop |  Architecture Software Architecture 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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 1-3 h | 1-3 h | 1-2 h |
Participantsdifferent | 10-50 | 3-10 | 5-30 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | Consensus Clusters, Theme Titles, Priority Areas | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | FacilitationConsensusWorkshopAlignment | CanvasArchitectureAlignmentWorkshop |