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 Spotify Model Mapping |  Team Design Team Topologies Interaction Modes |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 90-180 min | Half day | 1-2 h | 1-3 h |
Participantsdifferent | 5-15 | Team-Leads plus Architecture | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk |