View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Communication CanvasTeam APITeam Topologies Interaction ModesExpectation Mapping
| Criterion |  Architecture Architecture Communication Canvas |  Team Design Team API |  Team Design Team Topologies Interaction Modes |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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 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 | Low | Medium | Low |
Timedifferent | 60-120 min | Half day initial, dann laufend | Half day | 45-90 min |
Participantsdifferent | 2-8 | Ein Team plus Stakeholder | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Team API Document | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam |