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 | ![]() Facilitation Dot Voting | ![]() UX Research Customer Journey Mapping | ![]() UX Design Service Blueprinting |
|---|---|---|---|---|
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 workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-2 Tage | 5-15 min | 2-4 h | 0.5-2 Tage |
Participantsdifferent | 10-50 | 3-20 | 4-10 | 6-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Ranked list, Consensus signal, Shortlist | Journey Map, Pain-point List, Opportunity Backlog | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | SatisfactionPrioritizationCustomer | FacilitationVotingConsensusPrioritization | JourneyServiceService design | Service designOperationsJourneyBlueprint |



