View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Systems Thinking CATWOE Analysis |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | Half day | 45-90 min | 90-180 min |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | 3-8 | 5-15 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Spotify Model Map, Action List |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | Systems thinkingFramingStakeholders | TeamOrganizationAlignmentDiagnosis |