Run a Sailboat Retrospective Metaphor Exercise
Facilitates a Sailboat retrospective using the metaphor of wind, anchors, rocks, and island to surface team dynamics. Built for teams that benefit from visual or metaphorical thinking.
When to use this prompt
Use this when your team has been running Start/Stop/Continue or 4Ls for several sprints and needs a fresh format to keep engagement high. The Sailboat metaphor invites visual and spatial thinking that appeals to designers and creatives more than text-heavy formats. You will need 60 minutes and a shared virtual or physical whiteboard. It is also a good choice when the team is facing a major upcoming milestone or decision because the 'island' metaphor forces articulation of what the team is actually aiming at. Do not use it on brand-new teams who have not yet formed a shared sense of direction; the metaphor requires at least some team cohesion to land.
The Prompt
You are a Scrum Master facilitating a 60-minute Sailboat retrospective. The metaphor has 4 elements: wind (what propels us forward), anchors (what slows us down), rocks (future risks), and island (our goal). Sprint name: {{sprint_name}} Team size: {{team_size}} Upcoming milestone or goal: {{upcoming_milestone}} Known team dynamics: {{team_dynamics}} Produce the retro script in this structure: 1. OPENING (5 min) - Draw the sailboat metaphor on the whiteboard: boat, wind lines, chain with anchor, rocks in the water, island in the distance. - Explain each element: WIND: Forces pushing us forward (supports, strengths, helpful practices) ANCHORS: Things slowing us down (obstacles, frustrations, drag) ROCKS: Future risks we can see ahead (predictable threats) ISLAND: Our goal, the destination - Goal of this retro: get honest about what is propelling and slowing us. 2. DEFINE THE ISLAND (10 min) - Before brainstorming on wind/anchors/rocks, the team defines the Island together. - Prompt: "What are we actually sailing toward this quarter? Describe the island in 1-2 sentences." - Facilitate until the team agrees on a shared island definition. If they disagree, surface the disagreement; a team sailing toward different islands is a root cause of other problems. 3. SILENT BRAINSTORM (10 min) - Each person adds stickies to Wind, Anchors, and Rocks. - Minimum 2 stickies per element per person. - Prompt: "What feels like wind? What feels like anchors? What rocks do you see ahead?" 4. SHARE AND CLUSTER (15 min) - Each person shares their stickies. Facilitator clusters. - Pay special attention to rocks; they are often the most suppressed element in retros because naming future problems feels pessimistic. 5. DEEP DISCUSSION (15 min) - Pick the most important cluster from each of the 4 elements (1 wind, 1 anchor, 1 rock, and check the island definition). - Discuss each briefly: what does it mean for how we sail in the next sprint? 6. COMMIT AND CLOSE (5 min) - Commitments: one to amplify the biggest wind, one to remove the biggest anchor, one to prepare for the biggest rock. - Close with each person naming their confidence level (1-5) that we will reach the island. Facilitator cheat sheet: - If the team resists naming rocks, reframe: "Rocks are not predictions; they are things we can prepare for." - If the island is unclear, stop the retro and have that conversation instead. Everything else is moot. - If the anchors are all about people, gently redirect to systems and processes.
Example Output
RETRO: Sprint 15 (Billing Team, approaching Q2 end) OPENING: Draw the sailboat. Explain each element. Our goal: get honest about what is helping and slowing us as we sail toward Q2 end. DEFINE THE ISLAND (10 min): The team discusses. Island agreed: ship bulk invite and overdue sort to GA by end of Q2 with billing admin NPS at 50 or higher. WIND CLUSTERS - Strong product-engineering communication (mentioned by 6 of 7) - Clear sprint goals (5 of 7) - New hire Mika catching up fast (4 of 7) ANCHOR CLUSTERS - Tech lead is a PR review bottleneck (5 of 7) - Definition of done keeps changing (4 of 7) - Meetings fragmenting deep work (3 of 7) ROCK CLUSTERS - Auth refactor could delay bulk invite by 1 sprint - Customer-reported timezone bug may spread to more accounts - Q2 end is a Friday, which limits rollback window DEEP DISCUSSION (15 min) - Biggest wind: product-engineering communication. How do we protect it? Keep current rituals. - Biggest anchor: PR review bottleneck. Action: add Mika and Tomas as approvers. - Biggest rock: auth refactor dependency. Action: start parallel work that does not depend on it. - Island check: still valid. Confidence is moderate. COMMIT AND CLOSE - Amplify wind: keep weekly PM-EM sync; add one to the sprint. - Remove anchor: CODEOWNERS update this week. - Prepare for rock: parallel work plan for auth dependency. - Closing confidence: average 3.5 out of 5. Team feels the island is reachable but tight.
Recommended Tools
Taskade supports visual retro boards with the sailboat metaphor pre-built or easily drawn. Monday is a strong choice when the team already uses Monday boards for sprint tracking and wants retro artifacts in the same workspace. Notion projects works when the team prefers a document-based approach with embedded whiteboard images. The visual element is the key differentiator, so prioritize tools that render the metaphor clearly.
Frequently Asked Questions
When should I use this prompt?
Use it when the team has run Start/Stop/Continue or 4Ls for several sprints and engagement is starting to drop because the format feels routine. The Sailboat metaphor refreshes the conversation and appeals to teams with strong visual or spatial thinking. It is also good before a major milestone because the 'island' element forces the team to articulate and agree on the destination. Do not use it if the team has no shared sense of direction yet; the metaphor will expose the lack of alignment but cannot fix it in a single retro.
What if the team cannot agree on the island?
Stop the retrospective and have that conversation instead. A team sailing toward different islands has deeper alignment problems that no process retro can fix. The Sailboat format surfaces this disagreement earlier than other formats because it requires explicit definition of the goal. If the team cannot articulate a shared island in 10 minutes of discussion, the real work is in a strategy conversation with leadership, not in retrospection on the last sprint. Treat the disagreement as the most valuable finding of the retro and escalate appropriately.