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