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 Evaporating Cloud |  Systems Thinking Intervention Mapping |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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 | High | Medium | Low |
Timedifferent | 60-120 min | 1-5 Tage | 90-180 min | 45-90 min |
Participantsdifferent | 2-8 | 4-12 | 5-15 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ChangeSystems thinkingCapability | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |