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 Request for Comments |  Team Design Team Topologies Interaction Modes |  Decision Making DACI |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Half day | 30-60 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | Team-Leads plus Architecture | 2-10 | 5-15 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Interaction Heat Map, Agreements per Pair | DACI Matrix, Decision Owner, Decision Log | Spotify Model Map, Action List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TeamAlignmentCollaborationOrganization | DecisionRolesGovernanceAlignment | TeamOrganizationAlignmentDiagnosis |