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 Spotify Model Mapping |  Systems Thinking Evaporating Cloud |  Facilitation Expectation Mapping |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | 5-15 | 2-8 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Expectation Map, Alignment Notes, Agreements | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | Theory of ConstraintsAssumptionsSystems thinking | AlignmentStakeholdersTeam | Systems thinkingFramingStakeholders |