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 |  Engineering Kanban |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | Ongoing | 60-90 min |
Participantsdifferent | 2-8 | 2-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Kanban board, WIP policies, Flow metrics | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | FlowVisual managementDelivery | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
