View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Domain Modeling Bounded Context Canvas | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Context Canvas, Glossary, Integration Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesModeling | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






