View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Team Design Team Topologies Interaction Modes |  Team Design Team API |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Half day | Half day initial, dann laufend | 2-4 h |
Participantsdifferent | 1-3 | Team-Leads plus Architecture | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Interaction Heat Map, Agreements per Pair | Team API Document | Team Charter, Working Norms, Role Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TeamAlignmentCollaborationOrganization | TeamAlignmentCommunicationService | TeamAlignmentCollaboration |