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 Knowledge Mapping |  Knowledge Modeling Domain Storytelling |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30–60 min per interview | 1-3 h | 1-2 h | 1-2 h |
Participantsdifferent | 1 participant per interview | 3-12 | 2-8 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Domain Story, Glossary Notes, Process Narrative | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | QualitativeResearchCustomerDiscovery | KnowledgeMappingRisk | KnowledgeDomain-Driven DesignProcess | KnowledgeConceptsMappingSensemaking |