The sailboat retro uses a navigation metaphor to make abstract team dynamics concrete. Wind fills the sails. Anchors slow you down. Rocks are risks ahead. The island is the goal. Snap it when you're done.
Use the sailboat retro when a standard column-based retro format feels mechanical, when the team needs a creative reframe, or when you want to make risks and aspirations visible alongside the standard blockers-and-wins conversation.
The metaphor is particularly effective for teams going through a major product push, a challenging quarter, or a period of strategic uncertainty — the ship navigating toward an island captures the shared sense of direction that abstract retrospective formats can miss.
What the team is sailing toward — the sprint goal, the product vision, the quarter's objective. Draw the island on the right side of the board. It anchors the metaphor and reminds the team what the whole journey is for. Write it specifically: not 'build a great product' but 'ship the enterprise onboarding flow by end of Q2.'
The forces pushing the team forward — good decisions, supportive stakeholders, technical investments paying off, excellent teamwork, clear requirements. Draw wind lines filling the sails of the boat. These are the team's accelerants. Name them specifically so you can protect and amplify them.
The forces holding the team back — unclear requirements, technical debt, organizational friction, slow approval processes, missing tools. Draw anchors dragging below the boat. These are the team's impediments. Each anchor should become a proposed action: 'cut this anchor.'
Visible risks on the horizon that haven't become problems yet. Draw rocks sticking out of the water ahead of the boat. These might be upcoming dependencies, potential team changes, approaching deadlines, or technical uncertainties. Naming risks before they materialize is the most valuable thing the retro can do.
Some teams add a sun above the boat for things that energize the team: culture wins, celebration moments, sources of motivation. This element is optional but valuable for teams whose Anchors tend to dominate the conversation — the sun keeps the board from being all problems.
Draw a boat in the center-left, an island on the right, wind lines on the upper left, anchors below, and rocks ahead. Label the goal on the island. The physical drawing is part of the session — it signals that this retro will be different from the standard column format.
Before adding any other stickies, write the sprint or quarter goal on the island. This anchors the entire conversation. Everything the team places on the board should relate to the journey toward that goal.
Everyone writes stickies for all elements simultaneously. Encourage at least one sticky per element — especially Rocks, which teams often underinvest in.
Post stickies in the appropriate sections. Read each one aloud. Ask: 'Is this a Wind (accelerant), an Anchor (impediment), or a Rock (risk)?' The categorization is part of the discussion.
For each Anchor: what specific action would cut it? For each Rock: what's the mitigation plan? These conversations are the core product of the session.
Snap the diagram with BoardSnap. The AI reads the metaphor structure and outputs action items for cutting anchors and mitigating rocks — with the goal preserved as context.
The sailboat retro produces a genuinely visual diagram — a boat, a scene, a destination. Digital retro tools turn this into a themed template with text boxes. A physical whiteboard lets you draw the actual scene: a hand-drawn boat with waves, anchors with chains, rocks with spray. That visual engagement produces more creative and more honest input than a form.
BoardSnap reads the visual structure — where stickies sit relative to the boat, the island, and the rocks — and outputs a summary organized by metaphor element. The wind items become what to protect; the anchors and rocks become the action items.
The sailboat (or speedboat) retrospective format is most commonly attributed to Luke Hohmann, who included a version in his book 'Innovation Games.' The specific sailboat variant with wind, anchors, rocks, and island has evolved through agile community practice and exists in several forms — the one described here includes all four standard elements.
The speedboat retro focuses on what slows the team down (anchors) and what drives them forward (engines/motors), with less emphasis on risks. The sailboat retro adds the Rocks element (forward risks) and the Island (goal), making it more complete. Both use vehicle metaphors; the sailboat format is more commonly used for team-level retrospectives.
It tends to work particularly well with creative, design-oriented, or product-focused teams that respond well to metaphor. It can feel childish to some engineering teams who prefer direct formats — read the room before choosing this over a more literal retro format. If the team draws enthusiastically on the sailboat, that's a good sign.
Move the sticky. The physical board lets you do this in real time. A Rock that becomes an Anchor during the sprint is its own signal — you saw it coming and didn't mitigate it. That gap becomes an action item for the retro's meta-process: how do we turn risk identification into risk mitigation?
No exporting, no transcription. Snap the board, get the action plan.