View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Team Design Team Topologies Interaction Modes |  Facilitation Expectation Mapping |  Team Design Team API |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | Half day | 45-90 min | Half day initial, dann laufend |
Participantsdifferent | 2-6 | Team-Leads plus Architecture | 3-12 | Ein Team plus Stakeholder |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements | Team API Document |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam | TeamAlignmentCommunicationService |