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 |  Decision Making DACI |  Architecture Request for Comments |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | Half day | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Team-Leads plus Architecture | 2-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Interaction Heat Map, Agreements per Pair | DACI Matrix, Decision Owner, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | TeamAlignmentCollaborationOrganization | DecisionRolesGovernanceAlignment | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
