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 Context Map |  Knowledge Modeling Concept Mapping |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 60-90 min | 60–90 min |
Participantsdifferent | 2-8 | 1-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Concept Map, Relationship Labels, Knowledge Gaps | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | KnowledgeConceptsMappingSensemaking | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |