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 |  Knowledge Modeling Concept Mapping |  Decision Making DACI |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | Half day | 1-2 h | 30-60 min | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | 1-8 | 2-10 | 5-15 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Concept Map, Relationship Labels, Knowledge Gaps | DACI Matrix, Decision Owner, Decision Log | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCollaborationOrganization | KnowledgeConceptsMappingSensemaking | DecisionRolesGovernanceAlignment | TeamOrganizationAlignmentDiagnosis |