Sailboat Template
Reflect as a team on project goals, blockers, and future ambitions.
Trusted by 65M+ users and leading companies
About the Sailboat Retrospective Template
The Sailboat Retrospective (also known as the Sailboat Agile Exercise) is a low-pressure way for teams to reflect on how they handled a project. Originally based on the Speedboat retrospective by Luke Hohmann, the exercise centers around a sailboat as a metaphor for the overall project, with various elements broken down:
Rocks - represent risks and potential blockers
Anchors - represent issues slowing down the team
Wind - what helped the team move forward, represents the team’s strengths
Sun - what went well, what made the team feel good
By reflecting on and defining these areas, you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint.
When to use a Sailboat Retrospective Template?
If you are part of an Agile team, you know retrospectives are fundamental to improving your sprint efficiency and getting the best out of your team. The Sailboat Retrospective Template helps you organize this Agile ritual with a sailboat metaphor. Everyone describes where they want to go together by figuring out what slows them down and helps them reach their future goals.
Use this template at the end of your sprint to assess what went well and could have been done better.
Benefits of the Sailboat Retrospective Template
When facilitating your team’s retrospective, this template is an easy way for everyone to jot down ideas in a structured manner. The metaphor of a sailboat gliding over water can help team members think about their work as it relates to the overall course of the project, and the ready-made template makes it easy to fill in and add stickies with ideas and feedback.
To run a successful sailboat retrospective meeting, use Meeting mode to lead your team through each frame, set a timer for each section of the template, and control what participants can do on the board.
Create your own sailboat retrospective
Running your own sailboat retrospective is easy, and Miro’s collaborative workspace is the perfect canvas on which to perform the exercise. Get started by selecting the Sailboat Retrospective Template, then take the following steps to make one of your own.
Introduce the sailboat metaphor to your team. For some teammates, this may be the first time they’ve heard the analogy. Explain the four components, and feel free to frame them as questions (for example, “what helps us work to move forward?”, “what held us back?”, “what risks do you see in our future?”, “what made us feel good?”). Then, tie the visual metaphor back to how to run an Agile sprint. Like a sailboat, a sprint also has factors that slow it down, and risks in the face of a goal, target, or purpose to reach.
Ask each team member to write and reflect individually. Give everyone 10 minutes to create their own sticky notes. Ask them to record their thoughts and reflections relevant to each area of the retrospective. Use Miro’s Countdown Timer to keep things on track.
Present your reflections in pairs or small groups. Spend five minutes each taking turns to dig deeper into the insights recorded on each sticky note.
Choose one team member to group similarly-worded insights together. That team member can spot patterns and relationships between the group’s insights. Accordingly, the team can get a sense of which area had the biggest potential impact on the project.
Vote as a team on what the critical issues are to focus on mitigating and developing. Use the Voting Plugin for Miro to decide what’s worth focusing time and effort on. Each person gets up to 10 votes and can allocate multiple votes to a single issue.
Diagnose issues and develop outcomes. Discuss as a team what your follow-up action plans are for maintaining or building on helpful behavior and resolving issues in preparation for future sprints. Add another frame to your board by clicking Add frame on the left menu bar and annotate your team’s insights and next steps.
Dive even deeper into how to make your own sailboat retrospective – and see examples – in our expert guide to making your own sailboat retrospective.
How do you conduct a sailboat retro?
When conducting a sailboat retro, make a space for you and your team to uncover valuable insights, some of which might not be shareable across your organization. For that reason, make sure to adjust your privacy board settings so that only you and your team can access it, and let them know this is a safe space to share ideas and feedback honestly. The Sailboat Retrospective Template is built for you to run your meeting session smoothly, having complete control of how participants can add to the board. Start explaining the concept of the sailboat retro methodology. If they don’t know it already, guide them through your meeting agenda and set the timer for each section. After the meeting, gather insights in another frame on the same board, and thank everyone for contributing to your retro.
The 4-Step Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The 4-step retrospective board is intended to quickly add a simple retrospective template for your retro sessions.
OKR Drafting Board
Works best for:
Agile
The OKR Drafting Board (New) is a visual tool for defining and tracking Objectives and Key Results (OKRs). It provides a structured framework for setting ambitious goals, defining measurable outcomes, and aligning teams around shared objectives. This template enables organizations to articulate their strategic priorities, track progress transparently, and foster accountability and alignment across teams. By promoting focus, alignment, and agility, the OKR Drafting Board empowers organizations to achieve breakthrough results and drive continuous improvement.
FMEA Analysis Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
When you’re building a business or running a team, risk comes with the territory. You can’t eliminate it. But you CAN identify it and mitigate it, to up your odds of success. Failure Modes and Effects Analysis (FMEA) is a powerful tool designed to help you manage risk and potential problems by spotting them within a process, product, or system. And you’ll spot them earlier in your process—to let you sidestep costly changes that arise late in the game or, worse, after they’ve impacted your customers and their experience.
Features Prioritization Tool
Works best for:
Agile
The Features Prioritization Tool offers a systematic approach to prioritizing product features based on criteria such as value, effort, and strategic alignment. It provides a structured framework for capturing, evaluating, and ranking feature ideas, enabling teams to make informed decisions about what to build next. With customizable scoring mechanisms and visual dashboards, this template empowers product teams to optimize their product roadmap and deliver maximum value to customers, driving competitiveness and market success.
Parking Lot Matrix Template
Works best for:
Project Management, Ideation, Meetings
When the creative energy is flowing, a workshop or meeting will yield a lot of new ideas — but not all are on-topic or currently feasible. Roll them right onto a parking lot matrix, a simple, effective tool for separating the best ideas from those that are promising but could use more research or discussion. This template will let you easily make your own parking lot matrix, which will come in especially handy during long meetings (and when you have teammates who tend to go off-topic).
User Story Map Template
Works best for:
Marketing, Desk Research, Mapping
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.