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 Topologies Interaction Modes |  Team Design Spotify Model Mapping |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Half day | 90-180 min | 15-45 min | 1-2 Tage |
Participantsdifferent | Team-Leads plus Architecture | 5-15 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |