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 |  Knowledge Modeling Concept Mapping |  Product Discovery Hypothesis Prioritization Canvas |  Product Discovery Kano Model |
|---|---|---|---|---|
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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30–60 min per interview | 1-2 h | 60-90 min | 1-2 Tage |
Participantsdifferent | 1 participant per interview | 1-8 | 3-8 | 10-50 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Concept Map, Relationship Labels, Knowledge Gaps | Prioritization Canvas, Hypothesis Backlog | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | KnowledgeConceptsMappingSensemaking | ExperimentsPrioritizationDiscoveryHypothesis | SatisfactionPrioritizationCustomer |