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 Team Cognitive Load Assessment |  Systems Thinking Evaporating Cloud |  Facilitation Alignment Mapping |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-90 min | 60-120 min | 1-2 h | 90-180 min |
Participantsdifferent | 3-12 | 2-8 | 4-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Alignment Map, Open Issues, Decision Questions | Spotify Model Map, Action List |
Tagsno overlap | TeamComplexityImprovementDiagnosis | Theory of ConstraintsAssumptionsSystems thinking | AlignmentStakeholdersStrategyFacilitation | TeamOrganizationAlignmentDiagnosis |