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 | ![]() Team Design Spotify Model Mapping | ![]() Architecture Architecture Decision Record | ![]() Decision Making DACI |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 90-180 min | 15-45 min | 30-60 min |
Participantsdifferent | 3-12 | 5-15 | 1-3 | 2-10 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List | ADR File, Decision Log, Rationale | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernanceAlignment |



