kringo

Retrospective

Sailboat

3 steps, 20 min · Method after Luke Hohmann’s Speedboat (2006)

Some teams feel slow and cannot say why, and a direct question gets a shrug. Sailboat asks it sideways: if we were a boat, what fills our sails, what drags behind us, and which one thing do we change? The steps and the clock are on a screen everyone sees, in the room or shared in a video call, which leaves you free to hear what people say through the picture.

Start this sessionSign in to host. Participants need no account, only a first name.

The steps

  1. 1WindWhat pushes us forward?6 min
  2. 2AnchorsWhat holds us back?7 min
  3. 3One thing we changeWhat one thing do we change?7 min

These are the method’s minutes. During the session you add or take off a minute when the group needs it.

Roles

Facilitator
Leads the session, gives the word round the circle and decides when to move on.
Note-taker
Catches action ideas as you talk, one line each.

What the group sees

The shared screen: the step, its question, the roles and the clock, with a dot for everyone who joined.
Each phone: the same step, a note, and “I’m ready”.

When Sailboat fits

Pick it when the team feels slow and nobody has said why. The picture gives people a safe way to name what holds the team back: an anchor is a thing, not a colleague.

It also works for a group that does not know each other’s work well, such as two teams after a shared project, because everyone understands a boat without explanation. If the team wants a quick look at an ordinary sprint, Start Stop Continue gets there faster.

Leading it, step by step

Wind. The session starts with what pushes the team forward, on purpose. People who have first heard what works are more willing to talk about what does not.

Anchors. Ask for something you could point at: a meeting, a handover, a system that is slow. Then sort aloud. Some anchors the team can lift itself, and some are weather, outside its reach. Give the time to the first kind.

One thing we change. The step that makes the picture useful. The team chooses one anchor that is both heavy and liftable, and says what it will do about it. One, because a team that leaves with five changes makes none.

If you are in a room with a whiteboard, the Scribe can draw the boat and write along. Online, the steps on the screen are enough.

Three things to watch

  • The picture takes over. Pirates and sea monsters are a sign the group is avoiding the subject. Bring it back with one question: what is that in our week?
  • Only weather. If every anchor is somebody else’s fault, ask which one this team could move by a metre.
  • No single choice. When the group cannot choose, let everyone name their one anchor in the circle and take the one named most.

Where it comes from

Luke Hohmann published Speedboat in 2006 as a way to hear from customers what holds a product back: they wrote anchors on a drawing of a boat. Agile teams turned the exercise on themselves and added the wind. Other versions add rocks for risks and an island for the goal; ours keeps three steps so the session ends in one change.

Other methods