Sailboat Retrospective: Navigate Team Improvement with This Visual Format
November 1, 2024
RetroFlow Team
The RetroFlow team builds free retrospective tools and writes practical guides for agile teams. We have helped thousands of teams run better retros.
The Sailboat retrospective (also called the Speedboat or Boat retrospective) uses a powerful sailing metaphor to help teams visualize their journey toward goals. By representing propelling forces as wind and obstacles as anchors and rocks, this format makes abstract concepts tangible and engaging.
If your team responds well to visual thinking or you want to break away from column-based formats, the Sailboat retrospective offers a refreshing and effective alternative.
What Is the Sailboat Retrospective?
The Sailboat retrospective uses a sailing journey as a metaphor for your team’s sprint or project:
| Element | Metaphor | What It Represents |
|---|---|---|
| Wind ⛵ | Sails filled with wind | What’s pushing us forward |
| Anchor ⚓ | Weight holding us back | What’s slowing us down |
| Rocks 🪨 | Dangers beneath the surface | Risks and obstacles ahead |
| Island 🏝️ | Destination | Our goal or vision |
| Sun ☀️ (optional) | Good weather | What’s going well |
The visual nature of this format helps teams see relationships between elements—how risks might sink progress, or how removing anchors could accelerate toward the goal.
Why the Sailboat Format Works
Visual Metaphor Power
Research shows visual metaphors:
- Improve comprehension and retention
- Engage different thinking styles
- Make abstract concepts concrete
- Create shared mental models
Comprehensive Coverage
Unlike simpler formats, Sailboat covers:
- Current state (wind, anchors)
- Future risks (rocks)
- Goals (island)
- Positive factors (sun/wind)
Team Engagement
The sailing metaphor:
- Feels less like a meeting, more like a creative exercise
- Encourages storytelling and narrative thinking
- Works well for remote teams with digital whiteboards
- Creates memorable retrospectives that stand out
The Sailboat Elements Explained
Wind (Sails) ⛵ — What’s Pushing Us Forward
The wind represents everything propelling your team toward success.
What belongs here:
- Effective processes and practices
- Helpful tools and technologies
- Supportive team dynamics
- External tailwinds (market conditions, executive support)
- Recent wins building momentum
Examples:
- “Strong wind: Daily standups keeping everyone aligned”
- “Wind: New CI/CD pipeline speeding up deployments”
- “Breeze: Great collaboration between dev and design”
- “Gust: Executive buy-in for the project direction”
- “Wind: Clear sprint goals everyone understood”
Prompts:
- What’s helping us move faster?
- What recent changes have been positive?
- What would we miss if it disappeared?
Anchor ⚓ — What’s Holding Us Back
The anchor represents obstacles slowing your progress or preventing movement.
What belongs here:
- Blockers and impediments
- Technical debt
- Process friction
- Resource constraints
- Communication issues
Examples:
- “Heavy anchor: Waiting 2+ days for code reviews”
- “Anchor: Legacy system requiring manual deployments”
- “Dragging anchor: Unclear requirements from stakeholders”
- “Anchor: Too many meetings fragmenting focus time”
- “Chain: Dependency on another team that’s overloaded”
Prompts:
- What’s slowing us down?
- What would speed us up if removed?
- What recurring blockers do we face?
Rocks 🪨 — Risks and Obstacles Ahead
The rocks represent future dangers—things that could sink your boat if not addressed.
What belongs here:
- Known risks not yet mitigated
- Technical risks (scalability, security)
- Team risks (burnout, turnover)
- External risks (dependencies, market changes)
- Deadline or scope risks
Examples:
- “Rock ahead: No plan for handling peak traffic”
- “Submerged rock: Key team member might leave”
- “Rocky waters: Vendor contract expires next month”
- “Reef: Technical debt in payments module”
- “Rock: Regulatory changes coming Q3”
Prompts:
- What could derail us if ignored?
- What keeps you up at night about this project?
- What haven’t we addressed that we should?
Island 🏝️ — Our Goal or Destination
The island represents your team’s goal or vision—where you’re trying to sail.
What belongs here:
- Sprint or project goals
- Team vision
- Definition of success
- Key milestones
Examples:
- “Island: Launch MVP by end of Q1”
- “Destination: Zero critical bugs in production”
- “Shore: Complete user authentication epic”
- “Paradise: Sustainable pace with quality work”
- “Goal: 99.9% uptime SLA”
Why include the island:
- Reminds team what they’re working toward
- Helps evaluate if wind/anchors affect goal progress
- Creates alignment on destination
Sun ☀️ (Optional) — What’s Going Well
Some versions add the sun as a separate positive element distinct from wind.
What belongs here:
- Team morale highlights
- Environmental positives
- Things to celebrate
- General good vibes
Examples:
- “Sunny: Great team spirit despite challenges”
- “Warm: Supportive management”
- “Bright: Exciting technology we’re building”
When to Use the Sailboat Retrospective
| Situation | Why Sailboat Works |
|---|---|
| Visual/creative teams | Engages visual thinkers |
| Remote teams with digital whiteboards | Makes remote retros more engaging |
| Need to discuss risks | Explicit “rocks” category |
| Strategic retrospectives | Goal-oriented with island destination |
| Team needs fresh format | Breaks monotony of column-based retros |
| Longer projects | Journey metaphor fits multi-sprint work |
When to Choose Other Formats
- Very short retros (< 30 min): Use Start Stop Continue
- Pure emotional processing: Use Mad Sad Glad
- Action-focused teams: Use DAKI or Starfish
- First retrospective ever: Start with simpler format
How to Run a Sailboat Retrospective
Before the Meeting
Preparation:
- Schedule 45-60 minutes
- Prepare visual board with boat, water, island, rocks
- Draw or use a digital template (Miro, Mural, RetroFlow)
- Review previous retrospective action items
- Define the “island” (current goal) if not obvious
Step-by-Step Facilitation
Step 1: Set the Stage (5 minutes)
Introduce the metaphor:
“Today we’re doing a Sailboat retrospective. Imagine our team is on a sailboat journey toward our goal—the island.
We’ll explore:
- Wind filling our sails—what’s pushing us forward
- Anchors dragging behind—what’s slowing us down
- Rocks ahead—risks we need to navigate
- The island—where we’re headed
Let’s map our voyage!”
Establish the island first: “Our island this sprint is [goal]. Does everyone agree that’s our destination?”
Step 2: Silent Brainstorming (10 minutes)
Have team members add items to each area:
- Use sticky notes (physical or digital)
- One idea per note
- Place in appropriate area on the visual
Facilitator tip: Walk around the “boat” calling out each area: “Add your wind items… now anchors… now rocks…”
💡 RetroFlow has a built-in Sailboat template—free, no signup required.
Step 3: Share and Discuss (20 minutes)
Go through each area systematically:
Recommended order:
- Island — Confirm the goal
- Wind — Start positive
- Anchors — Address current blockers
- Rocks — Discuss future risks
For each item:
- Author explains briefly
- Group discussion on impact
- Note connections (e.g., “This anchor might hit that rock”)
Discussion prompts:
- “How strong is this wind? Breeze or gust?”
- “How heavy is this anchor? Can we cut it loose?”
- “How close is this rock? When might we hit it?”
Step 4: Prioritize (5 minutes)
Use dot voting to identify:
- Most important anchors to address
- Most critical rocks to navigate
- Strongest winds to maintain
Step 5: Create Action Items (10 minutes)
Convert priorities into actions:
| Element | Item | Action |
|---|---|---|
| Anchor | Slow code reviews | Implement review rotation; max 24hr SLA |
| Rock | Key person might leave | Cross-training sessions; document knowledge |
| Wind | Great standups | Keep format; share with other teams |
Framework for actions:
- Anchors: How do we cut them loose?
- Rocks: How do we navigate around them?
- Wind: How do we maintain or increase it?
Step 6: Close (5 minutes)
- Summarize action items
- Thank the crew for the voyage
- Optional: “What did you think of this format?”
Sailboat Retrospective Template
☀️ SUN
(What's going well)
🏝️ ISLAND
┌─────────┐
│ GOAL │
│ │
└─────────┘
💨 WIND 🪨 ROCKS
(What's pushing (Risks ahead)
us forward)
\ /\ /\
\ ⛵ / \ / \
\ /\
\ / \
\ / ⚓ \
\/______\
|
| ANCHOR
(What's holding us back)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WATER
Digital Template Layout
For digital tools, create zones:
┌─────────────────────────────────────────────────────────────────────┐
│ SAILBOAT RETROSPECTIVE │
├─────────────────┬─────────────────┬─────────────────┬───────────────┤
│ ☀️ SUN │ 💨 WIND │ ⚓ ANCHOR │ 🪨 ROCKS │
│ (Optional) │ │ │ │
│ Going well │ Pushing us │ Holding us │ Risks │
│ │ forward │ back │ ahead │
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
└─────────────────┴─────────────────┴─────────────────┴───────────────┘
🏝️ ISLAND: [Your Goal Here]
Sample Items for Each Element
Wind Examples
- Automated testing catching bugs early
- Weekly knowledge sharing sessions
- Clear product roadmap visibility
- Strong team communication
- Supportive management removing blockers
Anchor Examples
- Technical debt in core modules
- Manual deployment process
- Waiting for external team approvals
- Unclear acceptance criteria
- Too many meetings
Rocks Examples
- Upcoming security audit we’re unprepared for
- Scalability concerns as users grow
- Team member on extended leave next month
- Contract renewal negotiations
- Competitor launching similar feature
Island Examples
- Ship feature X by sprint end
- Achieve 95% test coverage
- Zero P1 bugs in production
- Complete migration to new platform
- Sustainable team velocity
For discussion prompts that pair well with this format, see our retrospective questions guide.
Tips for Facilitating Sailboat
Make It Visual
- Draw it out — Even rough sketches help
- Use colors — Green for wind, red for rocks
- Show movement — Arrows indicating direction
- Add personality — Name the boat, add waves
Extend the Metaphor
During discussion, use sailing language:
- “That’s a strong headwind—how do we tack around it?”
- “Can we jettison some anchor weight quickly?”
- “Do we need to chart a different course around these rocks?”
- “What would give us more wind in our sails?”
Connect Elements
Help team see relationships:
- “If we remove this anchor, would we sail faster toward the island?”
- “This rock and this anchor seem related—same root cause?”
- “Is this wind sustainable, or just a temporary gust?”
For Remote Teams
- Use digital whiteboard (Miro, Mural, Figma)
- Pre-build the visual template
- Enable simultaneous editing
- Use cursor presence to see where teammates are
- Screen share for those on phones
Variations on Sailboat
Speedboat
Emphasizes speed—“How do we go faster?” Less focus on risks, more on acceleration.
Pirate Ship
Adds treasure (goals) and sea monsters (risks). More playful for teams that enjoy theming.
Rocket Ship
For ambitious teams: fuel (wind), gravity (anchors), asteroids (rocks), moon/mars (goals).
See our Rocket Ship Retrospective guide.
Extended Sailboat
Add more elements:
- Crew — Who’s on board and their roles
- Compass — Our guiding principles
- Lighthouse — What guides us safely
- Weather forecast — Expected conditions ahead
Related Visual Formats
If your team enjoys the Sailboat metaphor, try:
- Hot Air Balloon — Rising vs. weighing down
- Speed Car — Engine, parachute, bridge
- Mountain Climber — Summit, gear, obstacles
- Rocket Ship — Fuel, gravity, stars
For non-visual formats:
- Start Stop Continue — Simple columns
- 4Ls — Liked, Learned, Lacked, Longed For
See all options in our sprint retrospective formats guide.
Frequently Asked Questions
What is a Sailboat retrospective?
A Sailboat retrospective uses a sailing metaphor to visualize team dynamics. Wind represents what pushes the team forward, anchors represent what holds them back, rocks represent risks ahead, and the island represents the team’s goal.
How many people can do a Sailboat retrospective?
The Sailboat format works well for teams of 3-12 people. For larger groups, consider breaking into smaller teams that each create their own sailboat, then share findings with the full group.
Is the Sailboat the same as the Speedboat retrospective?
They are very similar. The Speedboat retrospective typically uses an engine (what drives us) and anchors (what slows us) without the rocks and island elements. The Sailboat version adds more dimensions, making it slightly richer for discussion.
What tools support the Sailboat retrospective format?
Most dedicated retrospective tools including RetroFlow offer a Sailboat template. You can also run it on a whiteboard (physical or virtual) by drawing a simple boat with labeled areas for wind, anchors, rocks, and island.
Try Sailboat in RetroFlow
Looking for a quick way to run this format? RetroFlow has a ready-made Sailboat template with anonymous input and built-in voting. It’s free and takes about 30 seconds to set up.
Summary
The Sailboat retrospective uses a powerful visual metaphor:
- Wind ⛵ — What’s pushing us forward
- Anchor ⚓ — What’s holding us back
- Rocks 🪨 — Risks and obstacles ahead
- Island 🏝️ — Our goal or destination
It’s ideal for visual teams, strategic discussions, and breaking the monotony of traditional formats. Run it in 45-60 minutes with a focus on connecting elements and creating actionable outcomes.
Related Resources
- Sprint Retrospective Formats Guide - 30+ formats
- Hot Air Balloon Retrospective - Similar visual format
- Remote Retrospective Games - Engaging distributed teams
- Virtual Whiteboard Tools - Digital collaboration