View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 60–90 min |
Participantsdifferent | 4-12 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
