View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Team Design Team Topologies Interaction Modes |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | Half day | 15-45 min |
Participantsdifferent | Ein Team plus Stakeholder | Team-Leads plus Architecture | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Team API Document | Interaction Heat Map, Agreements per Pair | ADR File, Decision Log, Rationale |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
