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 |  Systems Thinking Evaporating Cloud |  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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | 60-120 min | 90-180 min | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | 2-8 | 5-15 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaborationOrganization | Theory of ConstraintsAssumptionsSystems thinking | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |