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 Domain Context Map |  Facilitation Team Charter |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 2-4 h | Half day |
Participantsdifferent | 3-10 | 3-12 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Team Charter, Working Norms, Role Notes | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | Domain-Driven DesignContextBoundaries | TeamAlignmentCollaboration | TeamAlignmentCollaborationOrganization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
