View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research User Interviews | ![]() UX Design Service Blueprinting | ![]() Product Discovery Kano Model | ![]() Product Discovery Hypothesis Prioritization Canvas |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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 many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30–60 min per interview | 0.5-2 Tage | 1-2 Tage | 60-90 min |
Participantsdifferent | 1 participant per interview | 6-12 | 10-50 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Service Blueprint, Fail Points, Ownership Map | Kano Matrix, Feature Classes, Priority Themes | Prioritization Canvas, Hypothesis Backlog |
Tagsno overlap | QualitativeResearchCustomerDiscovery | Service designOperationsJourneyBlueprint | SatisfactionPrioritizationCustomer | ExperimentsPrioritizationDiscoveryHypothesis |



