◎ Happy Backlog
GUIDE · 7 MIN READ

The sailboat retrospective: format, steps and facilitation guide

Turn a vague sprint review into a shared picture of goals, momentum, drag and future risk.

01

The four parts of a sailboat retrospective

  • Island — the goal or outcome the team is sailing toward.
  • Wind — practices, people and conditions that moved the team forward.
  • Anchors — current drag such as blockers, habits or avoidable friction.
  • Rocks — future risks that have not hit yet but need a plan.
02

When this format works best

Use the sailboat when the team is tired of Start, Stop, Continue; when future risk deserves more attention; or when people may not share the same picture of the goal. The metaphor is accessible for new and mixed teams.

Choose a focused timeline or incident review instead when one event needs detailed causal analysis. Use a simpler format when the group is completely new to retrospectives.

03

A 50-minute sailboat agenda

  1. Set the destination — 5 minutes

    Name the sprint or project goal and let the team correct it. Goal disagreement is an important finding, not a distraction.

  2. Brainstorm silently — 10 minutes

    Everyone adds one idea per note across wind, anchors and rocks. Quiet writing reduces anchoring and makes room for slower thinkers.

  3. Read and cluster — 10 minutes

    Read notes together, group similar observations and label clusters in the team’s own language.

  4. Vote and discuss — 15 minutes

    Use a limited dot-vote to find the two or three themes with the most value, then explore causes and evidence.

  5. Commit — 10 minutes

    Create one to three actions with an owner, a small next step and a review point. An ownerless action is a wish.

04

Remote facilitation tips

  • Use a shared board so everyone writes at once rather than dictating notes to a screen-sharer.
  • Keep the timer visible; remote silence often feels longer than it is.
  • Treat anchors as system conditions, not people to blame.
  • Ask what wind the team should strengthen—not only what it should fix.
  • Review the actions at the beginning of the next retrospective.
05

Useful variations

  • Speedboat: a shorter version with a tighter timebox.
  • Weather: add sunny, cloudy or stormy signals for team mood.
  • Sharks: reserve for active threats; avoid turning people into symbols.
  • Pre-seeded rocks: add one or two known risks, clearly labelled as facilitator prompts.
COMMON QUESTIONS

Frequently asked questions

How long should a sailboat retrospective take?+

About 45–60 minutes for a typical team. A 30-minute version works with strict timeboxes; larger or complex groups may need 75–90 minutes.

What is the difference between anchors and rocks?+

Anchors are slowing the team now. Rocks are upcoming risks that could cause harm later.

How many people can participate?+

Four to twelve works well. For a larger group, use breakout boats and bring the strongest themes back together.