Method · Retrospectives

Sailboat retrospective: how to run it

Draw a boat sailing to an island: the team adds what pushes it forward (wind), what holds it back (anchors), and risks ahead (rocks) — a picture that makes a retrospective easier to talk about.

45 minutes5 stepsRetrospectives
Other methods

When it helps

Use it for a team that is tired of the same retrospective format, or when talking about problems directly is hard — the picture gives people a way to say it.

When to use something else

Skip it for a quick check-in; the drawing takes a few minutes to explain. Very literal-minded groups may prefer plain columns.

How to run it, step by step

  1. Draw the picture3 min
    • A boat, an island (the goal), wind, anchors and rocks.
  2. Name the island4 min
    • What are we sailing towards — this quarter’s goal?
  3. Add notes10 min
    • Wind: what helps us. Anchors: what slows us. Rocks: risks ahead.
  4. Discuss anchors and rocks18 min
    • Which anchor slows us most? Which rock is closest?
  5. Actions10 min
    • One anchor to cut, one rock to steer around, each with an owner.

What comes out — an example

Made up, to show the shape.

Island. Launch the mobile app by March.

Wind. A strong designer joined; customers asking for it.

Anchors. Waiting days for API changes from another team.

Rocks. App store review could delay launch.

Actions. Weekly sync with the API team (Leo); submit for review two weeks early (Mia).

Questions

What is a sailboat retrospective?

A visual retrospective using a picture of a boat: wind for what helps, anchors for what slows the team, rocks for risks and an island for the goal.

Why use a metaphor in a retrospective?

A picture can make it easier to talk about problems and keep a regular retrospective fresh.

What is the difference between anchors and rocks?

Anchors are what slow the team today; rocks are risks ahead that could cause damage if not avoided.

Can the sailboat work for a whole project, not just a sprint?

Yes. Put the project’s end goal on the island and run it at the halfway point, when there is still time to cut an anchor or steer around a rock.

Other methods

Start, stop, continueA quick retrospective in three columns: what we should start doing, stop doing, and keep doing — ending with two or three changes to try.The 4 Ls retrospectiveLook back on a piece of work through four words — what we liked, learned, lacked and longed for — to see both the good and what was missing.Mad, sad, gladA retrospective built on feelings: what made the team mad, what made it sad, and what made it glad — useful when emotions are running high and need to be heard before problems can be fixed.Lean CoffeeA meeting with no agenda until it starts: everybody writes topics, the group votes, and you talk about the most popular ones in short, timed rounds.Fishbowl discussionA few people talk in an inner circle while everyone else listens from around them; listeners can step in by taking an empty chair, so a large group can hold one real conversation.1-2-4-AllEveryone thinks alone, then in pairs, then in fours, then the whole group shares — so every person contributes and the best ideas rise in about twelve minutes.

Every method →

Try Meetful

Meetings that take their own notes

Free video meetings in the browser: every line of the transcript under the name of who said it, and the summary and action items when you hang up. Nothing to install — guests just open the link.

Try Meetful freeSee what it does