Sailboat Retrospective
A visual metaphor that makes agile reflection feel less routine.
The Sailboat retrospective uses a nautical metaphor to help teams think about the forces shaping their sprint: what pushed them forward, what slowed them down, what risks lie ahead, and what goal they are sailing toward.
Board columns
Wind
What helped the team move faster? Practices, tools, teammates, or external factors that accelerated progress and should be amplified.
Anchors
What slowed the team down? Blockers, slow processes, unclear decisions, or dependencies that acted as drag on velocity.
Rocks
What risks or obstacles are ahead? Known threats to the next sprint—tech debt, upcoming dependencies, or external pressures.
Island
What is the team's goal? The destination everyone is sailing toward—sprint goal, OKR, or quarterly milestone.
When to use this template
Sailboat works best for quarterly reviews, cross-functional teams, or when the standard Start/Stop/Continue format feels stale. The metaphor makes abstract concepts tangible and encourages creative thinking.
How to run it
- 1
Draw or display the metaphor: a boat, sails, anchor, rocks beneath the surface, and an island in the distance.
- 2
Brief the team on each element.
- 3
Give 8 minutes to write cards privately.
- 4
Reveal and cluster Anchors by theme—these become your action candidates.
- 5
Vote on which anchors to address next sprint.
- 6
Confirm the Island is still the right goal before closing.
Facilitation tips
Spend extra time on Rocks—surfacing risks early is the most underrated part of retros.
Keep the Island visible throughout the discussion to anchor action items to the goal.
If the team cannot agree on the Island, that misalignment is itself the most important retro outcome.
Run your next retrospective free
paraboll.online is free with no signup. Facilitate any retro format with your team in seconds.
Start free retro