View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Responsibility Poker |  Domain Modeling Bounded Context Canvas |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 60–90 min | 45-90 min |
Participantsdifferent | 3-10 | 3-8 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Context Canvas, Glossary, Integration Notes | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Domain-Driven DesignBoundariesModeling | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |