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 |  Knowledge Modeling Concept Mapping |  Decision Making Cynefin Workshop |  Domain Modeling Context Map |
|---|---|---|---|---|
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. | 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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-2 h | 60-180 min | 1-3 h |
Participantsdifferent | 3-10 | 1-8 | 4-20 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Concept Map, Relationship Labels, Knowledge Gaps | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | KnowledgeConceptsMappingSensemaking | ComplexitySensemakingDecision | Domain-Driven DesignBoundariesStrategy |