View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Team Charter | ![]() Architecture Architecture Decision Record | ![]() Decision Making DACI | ![]() Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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 | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 15-45 min | 30-60 min | Half day |
Participantsdifferent | 3-12 | 1-3 | 2-10 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | ADR File, Decision Log, Rationale | DACI Matrix, Decision Owner, Decision Log | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernanceAlignment | TeamAlignmentCollaborationOrganization |



