methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Purposedifferent
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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 h1-3 Tage30–60 min per interview1-3 h
Participantsdifferent
1-8Internes Team1 participant per interview3-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsPersona Profiles, Needs Summary, Scenario NotesInterview Notes, Themes, Insight SummaryKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
KnowledgeConceptsMappingSensemaking
ResearchCustomerSynthesis
QualitativeResearchCustomerDiscovery
KnowledgeMappingRisk
Add more methods