Sailboat retro
Definition
A retrospective format using a sailboat metaphor with four zones: wind (things that propel the team), anchors (things that slow progress), rocks (risks ahead), and the island (the goal or destination).
The sailboat retro — sometimes called the speedboat retro depending on the vessel drawn — replaces abstract column headers with a visual narrative. The team draws a boat, an island in the distance, wind blowing from behind, an anchor dragging below, and rocks lurking ahead. Then everyone adds sticky notes to the relevant zones.
Why the metaphor works: Concrete visuals lower the facilitation barrier and make the conversation more accessible for non-technical teams, new hires, and mixed stakeholder groups. The metaphor also naturally introduces forward-looking thinking — the island (goal) and the rocks (risks) both push the team to think beyond the current sprint.
How it runs: The facilitator sketches the metaphor on a whiteboard in about two minutes. Teams spend five to ten minutes adding sticky notes. Discussion focuses on the anchors (impediments) and rocks (upcoming risks) because those produce the clearest action items. The island prompts the team to restate the goal explicitly, which is valuable when teams have lost sight of the destination.
When to use it: Great for quarterly planning, project kickoffs and retrospectives, and workshops where the audience isn't a regular Scrum team. Also useful when standard column-based retros have gone stale.
BoardSnap and the sailboat: The visual nature of this retro is exactly what BoardSnap handles well. Snap the whiteboard — boat diagram and all — and BoardSnap AI reads each labeled zone, extracts the sticky note content, and outputs a structured summary organized by wind, anchor, rocks, and island. No transcription needed.
Examples
- Wind: the new CI/CD pipeline ships code in 8 minutes. Anchor: waiting three days for security review. Rocks: migrating the legacy database next sprint. Island: launch the mobile app by end of quarter.
- A product team uses the sailboat retro at the end of a major feature cycle to reflect on pace, blockers, and what's next.
- A consulting team runs a sailboat retro with a client in a workshop setting — the metaphor makes it easy for non-Agile stakeholders to participate.
- An engineering org uses the sailboat format for quarterly retrospectives to complement the start / stop / continue format they use at the sprint level.
Snap a sailboat retro. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.