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 |  Knowledge Modeling Concept Mapping |  Business Strategy Value Chain Analysis |  Domain Modeling Context Map |
|---|---|---|---|---|
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. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 1-2 h | 1-2 h | Half day | 1-3 h |
Participantsdifferent | 2-8 | 1-8 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Concept Map, Relationship Labels, Knowledge Gaps | Value Chain Map, Lever List | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | KnowledgeConceptsMappingSensemaking | StrategyBusiness modelDiagnosisAnalysis | Domain-Driven DesignBoundariesStrategy |