Goal

What are we working towards?

Launch our new product feature by end of Q2
Reduce customer support response time to under 4 hours
Achieve 98% test coverage across all core modules
Wind

What is pushing us forward?

Our daily standups are efficient and informative
Great collaboration between development and design teams
New automation tools are saving us lots of time
Anchor

What is holding us back?

Outdated documentation is causing confusion
Too many meetings interrupting focus time
Slow approval process for new tools
Rocks

What risks do we face?

Potential system downtime during migration
Key team member leaving soon
Competing project might affect our deadline
Sun

What is making us feel good?

Recent successful product launch boosted confidence
Great feedback from customers on latest features
Team lunch last week was really fun

What is the Sailboat Retrospective?

The Sailboat Retrospective uses a powerful maritime metaphor to help teams reflect on their progress and challenges. In this retrospective, the team's journey is represented by a sailboat navigating through waters. The wind represents helping forces, while anchors symbolize obstacles. Rocks represent risks ahead, and the sun represents positive elements keeping team morale high. The destination represents the team's goals. This visual approach makes it particularly effective for teams who prefer metaphorical thinking or want to break away from traditional retrospective formats. It helps teams identify both opportunities and challenges while maintaining a clear focus on their objectives.

Sailboat Retrospective Format

Goal

What are we working towards?

The goal represents the team's destination. Encourage participants to think about both short-term and long-term objectives. Help the team align their vision and ensure everyone understands where they're heading.

Wind

What is pushing us forward?

Wind represents positive forces helping the team move forward. Guide the discussion to identify enabling factors, resources, and practices that are working well. This helps reinforce successful behaviors and processes.

Anchor

What is holding us back?

Anchors represent impediments slowing the team down. Encourage honest discussion about obstacles while maintaining a constructive tone. Focus on identifying actionable solutions rather than just listing problems.

Rocks

What risks do we face?

Rocks represent potential future risks and challenges. Help the team think proactively about what could go wrong and develop mitigation strategies. Focus on both technical and non-technical risks.

Sun

What is making us feel good?

The sun represents positive elements boosting team morale. Encourage sharing of achievements, recognition, and positive experiences. This helps build team spirit and identifies what should be maintained or expanded.

When to use this retrospective

  • When you want to make retrospectives more engaging and visual for teams that might be experiencing retrospective fatigue
  • During project milestones or quarterly reviews to assess progress and plan ahead
  • When teams need to balance discussing both opportunities and challenges in a structured way
  • For teams that are new to retrospectives and need a clear, metaphorical framework to guide their discussions

Suggested icebreaker questions

  • If your current project was a type of boat, what would it be and why?
  • What's your favorite memory of being near water (ocean, lake, river)?

Ideas and tips for your retrospective meeting

  • Start by explaining the metaphor clearly and ensure everyone understands what each element represents
  • Use the visual nature of the exercise to create a collaborative diagram during the session
  • Keep a balance between discussing problems (anchors/rocks) and opportunities (wind/sun)
  • Encourage quiet team members to contribute by going around the room for each element
  • End the session by prioritizing actions based on impact and feasibility
  • Consider using breakout rooms for larger teams to ensure everyone gets a chance to contribute

New to retrospectives? Read our guide on how to run a retrospective →