A sprint can leave the team with wins, blockers, worries, and a fuzzy sense of where the work is going. The Sailboat retrospective gives each one a place: wind for momentum, anchors for drag, rocks for risk, and an island for the outcome everyone wants.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
What helped the team move faster, work together, or make progress with confidence?
What slows the team or drains its effort?
Which risks, dependencies, or unknowns could hurt the next stage of work?
Which concrete outcome is the team sailing toward, and what will show that it has arrived?
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint, project, or time period under review. Agree on the island goal before anyone adds a card.
Give everyone seven quiet minutes to add specific observations across all four columns. Keep each card focused on one specific idea.
Move through the columns and let each author explain their cards briefly. Save every solution idea for the later discussion.
Combine any themes that describe the same underlying force. Give each person a few votes for the anchors or rocks that deserve the team's attention.
Discuss the strongest momentum, drag, and risk themes, then connect each one to the shared destination.
Choose one owned action before the next review. It should strengthen the wind, lift an anchor, or reduce a rock.
Give the team a timer and quiet time to write anonymous cards. Reveal every card together so typing speed stays out of the opening discussion.
Make the release outcome the island. Use rocks for launch, compliance, operational, and adoption risks.
Use wind and anchors for collaboration. Keep the rocks column focused on burnout, concentrated knowledge, or a staffing risk that could hurt the team.
Before the retro
Wind is momentum. Anchors are current drag, rocks are the risks waiting ahead, and the island is the shared goal or desired outcome.
Plan for 35 to 45 minutes. That timing suits three to twelve people, though collecting cards before the meeting can make a shorter session work.
Anchors slow the team today. Rocks are risks or unknowns that could cause trouble next, and keeping that time difference clear stops the two conversations from blending together.
Use it when the team needs to connect recent experience to a future destination, especially during releases, roadmap changes, or work shaped by dependencies and delivery risk.
Open the four-column template and invite the team. Collect cards, vote, and assign one navigation change before the meeting ends.
