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 |  Team Design Spotify Model Mapping |  Knowledge Modeling Concept Mapping |  Facilitation Team Charter |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Half day | 90-180 min | 1-2 h | 2-4 h |
Participantsdifferent | Team-Leads plus Architecture | 5-15 | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | Concept Map, Relationship Labels, Knowledge Gaps | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | KnowledgeConceptsMappingSensemaking | TeamAlignmentCollaboration |