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 Spotify Model Mapping |  Facilitation Team Charter |  Agile Starfish Retrospective |  Team Design Team Cognitive Load Assessment |
|---|---|---|---|---|
Purposedifferent | 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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 2-4 h | 45-90 min | 60-90 min |
Participantsdifferent | 5-15 | 3-12 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | Starfish Board, Practice Changes, Experiments | Cognitive Load Profile, Action List |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | RetrospectiveImprovementExperimentsTeam | TeamComplexityImprovementDiagnosis |