View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  UX Research Contextual Inquiry |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen | 1-2 h | 1-3 h |
Participantsdifferent | 3-10 | 4-12 Beobachtungen | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Field Notes, Workflow Insights, Pain Points | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | Domain-Driven DesignContextBoundaries | UX researchObservationContext | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk |