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 Alignment Mapping | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 4-12 | 4-12 | 4-12 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |



