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 Bounded Context Canvas |  Team Design Team Topologies Interaction Modes |  Facilitation Team Charter |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Half day | 2-4 h | 45-90 min |
Participantsdifferent | 3-8 | Team-Leads plus Architecture | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Interaction Heat Map, Agreements per Pair | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | TeamAlignmentCollaborationOrganization | TeamAlignmentCollaboration | AlignmentStakeholdersTeam |