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 |  Facilitation Team Charter |  Systems Thinking Evaporating Cloud |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 90-180 min | 2-4 h | 60-120 min | 45-90 min |
Participantsdifferent | 5-15 | 3-12 | 2-8 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | Theory of ConstraintsAssumptionsSystems thinking | AlignmentStakeholdersTeam |