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 |  Facilitation Responsibility Poker |  Facilitation Delegation Poker |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 45-90 min | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 3-10 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Responsibility Map, Role Agreements, Open Questions | Delegation Board, Decision Boundaries, Role Agreements | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RolesResponsibilityTeamFacilitation | AutonomyRolesTeam | Domain-Driven DesignBoundariesModeling |