View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  UX Research Contextual Inquiry |  Domain Modeling Bounded Context Canvas |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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 | Medium | Medium |
Timedifferent | 1-2 h | 1-3 Wochen | 1-3 h | 1-2 h |
Participantsdifferent | 2-8 | 4-12 Beobachtungen | 3-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Field Notes, Workflow Insights, Pain Points | Context Canvas, Glossary, Integration Notes | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | UX researchObservationContext | Domain-Driven DesignBoundariesModeling | KnowledgeConceptsMappingSensemaking |