View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Cognitive Load AssessmentSailboat RetrospectiveStarfish RetrospectiveSpotify Model Mapping
| Criterion |  Team Design Team Cognitive Load Assessment |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |  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. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min | 45-90 min | 45-90 min | 90-180 min |
Participantsdifferent | 3-12 | 4-12 | 4-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Spotify Model Map, Action List |
Tags1 shared | TeamComplexityImprovementDiagnosis | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | TeamOrganizationAlignmentDiagnosis |