Sailboat Retrospective

A visual metaphor the whole team gets instantly: what propels us, what drags us, what could sink us.

Use this template free

Free · No credit card · Guests join by link

The board

WIND

What is pushing us forward?

ANCHORS

What is slowing us down?

ROCKS

What risks lie ahead?

The Sailboat retrospective wraps the sprint in a single picture: your team is a boat sailing toward an island (the goal). Wind fills the sails and pushes you forward, anchors drag below the waterline and slow you down, and rocks lie ahead — risks that could sink the journey entirely.

The metaphor does real work. Because people describe the boat rather than each other, criticism depersonalizes naturally — 'the anchor is our release process' lands very differently from 'you slow down releases.' That makes Sailboat one of the safest formats for teams with unresolved tension.

Teams call it many things: the sailboat retro, sail boat, sailing boat or simply the boat retrospective. Some versions add a sun for what makes the team happy; the Speedboat and Speed Car retrospectives swap the boat for an engine but keep the same idea.

When to use a Sailboat Retrospective

Cross-functional or newly merged teams that need a shared, neutral vocabulary
When past retros turned into finger-pointing — the metaphor absorbs the blame
Forward-looking checkpoints: Rocks makes this one of the few formats that captures future risk, not just past friction
Kickoffs: run it at the start of a project to map tailwinds and hazards early

How to run a Sailboat Retrospective

1
Set the island
Before writing, the facilitator states the goal — the island the boat sails toward. In Retromik, put it in the board's focus question so it stays visible above every column.
2
Check that everyone sees the same island
Ask two or three people to describe the island in their own words before anyone writes. If the descriptions differ, that's the first finding of the retro, and the rest of the board will make more sense once it's settled.
3
Separate anchors from rocks
An anchor is dragging the boat today. A rock hasn't been hit yet. Ask people to put each card where it belongs; mixing them hides the risks behind the complaints.
4
Turn wind into something you can repeat
For the strongest wind cards, ask what made them happen. A tailwind you understand is one you can create again next sprint.
5
Chart a course around the rocks
For each top rock, agree on an early warning sign and an owner. For the heaviest anchor, agree on one thing to cut it loose.

Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.

Read the full facilitation guide

Example cards

What good cards look like for a software team. Specific, about the work, never about a person.

WIND

The design system made new screens twice as fast to build.
Product answered questions the same day.
Feature flags let us ship the checkout changes in small pieces.

ANCHORS

Manual release steps take half a day every time.
Support tickets reach us through three different channels.
We still wait a week for security reviews.

ROCKS

The payment provider's API version is retired in March.
Nobody owns the reporting service since the reorg.
Marketing has announced a launch date we haven't estimated.

A 45-minute agenda

0–5 minSet the island and check everyone sees the same one
5–15 minWrite wind, anchor and rock cards silently
15–20 minVote, three votes each
20–35 minDiscuss the heaviest anchors and the closest rocks
35–45 minAgree actions: one anchor to cut, an owner and early warning for each top rock

Common mistakes

No island. Without a goal, wind and anchors have no direction and the board turns into a general list of likes and dislikes.
Rocks that are really anchors. If it's already slowing you down, it isn't a rock.
Spending the whole session on anchors and never reaching the rocks, which is where Sailboat is most useful.
Drawing the picture takes longer than the retro. A simple board with the three columns is enough.

Frequently asked questions

What is a Sailboat retrospective?

A visual retrospective format using a sailing metaphor: Wind (what propels the team), Anchors (what slows it down), and Rocks (risks ahead), all relative to an island that represents the goal. Some variants add a Sun column for things that make the team happy.

Why use a metaphor instead of direct questions?

The metaphor depersonalizes criticism. Describing 'an anchor' feels safer than naming a person or team habit directly, so issues surface earlier. It is especially effective for teams with interpersonal tension or new members.

What goes in the Rocks column?

Future risks — things that have not hurt you yet but could: a looming dependency, an unowned service, a deadline stacking up against vacation season. Rocks is what makes Sailboat forward-looking where most retro formats only look backward.

Sailboat or Speed Car: which should I use?

They ask the same questions with different pictures. Sailboat's island makes it a good fit for kickoffs and goal-setting; Speed Car's finish line suits teams racing toward a release. If your team has run one several times, switching to the other keeps the retro fresh.

Is the Sailboat template free?

Yes. Retromik is free — create a board with the Sailboat template, set your island as the focus question, and share the link. Guests join without an account.