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 Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 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. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 45-90 min | Half day | 1-2 h |
Participantsdifferent | 2-8 | 3-12 | Team-Leads plus Architecture | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersStrategyFacilitation |