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 |  Knowledge Modeling Knowledge Mapping |  Team Design Spotify Model Mapping |  Facilitation Expectation 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. | 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. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 90-180 min | 45-90 min |
Participantsdifferent | 1-8 | 3-12 | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |