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 |  Decision Making RAPID |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | Half day | 45-90 min | 90-180 min |
Participantsdifferent | 1-3 | Team-Leads plus Architecture | 3-12 | 5-15 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Interaction Heat Map, Agreements per Pair | RAPID Role Map, Recommendation, Decision Log | Spotify Model Map, Action List |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TeamAlignmentCollaborationOrganization | DecisionRolesGovernance | TeamOrganizationAlignmentDiagnosis |