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 | ![]() Facilitation Expectation Mapping | ![]() Innovation Design Charrette | ![]() Team Design Spotify Model 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. | 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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Half day | 45-90 min | Halber Tag bis mehrere Tage | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | 3-12 | 10-50 | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam | BrainstormingWorkshopCollaborationIdeation | TeamOrganizationAlignmentDiagnosis |



