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 | ![]() Operations Process Mapping | ![]() Agile Mad Sad Glad | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 90-180 min | 1-3 h | 30-60 min | 45-90 min |
Participantsdifferent | 5-15 | 3-10 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Process Map, Handoff List, Improvement Backlog | Emotion Board, Themes, Action Items | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ProcessOperationsImprovement | RetrospectiveTeamReflection | RetrospectiveTeamImprovement |



