sailboat agile

Run The SailBoat Agile Exercise or Sailboat Retrospective

This exercise can be found in the book  Getting Value out of Agile Retrospectives . A book that was written by me and  Ben Linders  with a foreword by  Esther Derby .

Sailboat Exercise

What you can expect to get out of this technique.

From my experience, this technique is quite appreciated by teams because of its simplicity.

This exercise helps teams to define a vision of where they want to go; it helps them to identify risks during their path and allows them to identify what slows them down and what helps them to achieve their objectives.

When you would use this technique

I believe this method is quite simple and does not require any special occasion. Although, it might be interesting for situations when a retrospective is conducted with more than one team at the same time.

I had a situation, not long time ago that two teams worked together and because of their level of dependency on each other, they decided to conduct a common retrospective because of some ongoing issues.

Using the SailBoat exercise can be extremely interesting because we simply put the name of both teams on the SailBoat and we remind everyone that we are on the same SailBoat navigating in the same direction.

This technique reveals all the good things and less positive things performed by a team.

How to do it

This retrospective is quite simple. First, we draw a SailBoat, rocks, clouds, and a couple of islands like it is shown in the picture on a flip chart.

The islands represent the teams´ goals/vision. They work every day to achieve these islands. The rocks represent the risks they might encounter in their vision.

The anchor on the SailBoat is everything that is slowing them down on their journey. The clouds and the wind represent everything that is helping them to reach their goal.

Having the picture on the wall, write what the team vision is or what our goals are as a team. After that, start a brainstorming session with the team allowing them to dump their ideas within different areas.

Give them ten minutes to write their ideas. Afterward, give 5 minutes to each person to read out loud their ideas.

At this point discuss together with the team how can they continue to practice what was written on the "clouds" area. These are good ideas that help the team, and they need to continue with these ideas.

Then spend some time discussing how can the team mitigate the risks that were identified. Finally, together with the team chose the most important issue that is slowing the team down.

If you do not find an agreement within the team about the most important topic that should be tackled, you can use the vote dots.

In the end, you can define what steps can be done to fix the problem, and you can close the retrospective.

Like many other exercises, this exercise does not require a collocation of a team. You can use, for example, tools like Lino, to apply the exercise to non-collocated teams. This tool allows us to do everything that we need to run this exercise.

What do you think? Your feedback is always extremely important for me, so please leave me your comments.

An Agile Retrospective is an event that ́s held at the end of each iteration in Agile Development and it serves for the team to reflect on how to become more effective, so they can tune and adjusts its behavior accordingly.

I believe the SailBoat exercise is quite a simple Agile Retrospective Exercise and does not require any special occasion.

If you are interested in getting some extra Agile Retrospectives exercises, I created a blog post with dozens of  Agile Retrospectives Ideas , check them and see if you find something interesting.

"Starfish exercise" or "Starfish Retrospective"

The world cafe - agile retrospective technique, similar blog posts.

Find Out How To Use Kudo Cards in Agile Retrospectives

The Instant Retrospective

Sailboat Retrospective

You know the term ‘smooth sailing’? Imagine you could apply it to all of your current projects and future sprints. Using the Sailboat Retrospective technique can help you achieve team cohesiveness using a fun, visual exercise that gets all of your team members on the same page — or should we say— boat.

What exactly is a Sailboat Retrospective?

The Sailboat technique for retrospectives is a fun, interactive, and low-key way for your team to reflect on a project. It helps team members to identify what went right, what went wrong, and what improvements and changes can be made in the future. Usually the retrospective happens immediately after the completion of a project or sprint.

This technique uses the metaphor of a sailboat heading toward shore to help teams visualize their ship (team) reaching its ultimate destination (or ultimate goals).

Let’s look at a quick breakdown of the pieces involved:

Anatomy of the Sailboat Retrospective

In a Sailboat exercise, there are traditionally five main components:

• The sailboat: The team itself (or some teams prefer to make this the project)
• The island or shore: The ultimate goal or vision for the team (where it’s headed)
• The wind (or the sails): Things that are helping the team glide along (team strengths, competitive advantages of your product, good communication, etc.)
• The anchors: things that are slowing the team or project down or delaying progress (silos, areas of weakness, etc.)
• The rocks: the risks or potential pitfalls of a project (areas of tension, bottlenecks, competition, etc.)

Some Sailboat Retrospectives incorporate other aspects that fit into their vision such as the sun, which represents things that make the team feel happy or satisfied; or, choppy waves to represent something the team feels anxious about.

Some teams even scale their sails for bigger vs. smaller problems. If you have quite a few people involved in your retrospective or you have a lot of issues and need a way to prioritize, this is an option.

Feel free to get creative and add any aspects you feel would be beneficial to your retrospective. (This can be easily done via our Sailboat Retrospective template by adding additional columns. See below.)

Why is the Sailboat Retrospective technique so effective?

The effectiveness of the Sailboat Exercise lies in its ability to use relatable metaphors to help team members easily identify important strengths and weaknesses. Because it is more of a non-pressure approach, it can help team members feel relaxed and more open to communicate without overthinking things.

This exercise is a fun way to get your team out of their day-to-day and think about the ‘big-picture’ to continually improve processes. It can also be a nice way of mixing up your retrospectives to keep them fresh and engaging.

And just because it’s fun doesn’t mean it’s not effective! The average Sailboat Retrospective normally helps to identify around 3-5 action items . That’s 3-5 new ways that your team can enhance their performance!

How to run one with your team

Ready to try your own Sailboat method retrospective?

Note: This exercise should take around 60 to 90 minutes to complete.

1. First, gather your key stakeholders

Usually, a retrospective includes the Scrum Master, Product Owner and members of the Scrum team. If there are other key stakeholders for your specific project invite them to the retrospective as well. This specific type of exercise really benefits from having different opinions and perspectives.

If your team is distributed or remote (as many are these days) you can still perform the Sailboat Exercise. Consider using a great online tool designed specifically to help distributed teams facilitate retrospectives.

2. Set some ground rules

It’s important to set the tone for how you envision your retrospective going. There are a few things that should never be included in any retrospective, and the Sailboat method is no exception. Keep your retrospective free of:

And make sure the focus is on:

• Having a growth mindset
• Being optimistic
• Being open-minded and open to constructive criticisms
• Being a psychologically-safe environment

3. Sketch your Visual

The rough sketch below is a pretty standard depiction for this type of retrospective. If you don’t want to draw your own, a simple Google search of sample Sailboat Retrospective images can help you find more examples.

Your visual should include all of the elements you’ll be discussing in order to help facilitate the exercise.

4. Set up your Template

Next, you’ll want to set up the template you’ll be using to capture your team’s thoughts. You can use a white board and post-its for this, but we’d suggest using an easy-to-build online template ( like this one ) to keep things organized.

Add all of the categories you will be discussing to your template. Then, take a few minutes to explain in detail what each category represents.

5. Brainstorming and/or discussion

Once your categories are all laid out on your template, you can either ask your team to quietly brainstorm for each one, or you can hold a group discussion. Really, this depends on the communication style of your team.

If you feel it might be better to have team members submit their feedback anonymously, they can write out their notations on post-its and you can gather them before discussion. Once you have everyone’s thoughts and additions, add them to your template.

This is the final phase of the retrospective. At this point, you and your team should identify what the biggest successes of your project were and what attributes you’d like to carry forward.

Discuss your anchors (obstacles) and brainstorm ways to overcome them. Also discuss ways to mitigate your potential risks (rocks) and how close or far you are from reaching your ultimate goals.

Once everyone is on the same page, conclude your retrospective and move forward with a plan and improved understanding of team performance!

That’s all there is to it! We hope your team enjoys this retrospective and gains some valuable insights along the way.

Happy sailing!

Filter by Keywords

Project Management

Sailboat retrospective: for agile software development teams.

Sarah Burner

ClickUp Contributor

February 1, 2024

So much of the agile software development process is iterative. Sometimes it feels like a project never ends! But, sure enough, your team successfully crosses the finish line. Instead of simply moving on to the next project, the agile methodology requires retrospective meetings that analyze what went well and what you should change for next time. It’s all in service of fine-tuning your workflows and processes to boost team cohesion and work quality. 

Like any process on an agile team , retrospectives need structure. If you haven’t tried it yet, the sailboat retrospective technique is a true game-changer. This technique not only makes retrospectives more engaging but also provides a clear visual metaphor to help teams navigate the complexities of a project. 🛥️

Whether you’re a Scrum master , product owner, or member of an agile team, sailboat retrospectives will help you identify potential risks, celebrate what went well with the last sprint, and set goals for the next sprint. In this guide, we’ll explain what a sailboat retrospective is and offer tips for practicing retrospective techniques in ClickUp.

• What Is a Sailboat Retrospective?

The wind (or the sails)

The sun , running a sailboat retrospective, the concept of sailboat retrospective within a scrum framework, why project managers choose the sailboat retrospective, educate your team, create a comfortable environment, embrace visual aids, manage time carefully, focus on actionable outcomes and next steps.

What Is a Sailboat Retrospective ?

Agile software development teams use sailboat retrospectives to reflect on past sprints or project phases. Retrospectives are the final agile ceremony project managers oversee to improve the quality of future projects. The goal of any retrospective is continuous improvement. After all, it’s easier to do better next time if you know what to avoid. 

While you’re free to use any retrospective technique you like, the sailboat method is different because it uses the metaphor of a sailboat on a journey. It’s less dry than other retrospective techniques and gives your Scrum team a fun way to visualize progress, challenges, and future direction. 

In a sailboat retro, you imagine the project as a sailboat moving toward a common goal. During the session, team members use sticky notes to write down their thoughts on each component of the sailboat, which you place on a whiteboard and review together. The process encourages brainstorming and open discussion, culminating in a list of helpful action items for future sprints. 

Sailboat retros might be too abstract for some teams, but many project managers like how they act as a fun icebreaker that also aligns the team on areas of improvement. It’s much more fun than staring at a wall of bland text for two hours, isn’t it?

Components of a Sailboat Retrospective

A sailboat retro is a helpful agile project management tool. Since it uses metaphor, it’s easier for teams to think critically about future sprints. During a session, your team will document their thoughts on each component of the sailboat, which you later use to map out future projects.

The goal of a sailboat retro represents the destination. Think of this as the “X” on a pirate map. Some teams refer to this as the “island” your sailboat wants to reach. The goal could be just about anything, from the end of a sprint to the completion of a major project phase. What matters is that you choose a significant milestone for the team to work toward. 🌻

The wind or sails symbolize the positive forces that move your sailboat closer to its destination. This includes all of the successes, strengths, and good conditions that had a positive impact on the last sprint or project phase. It might include things like specialized certifications, a boost in department funding, or being able to outsource some of your team’s workload. 

In a sailboat retrospective, the anchor represents challenges or obstacles slowing the team’s progress. Anchors are anything that hinders your progress, like communication issues or resource limitations. 

Rocks are potential risks or foreseeable challenges in the sailboat’s path. While you look at the anchor in the past tense, rocks look forward and require the team to proactively plan for known issues. The goal is to minimize their impact on the next sprint. Rocks could include regulatory changes or continued resource limitations.

Finally, the sun represents your team’s objectives beyond the primary goal. This element adds a layer of motivation and inspiration, focusing on the team’s long-term objectives and vision. The focus here is to identify good things that came out of the project, like an improved product or positive customer feedback. It’s important to end on this note so your team can visualize the value of their hard work.

Ready to run a sailboat retro with your entire team? The good news is you don’t have to create the visuals on your own. We might be the world’s favorite project management software, but ClickUp also includes hundreds of free templates for anything you need—including agile retrospectives. 

Simply pull up the ClickUp Sailboat template during your team meeting and you’re off to the races. Start by inviting all employees to the retrospective meeting and run through this process together: 

• Set goals: Decide on a specific destination or milestone. If you’re already set up in ClickUp, this will likely come from your ClickUp Goals
• Collect supplies: Every boat needs supplies before a long voyage, right? During this stage, you chat about the necessary resources and supplies to support your goal. That might include personnel, software licenses, and other necessary equipment
• Check the weather: Can you expect smooth seas or stormy, treacherous waters? This stage of the sailboat retro looks at potential issues in the pipeline. The ClickUp Sailboat template integrates with your ClickUp Calendar view to give you a quick snapshot of your journey so you can plan accordingly
• Build a roadmap: Goals and calendar in hand, it’s time to build a roadmap with your team. During this step, you’ll decide on timelines and visualize them with tools like the ClickUp Gantt Chart view
• Prep your boat: Any seaworthy vessel needs a thorough inspection before setting sail. In this stage of the sailboat retro, you’ll map out tasks, assignees, and any other essential elements to support your next sprint
• Set sail: Finally, your team is ready for their next big voyage. At this stage, project managers continue refining their projects, tasks, docs, and workflows for better project outcomes 

Ultimately, this fun metaphor will help you get organized, plan for future problems, and agree on a shared vision. Since this sailboat retrospective template helps bring all of your work together into one dynamic platform, implementing your sailboat retro is as easy as a few clicks. 🚣‍♀️

The sailboat retro sounds like way more fun than a typical sprint retrospective brainstorming session, but how does it fit within a Scrum framework? 

It might be more creative than other retrospectives, but the sailboat approach aligns well with Scrum principles because it’s:

• Adaptable: Sailboat retros encourage teams to reflect on past performance (wind and anchors) and anticipate future challenges (rocks), which is essential for the always-adapting nature of Scrum project management
• Collaborative: This retrospective technique promotes open communication because all team members get a say on what hindered the team and what went well. That’s a perfect fit for Scrum’s emphasis on strong teamwork
• Goal-oriented: The focus on a common goal (or the destination, if we’re following the sailboat metaphor) fits with Scrum’s focus on delivering value while meeting sprint goals

Fortunately, the sailboat retro process isn’t much different if you follow the Scrum framework:

• Conduct a sprint review: Review the outcomes and deliverables of your most recent sprint with the team
• Conduct the sailboat retrospective: Visualize the entire project with the ClickUp Sailboat template . Ask the team to write their thoughts on sticky notes for the wind, the anchor, the rocks, and the sun. Review everything together to summarize key insights and lessons learned
• Determine action items : Mobilize your insights by deciding on action items at the end of the meeting. Plug action items into ClickUp with assignees, notes, and due dates to keep the next sprint on track

Sailboat Retrospective vs. Other Retrospectives

Sailboat retrospectives are a fun, metaphorical way to do project post-mortems, but they certainly aren’t the only way to review project progress. It’s one of many potential sprint retrospective formats , each with a different approach:

• Sailboat vs. Starfish: A starfish retrospective categorizes feedback into five buckets: Start, Stop, Continue, More of, and Less of. This is a broad framework for categorizing feedback from your team, customers, and other stakeholders, which can be helpful. However, sailboat is more of a visual and metaphorical approach, making it easier for your team to engage in the retrospective
• Sailboat vs. the 4 L’s: The 4 L’s stand for Liked, Learned, Lacked, and Longed For. Like a sailboat, it focuses on individual feelings and experiences. However, a sailboat is more useful because it also looks at external factors (wind and anchor) that affect the team, giving you a more holistic view of the project environment
• Sailboat vs. Mad Sad Glad: Mad Sad Glad is a more emotion-focused retrospective that lists team members’ feelings about a project. The sailboat retrospective does account for emotions, but it primarily focuses on factors that affect the project’s progress and future risks. That’s more business-focused than, say, someone feeling sad that the project is over

The right retrospective approach depends on your goals and corporate culture. Even so, more project managers are gravitating toward sailboat retrospectives because they’re:

• Highly visual: The sailboat metaphor is easy to understand, promoting better engagement and participation
• Comprehensive: We like the sailboat retrospective because, unlike other retrospective techniques, it offers a more holistic view of projects and provides a more well-rounded analysis
• Feedback-focused: Most employees find the metaphorical, fun approach less intimidating than other retrospective methodologies. In practice, this makes people more likely to share challenges and risks they might not have shared otherwise
• Flexible: You don’t have to be on a large enterprise software development team to do a sailboat retrospective. This technique adapts to various team sizes and departments, making it a helpful tool for any agile team

Sailboat Retrospectives in Practice

At this point, we know what a sailboat retrospective is and how to run one for your team. But how do you actually implement what you learned in the sailboat retrospective? Follow these pro tips to translate your retrospective insights into tangible business results. 

Your team might say, “Huh?” if you walk into the room with a big chart with a sailboat on it. Brief your team on the sailboat retrospective method before the meeting. Always explain the metaphor at the start of the session, even if you’ve done sailboat retrospectives before. Not everyone will admit that they don’t know what’s going on, so a little refresher does wonders for understanding and participation. 

You want to encourage honest, helpful feedback, but people won’t share their honest feelings if they feel uncomfortable. Foster a safe and open atmosphere where team members feel comfortable sharing their thoughts. If you still struggle to gather candid feedback, give your team the option to share anonymous feedback instead. 

Sailboat retrospectives are highly visual, so you need some kind of visual aid going into this meeting. Whether it’s a physical whiteboard or a digital Mind Map in ClickUp , have a clear depiction of the sailboat, wind, anchors, rocks, and sun.

Retrospectives can quickly run off the rails if you don’t watch the clock. Honor everyone’s time by creating a loose agenda for the meeting that breaks down what you’ll discuss and when. If your team has a habit of going over time, assign an official timekeeper and meeting facilitator to keep everyone on task. ⏱️

Other retrospectives, like Mad Sad Glad, focus too much on feelings. Emotions are a helpful type of feedback, but they aren’t very actionable. The sailboat retrospective is useful because it emphasizes what went well while also addressing what you could do differently next time. Instead of getting too hung up on subjective assessments, focus on desired outcomes and the steps required to achieve those outcomes. That will translate into tangible change that improves the quality of future projects.

Run Better Sailboat Retrospective Meetings in ClickUp

Sailboat retros are useful for understanding how your team feels about past projects and help propel the team forward in future sprints. Executed well, they help you identify risks, eliminate future bottlenecks, and provide clear goals for your next big project.

There’s just one little problem: Most retrospective sessions happen independently of your tasks, reports, and chats. That requires flipping through multiple project management tools, which is a recipe for confusion.

ClickUp’s all-in-one project management tool brings metrics, templates, Goals, Dashboards, tasks, and multiple views into one place—even for technical teams. See the difference for yourself: Create your ClickUp Workspace now for free .

Questions? Comments? Visit our Help Center for support.

Receive the latest WriteClick Newsletter updates.

Thanks for subscribing to our blog!

Please enter a valid email

• Free training & 24-hour support
• Serious about security & privacy
• 99.99% uptime the last 12 months

The Sailboat Retrospective is a fun and creative way for teams to reflect on the sprint and identify areas for improvement. It’s called “Sailboat” because the metaphor of a sailboat helps the team visualize their journey, the obstacles they faced, and the direction they want to sail towards in the future. The Sailboat or Speedboat Method for Sprint Retrospectives is an easy way to: adopt, reflect and map the team’s way forward easily, in a fun, tactile and visual way. It helps the team to reflect on what’s going well and what could be better, analyze their sails and anchors and identify opportunities for improvement or change.

The idea is that the team is on a sailboat, heading towards their goal while dealing with winds and icebergs along the way. Winds help propel the boat forward but obstacles such as pirates, rocks, and stubborn anchors represent the risks that the team might encounter that could slow them down or even stop them from getting to where they need to be.

• Boat : The Scrum team
• Sails : The things that helped us move forward (Wind, Cloud)
• Anchors : The things that held us back (Pirates, Rocks, Sharks, Icebergs, and Anchors)
• Island : The goals to be achieved
• Sun : What the team liked, the actions or attitudes that deserve thanks
• Reef : Represent future obstacles that have been identified, which the group is likely to encounter in the subsequent iterations.

Note : The original Sailboat technique doesn’t have a Sun – I added it to give them a feeling of accomplishment as most teams should understand that there are already things that work just fine. And it’s definitely worth the time to help the team to build on this base.

• Fact-based Analysis for Sprint Retrospective
• Start, Stop, and Continue Sprint Retrospective
• Glad-Sad-Mad Sprint Retrospective
• Starfish Sprint Retrospective
• Sailboat Sprint Retrospective
• Liked Learned Lacked Longed For (4Ls) Retrospective

Different Steps of Sailboat Sprint Retrospective

Step 1: set the stage – draw a sailboat.

Start by setting clear expectations for the meeting, including the purpose, goals, and agenda. Make sure everyone is aware of the retrospective’s purpose and that it is a safe space for open and honest communication.

Let the team draw a picture of a sailboat floating in the water, and fill half the space above and half below the water with the sun, anchors, wind, rocks, reef, and an island or you can simply print pictures and just attach them to the board or any available wall space. This visual representation can help the team better understand their progress.

Note : Team drawing the boat helps to act as an icebreaker and get the group participating and on the boat.

Step 2: Name the Sailboat

Decide the topic/theme of the retrospective and name the boat accordingly.

Step 3: Add mission

Ask the team to write what their mission is, what they want to achieve, and what their goal is, and add these post-it notes to the hull of the boat. The team can amend or clarify or replace as the game continues.

The boat can be saved and revisited as part of sprint reviews, where sails and anchors can be reviewed, rescored, removed, and new sails and anchors added.

Tips : Ask team members to share their successes and challenges during the sprint or project. This allows everyone to see what worked well and what didn’t, which can help identify areas for improvement.

Step 4: Add Sails and Anchors

Ask the team to add sails and anchors to their boat. Sails represent things going well, what’s good, and what is putting the wind into their sails. Anchors are the things that could be going better, the anchors holding them back and limiting progress.

Step 5: Scale your sails and anchors

Ask the teams to scale their sales and anchors, their sails from +1 to + 10, is it a +1 or 2, a nice but relatively small in-value sail, or a main sail that’s providing huge momentum, a +9 or +10?  The anchors from -1, a minor impediment, or -10 this anchor have stopped us from moving forward at all.

Now team should brainstorm and discuss each note, seek to clarify the meaning of the note, and then decide as a group where on the scale it should be. Teams can vote by Dot Voting. The team can compare Sails and Anchors. Is it a bigger or smaller sail/anchor than the previous one? The key here is engaging in group discussions, awareness, and consensus on what the sail/anchor is and how it impacts the team. Sticky notes may need to be clarified with extra information or split into multiple notes to score separately.

Step 6: Add ideas for +1 raising sails and/or anchors

Once all sails and anchors have been discussed and scored ask the team to capture activities and improvements to help raise sails further and raise up anchors. Ask the team to think of small actions that would raise one of the sails, or anchors on the boat by just one point, raise an anchor from a -6 to a -5, or raise a sail from a 2 to a 3. Capture ideas for improvements on post-it notes and place them beside the relevant anchor or sail.

Step 7: Discuss Reef, and Sun and Plan the next steps

Remember to celebrate success and plan action items for current as well as future obstacles that have been identified during the above brainstorming.

If there are numerous suggestions for raising sails and anchors then team activities like estimation games, MoSCoW prioritization, and Dot Voting to help discuss, rank, and decide upon which improvements to take forward. Map the improvements/actions into the team backlog/future work or on a dedicated change and improvement board to help track and measure progress.

Sailboat Retrospective Example

Let’s take an example of a team that developed a mobile app during the sprint. The team was able to deliver the features on time but faced some challenges during the sprint. Here’s how they conducted the Sailboat Retrospective:

• Draw a Sailboat: The team drew a sailboat with a sail, a mast, a keel, a waterline, wind, rocks, and a shore.
• Write the Sprint Goal: The team wrote the sprint goal at the top of the sailboat: “Develop a mobile app with login, registration, and dashboard features.”
• List the Positive Factors: The team listed the positive factors that helped them during the sprint, such as good communication, pair programming, and code reviews. They wrote these on the sail and the mast, as the wind filled the sail and propelled the sailboat forward.
• List the Negative Factors: The team listed the negative factors that hindered their progress during the sprint, such as a lack of automated testing, dependency on external APIs, and unclear requirements. They wrote these on the keel and the rocks, as the obstacles that slowed down the sailboat or could cause it to crash.
• Identify the Improvement Areas: The team discussed the negative factors and identified areas for improvement.

Open-ended Questions for Sailboat Retrospective

• What makes them happy?
• What’s slowing them down?
• What’s propelling them forward? What are the gusts of wind that help our sailboat to move forward?
• Is this bigger or smaller than the last item we scaled?
• If you could cut away one anchor which would it be? How could you do that?
• If you could raise one sail to 10 which would it be? How could you do that?
• What would happen if all anchors were cut away?  what would change?
• If you could add an ‘iron sail’ (an engine!) to your sailboat what would it be?
• How can we raise this sail from a 5 to a 6?
• How can we raise this anchor from a -7 to a -6?

Sailboat or Speedboat Facilitation Tips

• First collect all the anchors, as it’s easier for most teams to organize their current problems.
• Ask the team to turn each anchor into goals, desires, or wishes and put them before the cloud to represent the gusts of wind pushing the boat forward.
• Use these “winds” to define a desirable goal you will use as a true north for the rest of the retrospective.
• Use data to help guide the retrospective discussion, such as team velocity or user feedback. Data can help provide a more objective view of the team’s performance.
• Based on the discussion, identify specific action items that the team can work on to improve. Make sure to assign ownership of these items and set clear deadlines.
• Follow up on the action items from the retrospective in the next meeting to ensure progress is being made.
• Keep the retrospective focused on finding solutions, not blaming individuals or criticizing past decisions. Maintain a positive and constructive atmosphere to encourage open communication and a sense of teamwork.

Sailboat or Speedboat Challenges & Strategies to Overcome

Sailboat Sprint Retrospectives are an important part of the Agile development process, as they allow teams to reflect on their progress and identify areas for improvement. However, there are several common challenges that teams may face during these retrospectives. Here are some of the most common challenges and tips on how to overcome them:

• Lack of Participation: In some cases, team members may be hesitant to speak up during a retrospective, which can hinder the effectiveness of the session. To overcome this, the facilitator can encourage participation by creating a safe and open environment where all team members feel comfortable sharing their thoughts and ideas. They can also try using interactive activities or icebreakers to get everyone engaged.
• Blaming and Finger-Pointing: Retrospectives can sometimes turn into a blame game, with team members pointing fingers at each other for mistakes or issues. This can lead to a negative atmosphere and prevent constructive feedback. To avoid this, the facilitator should set ground rules at the session’s beginning that encourage constructive criticism and discourage personal attacks.
• Lack of Actionable Insights: In some cases, retrospectives can feel like a waste of time if the team does not develop actionable insights they can implement in future sprints. To prevent this, the facilitator can ensure that the team focuses on identifying specific actions that they can take to improve in the next sprint. They can also assign action items to team members and set deadlines for completion.
• Dominant Voices: Sometimes, one or two team members may dominate the conversation during a retrospective, preventing others from sharing their thoughts and ideas. To prevent this, the facilitator can use round-robin or anonymous feedback to ensure that everyone has an equal opportunity to speak.
• Lack of Follow-Through: Even if the team comes up with actionable insights during the retrospective, there is a risk that they may not be implemented in future sprints. To prevent this, the facilitator can assign ownership of action items to specific team members and follow up on their progress in subsequent retrospectives.

Scrum Master Role in Facilitating Sailboat Sprint Retrospective

The Scrum Master plays a critical role in facilitating a successful Sailboat Sprint Retrospective. Here are some key responsibilities of the Scrum Master in this process:

• Creating a Safe and Open Environment: The Scrum Master needs to create a safe and open environment where team members feel comfortable sharing their thoughts and feedback. The Scrum Master should encourage open and honest communication, actively listen to the team members, and ensure that everyone has an opportunity to share their perspectives.
• Guiding the Retrospective Process: The Scrum Master should guide the retrospective process, ensuring that it stays on track and that the team is making progress towards actionable improvements. The Scrum Master should use the Sailboat metaphor to help the team identify areas of strength and improvement, and facilitate a discussion that leads to actionable items.
• Encouraging Collaborative Problem Solving: The Scrum Master should encourage the team to work collaboratively to solve problems and address issues identified during the retrospective. The Scrum Master should facilitate a discussion where the team can brainstorm potential solutions and identify concrete action items.
• Facilitating Continuous Improvement: The Scrum Master should ensure that the team is focused on continuous improvement and that the actionable items identified during the retrospective are implemented. The Scrum Master should work with the team to develop a plan to implement the changes and monitor progress towards the goals identified.
• Monitoring Team Dynamics: The Scrum Master should also monitor team dynamics during the retrospective to identify any issues that may be hindering team performance. The Scrum Master should work with the team to address these issues and promote a positive team culture.

Sprint Retrospective – Tools and Techniques: Click Here

You can read more about the Sailboat technique from Luke Hohmann's book Innovation Games. Luke also provides a free online tool to do these with distributed teams at www.innovationgames.com (choose Visual Collaboration Games).

Length of time:

Usually about 45 minutes to get through data gathering and insight generation.

Short Description:

This retrospective technique uses a sailboat as a metaphor for the team. The team identifies anchors (impediments) and wind (positive forces) and chooses an area to improve.

Either a large white board or a large piece of poster paper. Flip charts can be used, but in my experience are not quite big enough for most teams. They'll work in a pinch. Lots of sticky notes Thick markers

Preparation

Not much required, other than having the materials in place. You may wish to pre-draw the sailboat.

Introduction

The facilitator draws a large picture of a sailboat floating in the water, with about half of the space above and half below the water/boat. He/she then explains that we're going to use the sailboat as a visual metaphor for the team. On a sailboat, there are things that slow it down (anchors), and things that propel it forward (wind). Just like the sailboat, there are things that slow our team down, and things that propel it forward. The facilitator then asks the team to think of what is anchoring the team down and what is propelling it forward, and to start writing one anchor/wind per sticky note.

Gathering Data

Sometimes people will be unsure if they should gather a bunch of stickies and then come up, or just bring them up as soon as they have one. I encourage the latter. As a facilitator, just keep an eye out for the energy in the room - you may need to prompt someone to go ahead and put their items on the board. When the energy starts to die down a bit, give people a fair warning that we'll wrap this part up in a moment. Once you see that everyone is done, get ready for the next step.

Generating Insights

Ask the team to come up to the board and group sticky notes that seem related somehow. As they do it, ask them to read the sticky notes out loud. This part is a bit of a self-organizing activity, it may need a bit of facilitation to make sure that people are getting some value out of the grouping and that one person's opinion isn't dominating when creating the groups. Once the stickies are grouped, ask someone to label the groups. Typically this will result in one or a few large groups of sticky notes, which point out that there maybe a good amount of energy around addressing those items. You may ask someone to read all of the stickies at this point too, just to ensure nothing was overlooked.

Choosing what to do

Finally, you can ask team members to "dot vote" for the group or individual sticky they think should be worked on. I typically give everyone three votes, and they are allowed to use them however they please: place all votes on one sticky/group, distribute them around, or even don't use one. You can do this with drafting dots are simply everyone gets a marker and is on their honor to only place three dots. Total up the sticky/group with the most dots, and move into some root cause analysis and proposed changes to make!

The idea started from Luke Hohmann, and over the years has been modified a few times by many in the community.

Navigation menu

Sailboat retrospective template and guide

This post is also available in: German

Retrospectives are an indispensable tool for assessing past performance and identifying areas of improvement. One way of ensuring retrospectives surface true insights is by leveraging the power of visual metaphors . This is where the Sailboat Retrospective can come in handy.

Whether your agile team is co-located or presently working remotely, a sailboat retrospective is a fun and engaging retrospective technique that ensures the entire team is aligned on the larger vision while simultaneously aware of headwinds and potential threats to project success. 

In this article, we break down how to use the sailboat retrospective template in 4 simple steps in combination with Conceptboard’s collaborative, online whiteboard . 

What is a sailboat retrospective?

A sailboat retrospective is a fun retrospective template whose visual nature makes it engaging for the entire team. It comprises 4 distinct sections. 

Use template

Wind (Drivers)

This section identifies the driving force behind the team’s success. Was it a helpful colleague? A clear project roadmap? A supportive client? It’s also an opportunity to recognize team members who made significant contributions in the sprint or project. The idea should be to keep these tailwinds blowing. 

Anchors (Bottlenecks)

Anchors are the factors that held the team back. What were the blockers that slowed down progress? It could be a lack of clarity about key objectives. Or an inability to see the bigger picture. Or maybe even a lack of motivation. This section is all about introspection and identifying what could be improved in the future. 

Rocks (Threats)

Rocks are risks that can threaten the team’s future success. This section forces the team to detach themselves from the immediate present and take a longer-term view of the project. It is important to identify threats before they result in damaging     

Goals (Vision)

For teams to perform and deliver results at an optimum level, it is important that the team share a set of common goals. The idea should not be to highlight operational minutiae, but rather focus on long and short-term goals. Is the goal to be the team with the quickest time to market? Or perhaps bring build products with the highest customer satisfaction score? This is an important section that drives team alignment. 

How to use a sailboat retrospective template?

Conceptboard’s ready-made template makes it easy to dive into a sprint or project retrospective with your team. Simply click on the ‘+’ button and choose ‘insert template’ to access a large range of templates across business functions. Follow the steps below for a successful retrospective session.

• Once you have inserted the template, share the board with the rest of the team. Click on the share button on the top right and add email addresses of stakeholders.
• Set a stipulated time and have team members add their feedback as digital sticky notes . To make feedback easier to track, have each person choose a specific sticky note color.
• Discuss the feedback shared and identify actionables. Use comments or the pen tool to highlight important feedback
• Download the template as a PDF or high-res image. Given that Conceptboard is a cloud-based whiteboard tool, the boards are saved automatically. 

Agile Retrospective templates

Unlike more traditional sprint retrospectives such as the lessons learned retrospective , visual templates such as the sailboat retrospective, the hot air balloon retrospective or starfish retrospective drive engagement and help teams focus on the big picture. The simplicity of the template means that no technical knowledge is required for stakeholders to add valuable feedback.

A retrospective is also a great idea to keep the team motivated, understand frustrations and improve processes. The collaborative nature of our visual templates acts as a forcing function to get teams ideating and solving problems together. If you are looking for additional sprint retrospective ideas, we’ve rounded up 11 retrospective ideas along with their corresponding templates you can use today. 

More interesting articles for you

Unwrap the Joy: Elevate Your Team’s Holiday Spirit with Our Exclusive Christmas Game Template!

Wireframe Template – A structure to build something great | Free Template

The Complete Guide to Hybrid Employee Onboarding in 2023

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Post Comment

Experience the power of visual collaboration

Experience how Conceptboard boosts your team’s hybrid collaboration and communication.

No credit card

No commitments

Start right now

• Retrospectives
• Health Checks

Sailboat retrospective

Retrospective Idea – Set sail on a bon voyage with an agile and adaptive team.

What is a Sailboat retrospective?

Heard of the term “smooth sailing”? This agile retrospective technique turns your team into the crew of a sailboat travelling to its final destination:  a sunny island. It uses this metaphor to help the people reflect on the last sprint, in order to determine the best way to navigate going forward.

Imagine that your team is working together aboard a sailboat heading on a journey to your final destination. Along the way, you are propelled forward by the wind. You can be slowed or stopped by the anchor. You will have to avoid icebergs, reefs or rocks, but you have your mind set on the sunny island where your team hopes to land and celebrate. The Sailboat retrospective takes this adventurous imagery and helps you to apply it to your last sprint.

Sailboat retrospective format

Before starting the Sailboat retrospective, ask the team to imagine themselves as the crew of the sailboat. Another way to think about it is that the Sailboat is the product, project or epic that they are working on. Now, ask them to consider the following.

What is the final destination for the team? What is their goal or vision? This is where they are heading to and represents their version of success.

The Wind (or the sails)

What is pushing the team forward towards their vision? What is driving them towards the goal? It could be their own capability, support from champions, being well resourced or being motivated by a common goal.

What would slow the team down, or bring them to a complete stop? What would create drag and reduce velocity? It may be a dependency or policy. It could be a lack of process or one that is too complex. Some anchors may be necessary, and others need to be considered to see if they will be a constant drain on the team, making them less agile and achieving less progress.

What are the risks or potential pitfalls along the way? What does the team have to watch out for? There may be communication gaps, the response from competition or technical risk that could unhinge the team. Understanding what the risks are early can help the team think of ways to navigate around them or put signals in place as a warning as part of the next sprint.

What is making the team feel positive? What are the good things that can come out of this? These may be things that they look forward to and may include customer feedback, usage or improving the robustness of their infrastructure.

Some other aspects that people can include into their Sailboat Retrospective template include Choppy Waves (Things that make them feel anxious) or Calm Waves (Things that can help them experience a state of flow ).

This style of retrospective can be used when your team is having trouble completing a task. Having the ability to see what has been slowing you down and what you have achieved despite this, can be helpful in providing confidence when trying to complete a difficult task.

Suggested icebreaker questions for the Sailboat retrospective

• What is your ideal island holiday?
• Which would you rather have: a sailboat or a speedboat, and why?
• Who would you want to be your sole companion if you were stranded on an island?
• If your boat is sinking and you can only save one thing, would you rather save your gold or your pictures?

Retro Rehearsal

Invite your team to rehearse the retro referencing their life journey so far.

Then ask them:

• What has pushed them forward to reach their goal?
• What has slowed them down?
• What has made them feel better throughout the journey?

Ideas and tips for your Sailboat retrospective

• The Sailboat retrospective aims to reduce the focus on any one person. It treats the team as a team and the sailboat as the project. This is a good time to remind people that they are there to help and support each other and that the goal is to help everyone reach the final destination together. No one gets thrown overboard, and no one left behind!
• Aim for a few action items that come out of your agile retrospective that will help you course correct. While it’s good to dream and to ponder, it’s also important that the team walks away knowing that their sailboat is travelling at the right speed in the right direction, or that there is a course change that is needed.
• Fold up a ship and float it in a bowl in front of the team or camera to bring your retrospective to life!
• If you are a remote team, you can request each member to change their screen background to a place they hope to visit on their next trip.
• Utilise team health checks to measure and track your team’s happiness over time. The Team Health Check   is a specialised self-evaluation tool for agile project teams that wish to improve their collaboration in order to achieve project objectives.
• Have fun looking back. Request input from the team about each retrospective to identify a structure or activity that people enjoy so that you may conduct them more frequently. People frequently learn more effectively when they are having fun or laughing while learning.
• Using a timer, you can Timebox discussions. This will keep the conversation on track and the retrospective on course.
• A good way to conduct the sailboat retro is to discuss ways to mitigate the identified risks and to prioritise the factors that are slowing you down. It should be clear what steps can be taken to fix, avoid, mitigate or eliminate the problem.

How to run a Sailboat retrospective in TeamRetro

Start your retrospective in a click Log into TeamRetro and choose your sprint retrospective template.

Discuss the most important things first You and your team discuss the top voted ideas and can capture deep dive comments.  Presentation mode allows you to walk your team through ideas one-by-one and keep the conversation focused.

Review and create actions

Easily facilitate discussion by bringing everyone onto the same page. Create action items, assign owners and due dates that will carry through for review at the next retrospective.

Share the results Once you have finished your retro, you can share the results and actions with the team. Your retro will be stored so you can revisit them as needed.

Sailboat Retrospective

Sailboat Retrospective is a fun and easy way to boost the communication of what went well and what slowed the team during current sprint. Based on the topics addressed during the retrospective, the team agrees on the improvement activities needed for future sprint.

The tropical island represents the set sprint goal they have aimed to achieve in their daily work during the sprint.

The Wind represents everything helping them to achieve the sprint goal, pushing the team's sails boat to go even faster.

The Sun represents all the things making them feel good and happy during work. As a retrospective is a time for team celebration this is a highly appreciated topic to bring up and an opportunity to bring forward kudos to your team friends.

The Anchor on the Sailing boat represents everything that is slowing us down an holding us back on the journey towards the sprint goal.

The Reef represents potential risks ahead that we see will jeopardize future sprint work.

How to use the Sailboat Retrospective

Set the stage - start the Retrospective by introducing the team of the sailboat metaphor.

Reflect and write individually - Give each team member 7 min to individually write down stickies on the board in the different areas of the sailboat canvas.

Present and discuss in pairs - Have breakout sessions with 2 (or 3) persons in each breakout room where they present their stickies to each other.

Summarize - Each pair summarize the discussion during breakout so all team members can hear what has been discussed. Opportunity to ask questions if any.

Group stickies - In case of more than one sticky with the same topics the team agrees upon grouping them together.

Voting - Time for team voting on the topic(s) that needs focus going forward. It could be topics helping the team go forward so they need continue with these to keep momentum, or topics related to what is slowing them down or potential risks coming up.

Find Actions - Based on the highest voted topic(s) the teams agree on improvement action going forward in the next sprint.

• Meetings & Workshops
• Retrospectives
• Agile Workflows
• Facilitator
• Consultants

Submit your template →

Do you have a great board to share with the world? We' ll help you turn it into a template to share with the community.

Similar templates

Quick Team Retrospective

Retrospective in the Island of Golocans

Retro My Suitcase

Facilitation

Hire me to facilitate your retrospective or a custom made workshop!

Book me now!

How to Run a Sailboat Retrospective: A Step-by-Step Guide

Explainer video

Introduction

The power of the sailboat retrospective is in the way you visualize everything from the previous sprint. You can visualize the sprint goal on the template as your focus point.

Running the sailboat retrospective, you and your team are trying to find how to get the boat to smooth sailing. Searching for risks they'll face, seeing what is working, looking for things that are slowing them down, and making sure the sailboat is heading in the right direction.

The sailboat retrospective template is one of the top agile retrospectives you can use to improve your team!

The elements of the sailboat retrospective

The retrospective consists of five elements. The sailboat, the sail, the anchor, the rocks, and the island (the focus point of the retrospective).

It gives you, as the facilitator, the perfect starting point to communicate the exercise through metaphors.

The sailboat

The sailboat represents the entire team and their processes sailing to their goal. You can use the metaphor: "Is the sailboat heading in the right direction?"

The island represents the sprint goal of your team's last sprint. This is where the team wants to go.

What is giving us wind in our sails to go to the island? What helps us move forward?

The team focuses on the good things that are happening and are helping them achieve their goals. What efforts move the team forward to their sprint goal?

What is holding us back from going to the island?

Here the team focuses on the bad things that they are doing. They'll look for impediments and issues they've faced.

What are the rocks we face when going to our island?

The rocks represent the potential risks they'll face. This part of the exercise helps them to be proactive about oncoming risks.

The benefits of the sailboat excercise

The sailboat retrospective is a great tool to see if the team is doing the right things to hit their goal. They identify risks, see what is holding them back and get to know what is working.

It brings the team members on the same page and helps improve the team's success. It gives the scrum master valuable feedback that he or she can use to help the teams focus.

As with every retrospective , it helps the team apply continuous improvement in their workflow as described in the agile manifesto .

How to run the sailboat retrospective

Facilitating sailboat retrospectives is pretty straightforward. Every good retrospective has a chronological number of exercises. This format makes it easier for the facilitator and the agile team.

We are going over the sailboat retrospective template, and I'll give you some retrospective techniques where you and your team can focus when creating actionable items.

Set ground rules for the retrospective (+- 3 min)

During a retrospective, we take our team and ourselves under the microscope. This can be an uncomfortable experience for many of us. Therefore we need to set some ground rules with the team and create an atmosphere where people feel comfortable participating.

Good ground rules

• What is said in the retrospective stays between the participants
• It is encouraged to air dirty laundry and express opinions.
• Try to focus on organizational systems and process improvements.
• It is a blame-free environment
• Encourage participation from everyone

Introduce the sailboat exercise (+- 3 min)

When the ground rules are set, we can introduce our sailboat and what we'll do during the retrospective.

Here's an example introduction:

Team, today we are doing the sailboat retrospective. We, the team are on the sailboat. We're trying to go to the island which represents our last sprint goal. [Insert sprint goal]. During our trip we've been lucky to have great wind in our sails. But we noticed that our anchor has been dragging along and slowing us down. We're going to try to raise our anchor a bit higher so we can move faster to our island. Like every sail trip, we'll face some rock along the way. This is risky business. We'll try to inspect what is risks we'll likely face so we can improve our sailboat and go smooth sailing.

The sail (+- 10 min)

The first step the team members take is the sail. Here we are going over what is working for the team. This exercise helps the team loosen up for the harder parts of the sailboat retrospective.

One retrospective technique we'll use throughout is working together alone. This means the exercises are done in silence alone. After a set period, we'll present our ideas and choose one to continue with.

Before flying straight into the sail exercise, introduce it to your team.

The first part of the sailboat retrospective is the sail. We will look what helps us move forward in our journey to our island. [Insert sprint goal] We are going to all work in silence for [Insert forseen time] when we are writing down our thoughts. Write every thought down on individual sticky notes. Afterwards we'll present our sticky notes to each other. Are there any questions?

When time passed that the team worked alone, we'll present the sticky notes to each other and put them on the sail. Keep the presentation simple, don't go deeper into the topic that is written down. Just saying out loud what is written on the sticky note is enough.

The anchor (+- 10 min)

The second step in the sailboat retrospective is the anchor. Here the team will focus on what is holding them back from reaching their target. Here we are trying to find where our process is lacking.

Here we'll use the same retrospective technique working together alone.

You can use the following template when introducing the anchor to your team.

Now that we know what helps gives us wind in the sails and helps us move forward. We'll now focus on our anchor. What is holding us back for moving forward towards [Insert sprint goal]. We are going to work again in silence alone for [Insert forseen time]. Afterwards we are not going to present the items to each other. We're just going to stick them on the lower side of the sailboat. Are there any questions?

When the time has passed, let the team put the sticky notes on the bottom side of the sailboat.

The rocks (+-10 min)

The third step in the retrospective meeting is the rocks. What rocks lie ahead of the team? After this exercise, we'll have identified risks we can be proactive about.

Again, we're working together alone. Afterward, we can stick our sticky notes on the rocks below our boat.

Here's an example introduction to the rocks:

Now that you've written down our anchors for our team, we're going to look ahead and see what risks we face for reaching [Insert sprint goal]. Again, we're woriking in silence for [Insert forseen time]. Afterward, we'll stick our sticky notes on the rocks. Are there any questions?

When the time has passed, let the team put the sticky notes on the rocks.

Vote! (+- 10 min)

We've captured a lot of insights from our team. But where do we need to put our focus? This is where we're going to vote.

There are multiple ways to vote for a focus point with your team. Here we are going to use dot-voting .

Give each team member ten votes they can use to vote on the sticky notes. They can vote on their own post-its and vote multiple times on one post-it. There are no rules.

While the team is voting, they can rearrange the post-its to make groups of related items.

Here is an example introduction to the voting part of the retrospective:

Now that we've capture all of our insights it is time to choose where we want to focus on as a team. We'll do this with our voting dots. You can vote on your own items and vote on multiple times on one item. While we are looking over our insights, rearrange the items to group them toghether if they are related. Are there any questions?

After time has passed, take the item with the most votes and put them to the side of the sailboat. Continue this step until you've created a top 3.

Brainstorming session ( +- 15 min)

We now know where the team wants to focus its efforts toward improving its processes. Now it's time to brainstorm ideas to improve future sprints.

We take the most voted issue and rephrase it to an opportunity question. We use the "How Might We" structure to create an opportunity for our anchor or risk that has been chosen.

Take the "How Might We" question you've created and put it on the top of another whiteboard or flipchart.

While we are brainstorming, everyone should work in silence again.

Here is how I would introduce the brainstorming session:

It is clear for us as a team where we want to put our efforts to improve our processes. We are going to brainstorm on [Insert "How Might We" question]. You get [Insert forseen brainstorm time] to generate ideas that we can do in the next sprint to resolve [Insert problem statement]. You are working in silence again.

When the timer goes off, the team must select the best ideas. Here you can give them five votes to vote on the best ideas.

Create actionable items (+- 10 min)

The team voted on the best idea they've found. Now it is time to take action! An idea is great, but execution is needed to improve their current process.

For an agile team, this could mean updating their definition of done. Most of the time, you'll define an experiment you'll run with the team.

• When writing an experiment, consider the following questions.
• How long will this experiment run?
• Who is going to conduct this experiment?
• What is the expected outcome of this experiment?
• When are we going to reflect on this experiment?

You can write your experiment in the following format:

What? Only allow our premium users to use the model. Who? Team Zebra When? Next sprint Expected outcome? Our premium users use the machine learning model more. Reflection date? 20/04/2023

The sailboat retrospective is a great tool to create team alignment for improving the team processes. The metaphorical way helps the facilitator and the team in the process to identify areas where they can improve, what is holding them back, and the risks they'll face.

You might also like

Sailboat Sprint Retrospective Format for Development Teams' use

People learn in all different ways. Some prefer auditory activities, while others learn better through kinetic or visual practice. This sailboat retrospective template is fitted for those who like a visual and metaphorical representation of the ideas being discussed.

How to run the Sailboat Retrospective TL;DR: 

The sailboat retrospective is a great way to create a team vision while addressing any problems that may pop up along the way. This simple agile retrospective format , also called the Pirate Ship Retrospective, involves a little artwork and a lot of discussion. It's a 4 column retrospective format, similar to the wedding retrospective and KALM , which can be very effective in giving the team a platform to come up with a vision and understand what problems or issues are impeding it.

The sailboat retrospective looks like this:

• The organizer of the retrospective draws a sailboat with an anchor, rocks, some islands, and wind.
• It’s explained that each part of the drawing represents a part of the sprint: there are certain factors that slow it down, and others that are the driving force.
• The islands represent the team’s goals and visions. Those should be written down for everyone to see.
• The team is asked to write down everything from the past sprint that slowed them down or drove them forward. Those are placed accordingly on the drawing.
• These are discussed and the team votes on the critical items to focus on.
• Then, teams can start root cause analysis and come up with solutions and outcomes.

What Is the Sailboat Retrospective?

Picture a vision board, but more dynamic and specific. It includes points of contention, future goals, causes of stagnation, risk prediction, and motivating forces - all wrapped up in a relaxing and scenic illustration of a sailboat or pirate ship at sea. 

The idea is for team members to really see their words in action. The past and the potential. 

Conceptualizing what slows the boat (the team/project) down and what blows it in the right direction is a great way to compartmentalize what processes have and haven’t been working for a smoother path to future destinations. 

When Can the Sailboat Format be Used?

The sailboat retrospective, or pirate ship retrospective, like most scrum retrospective templates , should be used directly following an iteration, so that feedback is fresh in the memory. Steps for moving forward as a unified front can then be established for upcoming projects.

A General Guideline to Using the Sailboat Retrospective Template

Either physically or virtually on a versatile retrospective platform like GoRetro , begin with an illustration of a sailboat in some water to represent the past scrum/sprint/project/team. 

Draw an anchor dropped to the seafloor, to represent what weighed the team/venture down. Towards the front of the boat, draw an island to represent the ideal destination (goals). Draw some clouds blowing wind to capture the motivating forces that propelled the team towards the 'island', and finally draw some menacing rocks just below sea level - an obstruction to the boat's path/goals. Add any other elements you'd like.

With this illustration and its metaphors explained, allow team members to add their answers to each area of the drawing. For example, in the clouds, someone could stick a note that reads 'gestures of appreciation’ as something that kept their momentum and morale up. 

Everyone can then discuss these points and get varied perspectives on those that aren't unanimous. To keep things democratic, you can vote on these controversial decisions before taking any future actions. 

By the end, the goal is to have a clear idea of what parts of the process should be repeated and what new things should be implemented for future sprints. 

How to Run A Sailboat Sprint Retrospective In GoRetro

GoRetro makes so many retrospective templates so easy to execute. Once logged in, all your team members can be invited into the dashboard and onto the chosen template. 

Team members can attach their thoughts to the virtual illustration and even take votes. The platform hosts discussion and comment threads for clear and easy participation, and even offers AI support and suggestions! 

Once a vision of future strategies and processes is formed, action tasks can be assigned with due dates. Then, the entire retrospective process will be virtually recorded for reference at any time in the future to ensure that everyone is remaining on task with all their new tools and strategies. 

Who is this Retrospective For?

The sailboat retrospective / pirate ship retrospective is for everyone who took part in the initial sprint. Each individual plays a different role in the process and has new and useful perspectives to add to the collective discussion. Leaders, partners, and valued customers could also be present.

‍ Why Is the Sailboat Retrospective Agile Format Important?

Reflecting on what edits to make for future endeavors should always be an evolving process, full of trial and error, making retrospectives incredibly important. 

This one in particular is fun, simple, and diverse for different learning/participation styles and needs. 

It's an effective way to unify the team, reminding them they are all part of the same crew, on the same boat, going in the same direction and working together. 

Retrospectives are so important for the unity and morale of the team. Putting strengths and weaknesses into perspective is a key factor in refinement strategy and group support. These meetings, whether virtual or physical, are a great place for praise, deliberation, and refocusing. 

With more and more of your workflow taking place online, trust GoRetro to get your team together online, guide effective discussions and keep every detail of the minutes forever! 

Interested in other retrospective formats?

‍ From " What Went Well " to " Starfish retrospective ", " 4Ls retrospective " and more, GoRetro's offers a wide variety of retrospective templates . Pick up the best template for your team or create your own retro board using our custom option.

Featured Posts

Best questions to ask in your daily stand-up, what is continuous integration in scrum, what is agile cadence, the best sprint goal templates, refining norms for your scrum team, top post mortem questions to ask, about the author.

Engineering leader, passionate about coding products and value creation. Vast experience with managing R&D teams at various scales. Embracing innovation and transformation for constant improvement.

Related Posts

Mad - sad - glad retrospective format for sprint retrospective use, 4ls retrospective format: liked learned lacked longed for retrospective, lean coffee retrospective format for sprint retro use, what went well - what didn’t go well sprint retrospective, starfish retrospective format, oscar academy awards retrospective format for dev teams, using smart goals to make the most of your retrospectives and projects, iteration retrospective (scaled agile) format for your use, start-stop-continue retrospective format for development teams, join thousands of companies.

Retrospective Techniques

Start, Stop, Continue

What Went Well

Mad Sad Glad

Lean Coffee™

Guided Facilitation

Retrospective History

Action Plans

Integrations

By team and department.

Human Resources (HR)

Improve Facilitation Skills

Increase agile team productivity.

Building team Culture

Remote and hybrid work.

The Ultimate Guide to Agile Retrospectives

Retrospective Hot Seat

Customer Stories

Agile Roundup

Help Center

Mad, Sad, Glad

Create your own format.

Scrum Master

Agile Coach

Sailboat Retrospective

Picture a sailboat headed toward a beautiful tropical island with all the drinks with umbrellas you could ever want.🍹 But as you sail to your island paradise, you want to stay wary of the obstacles in your way, like rocks or coral. And you want to harness the wind to keep your team progressing toward your end goal. Wait...obstacles, progress, and goals? Your vacation has all the makings of a great agile retrospective! In fact, a Sailboat retrospective is a useful retrospective template that can illuminate all of the things that are helping and hindering your agile team. ⛵

Use the sailboat retrospective technique when you want to…

Define your team's end goals.

Identify risks that may disrupt your path.

Identify what is slowing your team down on its journey to the end goal.

Identify what helps the team achieve its goals faster.

How to run a sailboat retrospective?

This fun retrospective exercise is all about the visual. So, before we sail off on this meeting, the facilitator sets the scene by explaining all elements of the retrospective: a sailboat heading towards an island, rocks between the sailboat and the island, gusts of wind pushing the sailboat, and an anchor hanging from the sailboat. Each of these items represents a part of the team's previous sprint. Together they will paint a full picture of your team's current sprint retrospective.

• Represents the teams’ goals and larger vision.

• Represent the potential risks the entire team may encounter while working towards their goals in future sprints.

• Represents things that are slowing team productivity and success.

• Represents ideas for improvements that may help propel the team towards your goal.

Setting the Stage

Before casting off, make sure everyone has a shared understanding of the common goal of the retrospective. Depending on the size of the team, your entire retrospective meeting has the possibility of lasting several hours. 😱 If you want to limit the time on this retrospective session, create a timebox for the entire meeting (30-60 minutes, depending on the size of the team) so the team has an idea of how much time each discussion should take.

Begin the retrospective by deciding as a team the purpose of your “mission,” keeping the end goal in mind. 🏝 At this step, the team will be expected to brainstorm and identify areas and processes that are:

⚓ Currently hindering the team

⛰️ posing risks to the team achieving the goal at hand, 🌬️  already existing team strengths that are propelling the team forward.

The facilitator should set a timebox and let participants develop their ideas and capture these as multiple notes. During the brainstorming session, the entire team should keep their valuable feedback private. 🤫 This helps prevent groupthink and ensures that team members aren't swayed by seeing the opinions of others. (Psst, we know a retrospective tool that makes this step easy...) 

Many notes will likely contain similar (or even identical) ideas. It's always great to see points of team alignment! To get the next step started, the facilitator announces the timebox (5 minutes) and encourages the participants to group notes into logical themes. This part of the exercise is intended to highlight popular and differing opinions that are in need of a discussion.

🌑 Identify the rocks: What are the things the team recognizes as potential risks to their success?

💨   identify the wind: what’s going well for your team, or, in other words, what’s putting wind in your sails, ⚓   identify the anchors: is there anything negatively anchoring your ships and blocking opportunities for improvement ‍.

Sometimes discussion topics are obvious. For example, if there are several similar notes on process improvement ideas, your team has an obvious pain point to discuss. However, sometimes it can be challenging to structure the discussion in an organized way. If this is the case, the facilitator can opt to use dot voting to prioritize the discussion based on the collective desires of the group.

Team Discussion

If dot voting was used, then the team discusses the notes in prioritized order. If not, the facilitator can choose the order of discussion. When it comes to timeboxing the discussion, you have a couple of options. You can set a period of time for the entire conversation (20-40 minutes), or you might choose to timebox the discussion of each individual topic (typically 5-10 minutes). The second approach tends to keep the conversation on topic and moving at a faster pace.  Throughout the discussion, the facilitator focuses on each part of the scene and helps the team evaluate all the anchors, wind, and rocks. For example, during the discussion, the team can strategize how to turn an anchor into a gust of wind, or eliminate as many rocks as possible. As the conversation progresses, it's imperative that the facilitator also write down any action items that come out of the discussion in order to help the team realize continuous improvement with each sprint.

This effective retrospective technique is a creative way for your team to visualize the end goal and understand what systems need to change for your team to reach all their islands. 🏝️

Ready to run a sailboat retrospective?

Get started with Retrium

Try all retrospective templates for 30 days

Learn more about Retrium

Get to know Retrium with a customized walk through

Terms of Use

Subscription Agreement

Privacy Policy

Introduction to using a sailboat retrospective

Reading time: about 5 min

Sailboat retrospectives are a unique way to think about your sprints or projects and brainstorm ideas for how to reach your goals. By using this popular retrospective model, you can keep your retrospective meetings collaborative and engaging. 

What is a sailboat retrospective?

Sometimes referred to as a speedboat retrospective, a sailboat retrospective uses a metaphor to understand the Agile journey, placing various aspects of a sprint or project into perspective for your team. Sailboat retrospectives are an excellent visualization technique. By taking familiar elements of a sailing journey and comparing them to the obstacles, goals, and tools your team has, you can look back on what happened with a project and highlight areas of particular interest and emphasis. 

Elements of a sailboat retrospective

Each element serves as part of the metaphor—a sailing adventure where your team is trying to sail successfully to an island destination. Along your journey, the wind carries you forward by filling your sails and pushing your boat, but one or more anchors or rocks can get in your way and impede your progress. 

As you think about your sprint or project’s story, you may find obvious elements for each category that stand out to you. Other elements may not be so obvious or may fit a different category than you’d expect. Creating a sailboat retrospective can change your interpretation of a recent sprint and cast light on elements you weren’t previously aware of. 

Anchors represent what held your sprint back from moving forward. Anchoring your boat in place, these obstacles can be issues that cause delays, challenges you identify partway through your voyage, or impediments presented by other projects, stakeholders, or environmental conditions (such as the market). 

You may have more than one anchor that restricted your project. As you brainstorm your anchors, you could make a note of solutions that come up, but don’t focus on them until you’ve identified all of your anchors. Remember to think about:

• Anchors stall or drag your project
• How might you manage anchors?

Wind is whatever helped your team keep moving. Wind gives your project momentum and may be your advantages, helpful team members, support from stakeholders, or even the roadmap you used to guide your project along. Looking back at your previous sprint, considering what helped enable your project’s progress allows you to see what represents wind in your sailboat retrospective. 

If it’s tempting to skip over the wind section and focus on your challenges, keep in mind that this part of the retrospective is a great time to thank colleagues and recognize stakeholders. Positive recognition is encouraging for your team and creates a positive cycle that supports your project. Consider the following:

• Wind advances your project forward
• How do you guide your boat with the wind? 

For any project, threats are a strong possibility, so planning for them is appropriate risk management. Real rocks are destructive to boats and can impede the adventurer’s chances of ever reaching the island. Since rocks aren’t always visible from inside the boat, sometimes rocks show up unannounced. If sailors see rocks, they can correct their course, but it’s too late to avoid a rock if you’ve already hit it. 

Retrospective rocks are a little like that, too. Once the risk is now part of your project’s reality, your best approach might be to manage it. Anticipating rocks and avoiding them in the first place can save a lot of hassle and potential fallout. Just like real rocks tend to be in specific places (such as near land), these rocks can be more common under certain conditions. Finding out what increases the probability of hitting a rock is a valuable part of your journey. Key things to think about for rocks include:

• Rocks can damage your boat
• How can you avoid rocks with risk management and planning? 

Island/ Goal 

Everyone wants to reach the destination eventually. That’s why you’re working on the project in the first place! Successfully reaching the island represents your team’s success when they arrive at the project destination. All of the planning, navigation, mitigating risks, and looking for wind to push your boat forward culminates in finding the island. You’ll want to make sure your entire team knows what the goals and expectations are for a project. During the retrospective meeting, think about:

• The island is your goal
• Did you reach the island? 

The sun is an optional element, but it can be helpful. Sunshine can be one of the best parts of both the journey and the destination. Instead of including your kudos and positive highlights in your “wind” category, you can count these as the sun shining on your team, giving team members a chance to appreciate the work of their colleagues. Consider:

• The sun makes your team happy
• Where did the sun shine and how can you recognize it?

When to use a sailboat retrospective

Sailboat retrospectives are helpful for nearly any project and can become part of your project management process. Use a sailboat retrospective: 

• During a team meeting: With a sailboat retrospective, you can show your team important information and provide a point of discussion.
• If your project is stuck: If your project stalls and you’re not sure where to go next with it, a sailboat retrospective could help you determine how far you are from the island, if you’ve hit a rock, or if you’re dealing with anchors. 
• To inform stakeholders: Sailboat retrospectives are also a helpful technique for informing stakeholders on a project’s outcome. 
• After the project: Following the completion of your project, you can use a sailboat retrospective to review what was successful and what needs improvement next time. 

Learn more about running effective retrospective meetings.   

How Lucidspark can help 

As a virtual whiteboard, Lucidspark can be used to put together sailboat retrospectives and to review and collaborate on. Lucidspark provides a place where you can brainstorm and share your ideas visually. 

Use Lucidspark to create and review your sailboat retrospective as a team during a virtual meeting or get asynchronous feedback and comments whenever your team is online.

Create your own speedboat retrospective in Lucidspark.

About Lucidspark

Lucidspark, a cloud-based virtual whiteboard, is a core component of Lucid Software's Visual Collaboration Suite. This cutting-edge digital canvas brings teams together to brainstorm, collaborate, and consolidate collective thinking into actionable next steps—all in real time. Lucid is proud to serve top businesses around the world, including customers such as Google, GE, and NBC Universal, and 99% of the Fortune 500. Lucid partners with industry leaders, including Google, Atlassian, and Microsoft. Since its founding, Lucid has received numerous awards for its products, business, and workplace culture. For more information, visit lucidspark.com.

Bring your bright ideas to life.

or continue with

Retrospective: The Sailboat

• June 2, 2022
• No Comments

The sailboat retrospective

The sailboat retrospective is a good format to use when you want to reflect on your progress towards a specific goal. This goal can be product- or process related.

The Icebreaker

For this template, we selected a fun icebreaker: share a picture of meme that explains the last iteration to you. You shouldn’t go into too much detail during the icebreaker, as the intention is just to get everybody engaged and participating in the retrospective. But, you can ask the participants to share a few words about the picture or meme that they shared, to get some more insights and make it interactive.

The retrospective format

The sailboat retrospective consists of two rounds:

• “Our destination”: what’s our goal? This should be the main theme for the retrospective. What are we striving for? As mentioned above, this can be something related to the product that you are building, or it can be something related to the way of working within the team.
• “Helping us”: what is currently helping us on our road to achieving this goal? What should we keep doing?
• “Holding us back”: what is currently holding us back, slowing us down, or preventing us to reach our goal?
• “Obstacles”: what risks do we see in the future, that could prevent us from reaching the goal? Something that we see happening, but is not yet happening to us today.

After explaining the stages to your team, give everybody a few minutes to write down their thoughts on a post-it. After this, you can do a quick dot voting session to determine the most important one(s) and start with a discussion on those.

First discuss all the post-its in the “Destination” category and come to a conclusion of the goal of the team before discussing the other stages. It’s important that everything you are discussing in the “Helping us”, “Holding us back” and “Obstacles” categories are related to the overall goal that you are trying to achieve as a team.

While having the discussion on a topic, always focus on what’s within the control of the team. Don’t focus too much on external people or factors, but mainly on the things that are within the control of the team to identify improvement actions that the team is able to take. You want to have 1 – 2 action items at the end of the retrospective that you can implement in the next iteration(s). Remember: you will not always have big live changing action items in each retrospective. That’s also not the intention. A small action that brings a small improvements is already very good. Try to improve a little each sprint instead of trying to bring big changes at once.

About last retrospective...

A crucial part of the retrospective is to reflect on the outcome of the previous one! Teams often forget to do this, but it is very important as it gives the team the confirmation that the action items are actually important… And that we want to make sure we improve! There is a section on the top of the template where you can refer to the action items of the last retrospective. Go over them, see how you are doing in regards to them, and decide what to do next.

Rate your retro!

At the very end of the retrospective, I ask the team to quickly rate their retrospective with focus on: 

• Did we have a good discussion? Did we speak openly, and respect each others opinion?
• Do we have valuable action items? And, are we confident that we will do them in the next sprint?

We also use a feedback wall where team members can share their feedback on the retrospective. As the facilitator, you can encorporate this feedback into the next retrospective session.

Other things about the format

On the very top of the format, you can see 2 elements:

• Action items / experiments: this is the place where you would write down the action items during the retrospective. This makes it easy to summarize them at the end of the session.
• Idea for the next retrospective: I always like to foresee an area where people can give feedback or give input for the next retrospective. This can be feedback on the current format, ideas for a new format, tips, general feedback… Anything that can help us make the next retrospective even better! I would not make it required for people to give input in this, make them feel free to give input when they come up with something.

Download the template (for free)

You can download the Miro template for free below:

If you don’t have a premium version of Miro, you can also download the picture at the top of the screen and create the board in Google Drawings .

Tom Abrahams

Recent comments, leave a comment cancel reply.

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Other templates

The Scrum Master retrospective

Movie retrospective

Sprint progression retrospective

Cats and dogs retrospective

Privacy overview.

Sailboating: How This Agile Activity Can Help You Spark Innovation

UI/UX Design

Working Agile

When developing a digital product, the classic process involved documenting requirements, designing solutions, and building and testing in a waterfall approach. Then Agile came around and changed everything, decreasing the time it took to deliver working software and reducing the need for front-loaded documentation.

By working in ‘sprints’, development teams can focus on core requirements to build a product, while allowing for the ups and downs that come with developing complex technology. An added bonus is that clients can deliver feedback after sprints rather than at the end of the ‘completed’ project.

Agile is a system of working, but it’s also a mindset based on promoting better interaction between the people involved in the project, the flexibility to change things when required, and focusing on working, functional product over bureaucracy. It’s a flexible way of working - hence the name ‘agile’, but it also encourages the concept of taking stock after a sprint to see what worked and what didn’t.

This is often called an Agile retrospective. These are exercises performed after a sprint or project to determine efficiency and spot problems or issues so a team can avoid them in the future. It also ties into a Lean methodology in that a retrospective helps cut future waste.

One of the most powerful forms of retrospectives comes in the form of the ‘sailboat exercise’.

What is the Agile Sailboat?

If you’re planning to work in an Agile system, or working with an agency that utilises Agile methodology (hint hint, it’s us), then you’ll probably encounter the term sailboating.

Even if you’re NOT an agile organisation, the sailboating exercise can still be a great way to help rethink your projects and prioritise the production journey. It’s a visual metaphor and an exercise that focuses on the team and future direction.

A sailboat workshop involves two main processes: the team writing down answers to a few questions and then mapping these answers against the ‘sailboat’ metaphor.

You can use a digital board such as Miro for this, or Sticky notes will do the trick if you’re doing it in person. Ask your team the following questions (adjusting based on whether you’re running this as a sprint exercise or at an operational level.)

At operational level:

What’s moving us forward?

What are our goals?

What’s holding us back?

What’s not gone so well?

For sprint exercises:

What risks did the sprint/project face?

What delayed the sprint?

What propelled the sprint forward?

The Sailboat in action at a KOMODO Innovation Workshop.

Once your team have created their answers as Sticky Notes, ask them to stick them to a graphic you’ve drawn or printed that includes the following elements:

A boat - this is your team/project.

An island - this is the goal you’re working towards. It can be the specific features designed in a sprint or a more operational-level goal.

Wind in your sails : what propels your team/project forward.

Rocks : the risks your project faces in the future as it reaches the goal.

Anchor : the problems and challenges which delayed the sprint/project.

Once the team has had a chance to place their sticky notes, go through as a group and see if you agree on the placements. Then see if there’s a common theme being suggested by multiple people as a delay.

Just like you would in an Agile sprint, you can use this information to pivot and enact change. For example, if there’s an anchor problem holding your team back, prioritise a way to remove it. Outlining the ‘rock’ or future risk also helps you spot potential obstacles that should be dealt with before they become a problem and ‘sink’ the ship.

The sailboat exercise is great because it’s a visual metaphor that is easy to understand. It aligns the team and quite literally puts everyone in the same boat. For an agency/client relationship, sailboating also helps both sides of the relationship feel they are aligned and heading in the right direction.

While the Sailboat method is so often used in a retrospective fashion, we believe it has great value as an onboarding process for new projects and why it features as the first activity in our innovation workshop process.

Sailboat as a prospective tool

The sailboat system can also be used at the beginning of a project to help map out your strengths and weaknesses.

Demand for your product.

What your user’s needs are.

What solutions are most important in terms of priority.

We’ve written about this sort of thinking many times - but it’s so important we thought we’d mention it again here in the context of the Sailboat exercise. You can’t, for example, just go into a planning session with ‘general ideas’ of what your customers want. Instead, you need to do research and ensure that your product can solve a genuine need . Otherwise, it’s all based on guesswork.

Once you know enough about your users, you can use Sailboat to plan the overall product or project. This time, you’d define the elements as:

Rocks : what risks does the product face in terms of competitors, technical issues, user error?

Island : what functional requirements are most important - they should be positioned closer to the ‘shore’ to create priorities.

Anchor : what issues could delay the project. Think of factors like stakeholder intervention, poor client/agency communication etc.

Wind/sail: what can contribute towards the product being completed to the right timeframe?

While you might not have the same retrospective analysis to assign actual, tangible things that went wrong for your rocks etc. The sailboat is still a good way to map out a project at the beginning to get your team on the same page.

Remember that the sailboat as a concept is not really that important. It could be many different visual metaphors - all of them just have to share a way to map goals, threats and success factors.

By completing these exercises either at the start of a project or as a retroactive after a sprint as intended, you’ll be putting your team on the right track and creating a more collaborative process both internally and, if working with an agency, externally too.

The sailboat is just one Agile exercise we love. If you choose to work with KOMODO for your digital product development, we’ll lend our workshopping expertise to your project journey to help ensure the product is as functional and successful as it can be. Get in touch if you’d like to know more .

Got an idea? Let us know.

Discover how Komodo Digital can turn your concept into reality. Contact us today to explore the possibilities and unleash the potential of your idea.

Get in touch

Sign up to our newsletter

Be the first to hear about our events, industry insights and what’s going on at Komodo. We promise we’ll respect your inbox and only send you stuff we’d actually read ourselves.

Latest articles

Life at Komodo

Komodo Digital Hosts Buzzing FinTech Social in Partnership with FinTech North

A Complete Guide to Creating a Design System That Works in 2024

Web Development

9 Reasons Why React is Still Popular in 2024

Some of our case studies.

A Robust Data-Heavy Platform For Just-In-Time Print Logistics

Building with Nature

Agile software development for cutting-edge lawtech startup.

App Development

Cross-Platform Mobile App for Gathering Clinical Trials Feedback

The Sailboat Retrospective Template

What is the Sailboat retrospective template?

The Sailboat retrospective is a very popular Agile retrospective technique. This original activity will help the team project itself towards a common objective As for any retrospective session, the expected output is to develop an action plan by taking advantage of the knowledge accumulated during previous Sprints. Connoisseurs know that the Sailboat retrospective template is what we call a Futurespective . 🤓

Picture this! Your Agile team has turned into a sailboat crew, navigating the seas towards a paradise island. The island is your team's goal. The wind represents all the things that will help your boat reach the island. The anchor symbolizes things that can slow down the boat on its way. The iceberg, however, illustrates the dangers that could stop your journey in a very abrupt way.

Thanks to its adventurous imagery, the Sailboat retrospective idea is the perfect exercise to launch a new project or simply run a Sprint retrospective . In addition, this fun retrospective format can be handled by both beginners and experts. So wait no more and hoist the mainsail! ⛵

How does the Sailboat retrospective format work?

An easy way to introduce the Sailboat Retrospective template to your Agile team is to explain that each member is now part of a sailboat crew. You can then break the ice by taking 2 or 3 minutes to collectively choose the name of your sailboat! Once this task is completed, present each of the 4 retrospective questions below.

First, discuss your team’s overall goal. If you're starting a new project or Sprint, this could simply be about the delivery of it.

You can also take this opportunity to talk about secondary objectives such as (non-exhaustive list):

Improve the product quality.

Have a better collaboration with other departments.

How to properly involve stakeholders in our decision-making process.

Based on the objectives defined earlier, what actions can greatly contribute to the success of the team? 

Let’s take an example based on what we cover in the previous section: Improve the product quality.

Here are some examples for “The Wind” column:

Work on our test plans to reduce the number of bugs during production deployments.

Review our Code review process and find opportunities for improvement.

Involve designers in the PR review process in order to validate the consistency of our user experience.

Maintain a test environment (‘staging’) up to date and accessible to the entire team.

In an Agile team, we tend to focus on value delivery and want to move quickly (well, very quickly). The anchor will trigger conversations about potential irritants that could harm your team's velocity.

Let’s  keep digging into our objective of improving the quality of the product . Here are some examples for the “Anchor” column:

I often wait several days before someone validates my PRs, what a waste of time.

I'm missing requirements and details in my Jira tasks, which slows down my work considerably.

Our test environment is very slow and doesn’t reflect the feature of our expected product

What should the team pay attention to? These could be gaps in team communication, collaboration issues, or even technical challenges. Identifying these risks at the start of the project is a major asset that will help your team better anticipate issues and establish warning mechanisms.

Still looking for ways to improve our product’s quality ? Here is a list of examples for the “Iceberg” column:

Our technical debt significantly increases the risk of bugs during deployments.

Test plans are not detailed enough, and do not cover the entire user journey.

Our deadlines are too ambitious, leading to early deployments that can harm user experience.

Optional: The Sun column

You can add the Sun section: what could have a positive impact on the team and make you happy - to the Sailboat retrospective idea. The main thing is to take ownership of this exercise and make it the ultimate Agile retrospective template.

Why is the Sailboat retrospective template so effective?

The Sailboat's greatest strength lies in its metaphor. All team members come together as one (the sailboat crew) to develop the best plan towards a common goal.

By removing the notion of the individual, you’ll probably observe increased ease when it comes to proposing new ideas or even discussing potential risks.

This Agile retrospective idea can also serve as a trigger when the team becomes stuck on complex tasks. Each column is designed to guide the team through a set of specific questions.

Finally, with an imaginative and colorful universe, the Sailboat retrospective model strongly differs from old-fashioned retro exercises.

In a nutshell, the Sailboat activity is the ideal retrospective idea to consider when you want to talk about the future as a team.

Icebreaker question examples for the Sailboat retrospective template

When using the Sailboat Retrospective idea, it is quite easy to prepare a list of specific questions to break the ice at the start of the activity. Here are some questions we like to use at Neatro :

What would be your dream island?

What is the name of your boat? What does this name mean to you?

Do you get seasick?

Hotel or hut at the water’s edge?

You can only bring one kind of food in your suitcases, which one?

Do you prefer volleyball on the beach or relaxing reading in the shade?

If you could choose: sailboat or yacht?

Have you ever gone scuba diving? If not, would you consider trying it?

If you had to build a life raft, how would you proceed?

Who has the secret of fire?

Sunscreen factor 20, 40 or tanning oil?

Do not hesitate to check out our guide to the top 100 “icebreaker” questions or the two truths and a like icebreaker to start your retro in an engaging and stimulating way.

Night Train

Create | Connect | Contribute

The Sailboat Exercise

An unconference approach to running productive team retreats.

I thoroughly enjoy planning and facilitating team retreats. When done well, they are a rejuvenating time for team members to reflect on the previous few months, to plan what’s coming next, and to just straight up have some fun together.

As a manager, I’ve found these retreats essential in keeping a team aligned and empowered to take ownership of what they’re building together. Even in Covid times – when the idea of getting together in-person seems quaint – taking time off from "normal work" to connect with your team in a less formal setting can still be quite valuable.

I’ve experimented with different approaches to running these retreats, but one exercise that has become essential is the “Sailboat Exercise”*:

At its core, the Sailboat Exercise is a brainstorming process for garnering honest feedback from employees about the state of the team / product / company. As such, it can be used independently of team retreats. That said, I’ve found it particularly effective in such a setting because it’s a fun, low pressure exercise at a time when folks are in a mindset to candidly assess the state of things — i.e. they’re removed from the stresses of their normal day jobs, and able to come up for air to think more holistically.

In fact, I’ve found it to be such a good exercise for divining the zeitgeist of the team — what’s been good/bad/indifferent and where should we head next? — that I use it to kick off the retreat, with its outcome driving the topics to be discussed during the rest of the event.

In this way, it essentially becomes a tool for running a team retreat as an unconference (i.e. a participant-driven conference), but with enough structure in place to achieve the goals of 1) clear-eyed retrospection, and 2) forward-thinking planning.

For those wanting to try out the Sailboat Exercise, the steps are as follows:

• Draw the sailboat scene on a whiteboard (have some fun with it!), being sure to include the following visual elements: the wind in the boat’s sails, the anchor dragging behind it, the hidden rocks beneath the surface ahead, and the island beyond that.
• Ask the team to write as many ideas as they can possibly think of, 1 per sticky note, for each of the four groups, where:
• Wind = the things that are propelling the team forward (e.g. inherent team strengths, competitive advantages of what you’re building, solid processes, etc.)
• Anchor = the things that are slowing the team down (e.g. gaps in the team, competitive weaknesses, subject areas to invest in, etc.)
• Rocks = the things that aren’t currently being considered at the moment, but are risk points for the team going forward (e.g. areas of tension, bottlenecks around scaling, lurking competition, etc.)
• Island = the things that the team should be aspiring to (e.g. short term objectives, medium term goals, long term mission, etc.)

3. Let the team members independently brainstorm these ideas for 20–30 minutes, encouraging them to not overthink it. At the end of the brainstorming process, have them affix each sticky note to the whiteboard near its appropriate visual element. People are often inclined to avoid affixing a sticky note that duplicates one already on the board, but it’s important to help the group fight that urge since it’s actually quite useful to see which topics were brought up by multiple team members.

4. At this point, the facilitator’s job becomes to organize the stickies on the board so that similar ones are physically connected (see image below). This can be done with the full group’s participation, or with just 1 or 2 others while the rest of the group mingles. Either way, it’s useful for the facilitator to have at least some help in order to group these sticky notes together into thematic topics.

5. Once grouped, the facilitator asks each team member to assign a total of 5 votes to whichever topics that they personally would like the group to discuss while at the retreat. I’ve found that five votes seems to be the right number for most situations, and that the fastest way to enable the voting is to let each person write their own tally marks:

6. The most popular topics become the basis for the set of follow-up sessions during the rest of the retreat. The scheduling of which topics to discuss when can be outlined at this point, or left fluid as the retreat unfolds. As facilitator, your goal is to help the team cover as many of the highest ranked topics as possible while ensuring that the group is energized going into a given session at a particular time. If they don’t seem ready for a discussion because they need a break, some food, a lighter topic, etc. it’s best to delay or forgo the conversation rather than plow ahead.

7. Whenever possible, I look for others on the team to facilitate and/or drive the conversation during a particular session, only speaking up myself when necessary to move the discussion along, or to alleviate any buildup of tension.

8. At the end of our time together, we run a retrospective on the retreat as a whole — what did people like/dislike, and what might we do differently next time. This includes feedback on the Sailboat Exercise itself, as well as the topics that were brought up / discussed. As part of this retrospective, I make sure to thank everyone for their time, energy, and input. I also outline a few actionable steps we’ll be doing as we come out of the retreat because it’s important to a) ensure that team members have felt heard, and b) carry the positive momentum and energy from the event back into the workplace.

That’s it! The Sailboat Exercise has been a crucial tool in my manager tool belt largely because it’s simple to run and consistently produces great results.

I was recently asked by a fellow technologist what advice I had for creating a highly productive team. I said that, amidst a dizzying number of variables, the underlying foundation is almost always that each member of that team feels empowered — to share their opinions, to take on responsibilities, and to be a tangible part of contributing to something larger than themselves. It’s a cliched answer, of course, but as with most cliches, the devil is in the details; accomplishing this goal requires constant nurturing through thoughtful intent, communication, and processes.

In my experience, the Sailboat Exercise has been a great concrete tool for showing, not just telling, team members that they are central to the process of steering the ship.

* Note: I was introduced to this idea by friend and former colleague, Christopher Atkins . He had seen a few folks in the agile community using a version of it for sprint retrospectives, and we decided to experiment with the idea of leveraging it to run our next team retreat. It turned out to be a highly successful experiment, and I’ve since run the process numerous times / adapted it a bit as I’ve learned what works and what doesn’t. It’s worth noting that in doing research for this post, I discovered that the original inspiration for this type of process was a “Speed Boat Exercise” developed by Luke Hohmann .

The mosaic — how to build a healthy team

As many managers know, it’s damn hard to create and cultivate healthy teams.

Management Teams Visualizations Organizational Culture Leadership

Strategy via storytelling

So many strategy artifacts. So little clarity.

Leadership Storytelling Strategy Organizational Culture Product Management

Parkgoer captures alarming encounter between fellow tourist and bear within mere feet of each other: 'Bears are agile climbers'

A tourist visiting Yellowstone ignored the number one rule of bear safety: Don't get too close. 

A woman was caught on video standing in the bed of her truck, mere feet from a black bear, while taking videos of the animal.

The account Tourons Of Yellowstone (@TouronsOfYellowstone) — " touron " being a mix of tourist and moron — posted the video. 

The account emphasized that visitors should always keep at least 100 yards from wildlife unless they are watching from inside their own vehicles.

More viewers were quick to point out that the touron was risking her life. "Can someone break the news to that lady that bears are agile climbers?" one person said. 

Another agreed. "If a bear can climb a tree, I'm pretty sure it can climb into the bed of a truck. And faster than you."

Watch now: Solar-powered boats from the Honnold Foundation are making a difference in the Amazon

It's true: A black bear can climb 100 vertical feet in 30 seconds . But that knowledge didn't stop this person — and it hasn't stopped others. 

Thousands of videos have captured people getting dangerously close to all sorts of animals, from sea turtles to monk seals , elk , and buffalo . While an animal may look docile from several feet away, its defensive instincts could activate at any moment.

Not only are these behaviors dangerous for the humans engaging in them, but they're potentially deadly for the animals as well. There have been several instances of innocent wildlife being euthanized after interacting with humans, even when the humans did so deliberately.

"Approaching wild animals can drastically affect their well-being and … their survival," reports the National Park Service . "The safety of these animals … depends on everyone using good judgment and following these simple rules."

From wildlife rescue groups in major cities to tourism-specific educational groups such as the Honu Guardians in Hawai'i , many organizations are working to curb the negative impact that people have on wildlife. 

Additionally, brushing up on rules and regulations of local wildlife interaction before a trip can significantly improve everyone's experience with nature and ensure both humans and animals can return home safely after crossing paths.

"Being in the bed of that truck will NOT protect you," one person commented.

Join our free newsletter for cool news and cool tips that make it easy to help yourself while helping the planet.

Parkgoer captures alarming encounter between fellow tourist and bear within mere feet of each other: 'Bears are agile climbers' first appeared on The Cool Down .