Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 2 min read

Sailboat retro

Wind (helps), anchors (holds back), rocks (risks), island (goal): a visual reflection for teams and programmes.

1Island

The goal the team or programme is sailing towards.

e.g. one design system across apps
2Wind

What helps and pushes us forward.

e.g. developers join critiques
3Anchors

What holds us back today. Spend most of the time here.

e.g. no time for shared components
4Rocks

Risks ahead that could sink us if we ignore them.

e.g. key designer leaving
The Sailboat retro uses one picture to show the goal, what helps, what holds back and what could go wrong.

Use it when

  • You run a team or programme reflection after a quarter or a large milestone.
  • A group needs a shared goal picture before it talks about problems.
  • You want a retro that also looks ahead at risks, not only back at what happened.

How to use it

  1. Draw the boat first. Draw an island (the goal), a boat, wind behind it, anchors below and rocks ahead. Write the goal on the island and agree it with the group. Output: the picture and an agreed goal.
  2. Write alone, in silence. Everyone writes stickies for wind (what helps), anchors (what holds us back) and rocks (risks ahead). Output: stickies for each part. About 10 minutes.
  3. Place and briefly share. Each person places their stickies on the picture and reads them aloud. Group duplicates. Output: a full picture.
  4. Go deep on the anchors. Cluster the anchors, vote for the heaviest ones and discuss causes. Spend most of the session here. Output: the two or three heaviest anchors.
  5. Check the rocks. For each big risk, ask "what would we see before we hit it?". Output: risks with an early signal.
  6. Agree two actions. Pick two actions, each with an owner and a date, that cut an anchor or avoid a rock. Output: two actions. 30–45 minutes in total.

Worked example

A UX lead runs a 40-minute Sailboat retro with 8 designers at the end of a quarter on an internal operations platform. The island: "one design system used across all apps".

Part Top stickies
Island One design system used across all apps
Wind Developers join critiques · the new component library is popular
Anchors No time in team plans for shared components (6 votes) · unclear who approves new patterns (4 votes)
Rocks The design-system designer may move to another team

Actions: the lead brings shared-component time to the next priorities session (owner: lead, in two weeks). The team sets up a DACI for new patterns (owner: design-system designer, next month).

Watch out for

  • A vague island. If the goal is unclear, every sticky is about something different. Agree the island first.
  • Too much time on the wind. It feels good but changes little. Keep it short and move to the anchors.
  • Ten actions. Nobody finishes ten. Agree two and check them at the next retro.
  • Rocks as a list of fears. Turn each big risk into an early signal you can watch.

Template

Draw the picture, then use these prompts.

SAILBOAT RETRO

ISLAND (goal):   ___________________________________________

WIND     What helps us move towards the island?
ANCHORS  What holds us back today?         <- spend most time here
ROCKS    What risks are ahead? What early signal would we see?

Top anchors (after vote):  1.            2.            3.

Actions (max 2):
1. ______________________  Owner: ______  Date: ______
2. ______________________  Owner: ______  Date: ______
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close