View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Topologies Interaction ModesArchitecture Decision Recordarc42Architecture Communication Canvas
| Criterion |  Team Design Team Topologies Interaction Modes |  Architecture Architecture Decision Record |  Architecture arc42 |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Medium | Low | Low | Medium |
Timedifferent | Half day | 15-45 min | 1-2 Tage | 60-120 min |
Participantsdifferent | Team-Leads plus Architecture | 1-3 | 1-4 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Interaction Heat Map, Agreements per Pair | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCollaborationOrganization | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |