View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making DACI |  Facilitation Team Charter |  Architecture Request for Comments |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | Half day |
Participantsdifferent | 2-10 | 3-12 | 3-20 Reviewer | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | DACI Matrix, Decision Owner, Decision Log | Team Charter, Working Norms, Role Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | DecisionRolesGovernanceAlignment | TeamAlignmentCollaboration | ArchitectureDecisionAsyncGovernance | TeamAlignmentCollaborationOrganization |