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 |  Knowledge Modeling Knowledge Mapping |  Knowledge Modeling Concept Mapping |  Business Strategy McKinsey 7S |
|---|---|---|---|---|
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. | 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. | 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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 90-180 min | 1-3 h | 1-2 h | 2-4 h |
Participantsdifferent | 5-15 | 3-12 | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps | 7S Assessment, Alignment Gaps, Change Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking | OrganizationStrategyAlignmentChange |