Sailboat

When to use

End of a project, a difficult quarter, or a sprint where the team can feel a problem but nobody's said it out loud. Run it as a pre-mortem before kickoff — same quadrants, future tense. Skip it for a healthy weekly cadence; SSC is faster and Sailboat's overhead doesn't pay back unless there's something structural to surface.

How it runs

1. Draw the boat

   Boat in the middle, Island on the right (the goal), Wind above, Anchors below the boat, Rocks ahead in the water. Five minutes max — the metaphor is a tool, not the meeting.

2. Silent write, all four quadrants

   Ten minutes. Cards into all four quadrants, in any order. Don't make people start with Wind — most teams have more to say about Anchors and that's where to spend the time.

3. Read each quadrant in turn

   Wind first to set the tone, then Anchors, then Rocks, then Island. The Anchors discussion is the meeting — budget thirty minutes there and don't let the metaphor debate eat the time.

4. Vote on the Anchors

   Three dots each, on Anchors only. Pick the top one or two as commitments. Rocks become a watch-list, not action items.

5. Name an owner

   Each chosen Anchor needs a name attached and a deadline before the meeting closes. Otherwise it's just a drawing.

Why it works

The metaphor depersonalises the complaint. Saying 'the staging environment is an anchor' is easier than 'the platform team's process is slowing us down,' even though it's the same statement. The visual also makes it harder to forget — teams come back to a Sailboat board weeks later and the picture jogs the conversation in a way a list of cards doesn't.

Variations

• Speedboat — same shape, different metaphor. Use it if Sailboat feels twee for the team.
• Pre-mortem variant: run all four quadrants in future tense before a project starts. The Rocks column is the real output.
• Drop the Island if the goal is obvious; it's the column that adds the least.
• Add a Sun (what's giving the team energy) for a longer reflective retro — useful at end of quarter.

Facilitator notes

The failure mode is the metaphor becoming the meeting — people debate whether something is a Rock or an Anchor instead of fixing it. When that starts, name it, pick the closer quadrant, move on. The senior person should write last and read last on Anchors specifically; their cards anchor the room and you get a retro about their priorities.

Pitfalls

• Spending fifteen minutes drawing a beautiful boat. Five minutes, then move to the cards.
• Letting Wind be a victory lap. Two minutes — the Anchors are why you ran the meeting.
• Treating Rocks as action items. They're risks, not commitments. Watch-list them.
• Anchors that name a person ('Sarah's reviews are slow'). Take it offline; the retro is for systems.

Remote tips

On a 13-inch laptop the four-quadrant board reads as cramped — pre-build the template large, zoom to one quadrant at a time during discussion. Open the board 24 hours before the call so async writers contribute; the Anchors quadrant always benefits from overnight thinking.

Example outputs

• Anchor: the design review queue — three days median, blocking three of our six tickets.
• Anchor: the staging environment we share with QA. Every release week we're stepping on each other.
• Wind: the new on-call rota. Pages dropped from 12 to 4 last month.
• Rock: the auth migration in two sprints — nobody's owning the cutover plan yet.

FAQ

Should I use Sailboat or Start/Stop/Continue?

SSC for the weekly cadence — it's faster and pushes for clear action. Sailboat when the team can feel something structural and needs the metaphor to say it. If you're not sure, you want SSC.

How long does it take?

45-60 minutes done well. Most of that is the Anchors discussion. If you're scheduling 30, you're either rushing or you should run SSC.

Can I run it as a pre-mortem?

Yes — same quadrants, future tense. 'What will be the wind, what will become an anchor, what rocks are we sailing into.' The Rocks column is the artefact you come back to at the project's halfway point.

Related activities

Recommended use cases