The Sailboat retrospective turns a sprint or project into a shared map. Teammates name what creates momentum, what causes drag, what could hurt progress next, and what success should look like.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
What helped us move faster, collaborate better, or make confident progress?
What repeatedly slowed the team or consumed more effort than it should?
Which risks, dependencies, or unknowns could damage the next stage of work?
What concrete outcome are we navigating toward, and how will we recognize it?
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint, project, or time period being reviewed and agree on the island goal before collecting cards.
Give everyone quiet time to add specific observations to all four columns. Ask for one idea per card.
Move through each column, letting authors explain cards briefly without starting the solution discussion yet.
Combine duplicate themes and give each person a small number of votes for the anchors or rocks that matter most.
Discuss the top momentum, drag, and risk themes. Connect each theme back to the shared destination.
Create one owned action that strengthens the wind, lifts an anchor, or reduces a rock before the next review.
Use silent writing, anonymous cards, and a timer. Reveal all cards together so faster typists do not frame the room first.
Set the island as the release outcome and use rocks for launch, compliance, operational, and adoption risks.
Treat wind and anchors as collaboration forces while keeping rocks focused on burnout, knowledge concentration, or staffing risk.
Before the retro
Wind represents forces helping progress, anchors represent current drag, rocks represent future risks, and the island represents the shared goal or desired outcome.
Plan 35–45 minutes for a team of three to twelve. A shorter session can work when cards are collected before the meeting.
Anchors are problems already slowing the team. Rocks are risks or unknowns that could cause trouble next. Keeping that time distinction prevents duplicate discussion.
Use it when the team needs to connect recent experience with a future destination, especially around releases, roadmap changes, dependencies, and delivery risk.
Open the template with all four columns ready, invite the team, collect cards, vote, and assign the navigation change before the meeting ends.
