View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingTeam Topologies Interaction ModesTeam APIArchitecture Communication Canvas
| Criterion |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Team Design Team API |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | Half day | Half day initial, dann laufend | 60-120 min |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | Ein Team plus Stakeholder | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas |