Sailboat Retrospective
Use wind, anchors, rocks, and the island to talk about propulsion, drag, risks, and goals.
Wind
Forces that sped you up: people, clarity, automation, or momentum.
Anchor
What held you back even though you could often influence it?
Rocks
Risks ahead—things that could shipwreck the goal if ignored.
Island
The shared destination: what success looks like for the team.
This board is for demo purposes only. Your responses are not saved. Close or refresh the page to clear all cards. Do not add any sensitive information.
What is the Sailboat Retrospective?
The Sailboat Retrospective is a metaphor-driven retrospective format where the team imagines their project or sprint as a sailboat journey. Originally introduced by Luke Hohmann in his book "Innovation Games" and later adapted by agile practitioners worldwide, it has become one of the most widely recognized visual retrospective formats. The nautical metaphor makes abstract concepts tangible and is engaging enough to keep even retrospective-fatigued teams interested.
The four elements of the sailboat represent different forces acting on the team. "Wind" represents the tailwinds—everything that propelled the team forward, from good tooling to clear requirements to strong collaboration. "Anchor" represents drag—processes, dependencies, or habits that slowed progress. "Rocks" represent risks—hidden dangers below the waterline that could damage or sink the project. "Island" represents the destination—the shared vision of success that guides decision-making.
The beauty of this format lies in how the metaphor naturally separates current state from future risk. Most retro formats focus on what happened; the sailboat adds a crucial forward-looking element through the rocks and island columns. This makes it especially valuable for teams navigating uncertain territory.
When to use the Sailboat Retrospective
The Sailboat Retrospective shines at the beginning of a new project phase, after a major release, or at a mid-project checkpoint. Its forward-looking elements make it ideal when the team needs to balance reflection on past performance with strategic thinking about upcoming challenges. It works particularly well for teams of five to twelve people and fits naturally into a 60-minute session.
Use this format when your team is stuck in a reactive pattern—always fighting fires without stepping back to see the bigger picture. The island column forces strategic alignment conversation, while the rocks column shifts the team from reactive problem-solving to proactive risk management. It is also excellent for newly formed teams because the metaphor provides shared vocabulary that accelerates team bonding.
Avoid this format if your team needs to focus purely on emotional processing or if the group is too large for meaningful metaphorical discussion. The format loses its power when the metaphor becomes forced—if your team does not resonate with nautical imagery, consider the Hot Air Balloon or Mountain Climber alternatives, which offer similar structure with different visual language.
How to facilitate the Sailboat Retrospective
Start by drawing a simple sailboat on the whiteboard or displaying one on your digital board. Label each element clearly: wind (sails), anchor (below the boat), rocks (underwater ahead), and island (on the horizon). Spend two minutes walking through the metaphor so everyone shares the same mental model. A quick drawing exercise where each person sketches their own boat in 30 seconds can make the metaphor more personal and playful.
Give the team seven minutes to write sticky notes for all four quadrants. Process the columns in this order: island first to establish shared direction, then wind to celebrate momentum, then anchors to identify drag, and finally rocks to surface risks. Starting with the island is crucial because it frames all subsequent discussion—anchors and rocks only matter relative to where you are trying to go.
For each theme that emerges in the anchor and rocks columns, facilitate a brief root cause discussion. Then create action items specifically framed as "how do we strengthen the wind" or "how do we cut this anchor." Keeping the metaphor alive during action planning makes commitments more memorable and easier to reference in daily standups.
Tips for getting the most out of the Sailboat Retrospective
The most common mistake is treating the island column as a formality. If everyone writes "ship the feature on time," you have missed the opportunity. Push for richer definitions of success: "Ship with zero P1 bugs and a runbook the on-call team actually uses." Specific destinations create more meaningful wind and anchor discussions because the team can evaluate forces relative to a well-defined goal.
Another pitfall is conflating anchors with rocks. Anchors are current realities that are slowing the team right now—they are known and felt. Rocks are future risks that have not yet materialized. Help the team distinguish by asking: "Is this hurting us today, or could it hurt us tomorrow?" This distinction is strategically important because anchors need immediate action while rocks need monitoring or mitigation plans.
Keep the visual metaphor alive after the retro. Some teams display the sailboat in their team area and update it throughout the sprint. When a new risk emerges, they add a rock. When momentum builds, they add wind. This turns a one-time exercise into a living strategic tool that reinforces continuous improvement culture.
Variations and adaptations
For remote teams, use a collaborative whiteboard with a pre-drawn sailboat template. Color-code sticky notes by quadrant for visual clarity on busy boards. Remote sailboat retros benefit from a "tour of the boat" approach where the facilitator zooms into each section, making the virtual board feel more spatial and less like a spreadsheet.
For asynchronous teams, share the boat template with written instructions for each quadrant and give the team 24 to 48 hours to populate it. During the synchronous wrap-up, focus on the island alignment conversation first—if the team is not aligned on the destination, everything else is premature. Async sailboat retros often reveal destination misalignment that would not surface in faster formats.
A popular variation adds a fifth element: "Sun" or "Weather" to represent the external environment—market conditions, organizational changes, or competitive pressure. This is useful for product teams that need to account for forces beyond their control. Another adaptation for quarterly planning sessions extends the format to include a "fleet" view where multiple teams discuss how their boats relate to each other—shared winds, common rocks, and convoy-level coordination needs.
Run Retrospectives in CodeKudu
CodeKudu includes dozens of retrospective board templates, anonymous feedback, AI summaries, and action items that sync to GitHub Issues, Jira, and Linear.
