RunsheetAgile

Sailboat Retrospective

ComplexityLow

Time45-90 min

Participants4-12

FormatWorkshop

MaturityEstablished

Preparation

What needs to be ready before start

Materials

Whiteboard or Miro board with a pre-drawn sailboat (island = goal, wind = supporting factors, anchors = slowing factors, rocks = risks); stickies; timer; action tracker.

People / roles

One facilitator; 4-12 team members; scribe.

Pre-read

Clear team goal or sprint/project outcome as the island; previous retro actions; known risks from the current pipeline; mood indicator.

Time needed

45-90 min

Setup

Sailboat clearly labeled with four elements. Island on the right with goal statement. Wind above, anchors below the boat, rocks ahead in the water. Rule: each person contributes at least 2 stickies per element.

Core question

The one question this method answers

What moves the team toward the goal, what holds it back, what risks lie ahead, and which actions follow?

Flow

Marker: Phase

Step	Duration	Action	Hint
1Phase 1: Define the island	5-10 min	Formulate the island as a shared goal (one to three clear outcomes). If unclear, do a short clarification; otherwise pause the retro.	Without a clear goal the metaphor loses meaning. The island must be concrete ("MVP launched by 06/30"), not abstract.
2Phase 2: Wind and anchors	15-20 min	Silent work. Each person writes 2-3 wind stickies (what moves us forward) and 2-3 anchor stickies (what holds us back). Make them concrete, with examples.	Wind is more than "good atmosphere". Name what specifically helps: tools, practices, role constellations. Same for anchors: what weighs the team down, and by which mechanism.
3Phase 3: Rocks and risks	10-15 min	What lies ahead of the boat, what could prevent reaching the island? Each person writes 1-3 rock stickies. In an online tool, optionally use a separate symbol for external risks.	Rocks are future-oriented, not historical problems. If people only note the past here, they are repeating phase 2.
4Phase 4: Cluster and vote	10-15 min	Form clusters. Dot-vote (3 dots per person across all elements). Identify top clusters per element.	Anchors and rocks are often most important for actions, wind for "continue deliberately". Keep the balance.
5Phase 5: Actions	15-30 min	Define an action or mitigation for each top cluster. Rocks need a risk plan (mitigation and trigger). Limit to 5 actions, each with owner and date.	Rock actions are often risk reduction, not instant solutions. Formulate triggers ("if X happens, then Y").

Artifact

What comes out at the end

Form

Photo or digital sailboat board with island goal, all stickies in wind/anchors/rocks, top clusters, agreed actions (owner, date, success criterion) and risk mitigations with triggers. Status overview of previous actions.

Versioning / ownership

One entry per retro with date and island goal in the title. Maintain rocks across multiple retros as a risk register, archive wind clusters as success patterns.

Tool alternatives

Miro with sailboat template
FigJam with custom sailboat
Retrium or EasyRetro with sailboat mode
Whiteboard with hand-drawn boat, photo export

sailboat-retrospective-working-template.md

Compact working template for the Sailboat retrospective with winds, anchors, rocks, and next actions.

Sailboat Retrospective Working Template

Goal

Use the sailboat metaphor to surface what moves the team forward and what holds it back.

Context

Which time frame or delivery should the team review?

Input

Time frame:
Team or group:
Notes, signals, or examples:

Working area

Destination island:
Winds:
Anchors:
Rocks:
Patterns:

Output artifacts

Sailboat board:
Risk list:
Improvement actions:

Open questions

Decision / next step

Owner, date, and success signal.

Example output

Concrete filled scenario, fictional example

sailboat-retrospective-beispiel.md

Concrete filled scenario, fictional example

Sailboat — Team Onboarding Initiative, Mid-Quarter Retro (2026-05-20, 70 min, 9 people)

Island: MVP onboarding flow live by 2026-06-30 with measurable activation lift from 22% to 35%.

Wind

Async doc refinement established (4 stickies).
Pairing between frontend and design (3 stickies).
Data pipeline for activation KPI ready (3 stickies).

Anchors

Wait time for compliance review per feature (5 stickies).
Duplicate data-model sources (legacy + new) (4 stickies).
No dedicated test-account system (3 stickies).

Rocks

Summer vacation starts 07/01, who owns maintenance? (4 stickies).
DPA approval for external tool integration pending (3 stickies).
Performance limits in staging DB under realistic data volume (2 stickies).

Actions:

Book weekly compliance review slot in advance (Owner: @anna, from 2026-05-23, success: 5-business-day SLA).
Complete data-model migration in Sprint 25 (Owner: @ben, by 2026-06-12).
Test-account setup spike (Owner: @lisa, by 2026-05-30).
Define vacation plan and maintenance buddy (Owner: @marcus, by 2026-06-06, trigger: if DPA is not ready by 2026-06-15, escalate).
Staging DB load test (Owner: @marcus, by 2026-05-30, success: 100k records, stable p95).

Discussion revolves around wind-and-weather analogies, content gets lost.

What to do

Facilitator keeps the substance visible. The metaphor is a frame, not the goal. Overstretching it weakens the work.

Stop criteria

Done signals checkable in under a minute

Team has no clear goal, island cannot be formulated.

Format is used for the third time in a row, routine sets in, variation is needed.

No future-oriented horizon (for example maintenance team without roadmap), rocks would be speculative.

Team is in acute crisis, format feels too playful, shorter Mad-Sad-Glad or Crisis Retro is a better fit.

Actions from previous retros are not implemented, trust in the format drops.

Group larger than 12, clusters become hard to manage.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods