View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Team Design Spotify Model Mapping |  Systems Thinking Evaporating Cloud |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 90-180 min | 60-120 min |
Participantsdifferent | 3-12 | 5-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Spotify Model Map, Action List | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | Systems thinkingMappingBoundariesChange | TeamOrganizationAlignmentDiagnosis | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
