Guide only · On the RetroRally roadmap
Sailboat Retrospective retrospective template
A visual format that connects a shared destination with tailwinds, anchors, and delivery risks.
A practical RetroRally guide · Updated August 2026
When to use Sailboat Retrospective
Teams aligning around a milestone, product goal, or complicated delivery period.
When not to use it
The team needs a very short check-in or has no shared outcome to use as the destination.
Suggested timing
45–60 minutes. Reduce the number of themes before shortening private writing or action design.
Preparation
- Define the island or destination in one sentence.
- Create areas for wind, anchors, rocks, and optional treasure.
- Bring the relevant sprint goal or outcome metric.
Exact prompts
- What moved us toward the goal?
- What anchored or slowed us?
- Which rocks could hurt the next sprint?
- What valuable capability did we discover?
Step-by-step facilitation
- Name the destination — 5 min. Confirm the shared outcome before collecting observations so the metaphor stays grounded.
- Map the journey — 10 min. Participants write wind, anchor, rock, and treasure notes privately.
- Build the map — 10 min. Reveal notes, group related signals, and ask neutral clarifying questions.
- Choose the obstacle — 8 min. Vote for the anchor or rock with the highest impact on the destination.
- Plan the manoeuvre — 12 min. Define one mitigation or experiment, an owner, and the evidence the team will inspect.
Example answers
- Wind: shared acceptance examples shortened review cycles.
- Anchor: flaky staging data delayed every test.
- Rock: a vendor deadline lands midway through the next sprint.
Remote and hybrid adaptations
- Share the destination before the session.
- Use clear text labels as well as icons for accessibility.
- Zoom into one category at a time on small screens.
Common mistakes
- Spending more time drawing the boat than discussing work.
- Mixing the goal with the actions.
- Treating every future risk as the team’s responsibility.
Turn the discussion into action
Connect the action directly to the destination: ‘To reduce the staging-data anchor, Jules will publish a reset script by Wednesday and we will measure failed test setup time.’
Review the action at the start of the next retrospective. Mark it complete, partially complete, or blocked, then use the evidence to decide whether to keep, change, or stop the experiment.
Explore related resources
Compare every retrospective template, browse questions by team situation, or learn how to run the complete meeting.