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 Concept Mapping | ![]() Domain Modeling Bounded Context Canvas | ![]() Business Strategy Value Chain Analysis | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
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 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. | 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 | Medium | Medium | High | Medium |
Timedifferent | 1-2 h | 1-3 h | Half day | 1-3 h |
Participantsdifferent | 1-8 | 3-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Context Canvas, Glossary, Integration Notes | Value Chain Map, Lever List | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignBoundariesModeling | StrategyBusiness modelDiagnosisAnalysis | Domain-Driven DesignBoundariesStrategy |



