View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Agile Sailboat Retrospective |  Team Design Spotify Model Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 90-180 min | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 5-15 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Sailboat Board, Risks, Improvement Actions | Spotify Model Map, Action List | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ProcessOperationsImprovement | RetrospectiveTeamImprovement | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementExperimentsTeam |