View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingSailboat RetrospectiveSpotify Model MappingTeam Cognitive Load Assessment
| Criterion |  Facilitation Expectation Mapping |  Agile Sailboat Retrospective |  Team Design Spotify Model Mapping |  Team Design Team Cognitive Load Assessment |
|---|---|---|---|---|
Purposedifferent | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 45-90 min | 90-180 min | 60-90 min |
Participantsdifferent | 3-12 | 4-12 | 5-15 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Sailboat Board, Risks, Improvement Actions | Spotify Model Map, Action List | Cognitive Load Profile, Action List |
Tags1 shared | AlignmentStakeholdersTeam | RetrospectiveTeamImprovement | TeamOrganizationAlignmentDiagnosis | TeamComplexityImprovementDiagnosis |