View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Team Design Spotify Model Mapping |  Facilitation Team Charter |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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 | 1-2 h | 90-180 min | 2-4 h | 1-3 h |
Participantsdifferent | 1-8 | 5-15 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | KnowledgeMappingRisk |