Sprint Retrospective Guide: Sailboat Format (Remote, 60 Minutes)

This guide covers a 60-minute Zoom retrospective for your 7-person product team, split between Chicago and Lisbon. The session has three goals: refresh a format that has gone stale, hear from everyone (especially quieter voices), and leave with no more than 2 actions the team will actually finish. The recommended format is the Sailboat exercise on Miro, combined with silent writing and dot-voting. Sailboat suits your team because its visual metaphor (wind, anchors, rocks, island) breaks the Start/Stop/Continue habit, and silent sticky-note writing lets everyone contribute equally before anyone speaks.

Assumptions: You're reviewing your most recent sprint. The meeting is scheduled within the Chicago–Lisbon overlap window (the cities are usually about 6 hours apart, so a Chicago morning means a Lisbon late afternoon). You can find last retro's 6 action items. Everyone can access the Miro board.

Before the Meeting

• Send the invite (Slack and calendar):

  "Hi all! Our sprint retro is on [date/time CT / time Lisbon] on Zoom. We're trying a new format this time (no Start/Stop/Continue, promise), and we'll keep it to 60 minutes with just 1–2 actions we'll really commit to. Board link: [Miro link]. Feel free to add sticky notes early if something's on your mind."

• Set up the Miro board with these frames:
  • Last Retro's Actions: paste all 6 items, with three columns: Done / Still Matters / Let It Go
  • Sailboat: draw a boat with four labeled zones:
    • Wind: What pushed us forward
    • Anchors: What slowed us down
    • Rocks: Risks we see ahead
    • Island: Where we want to be
  • Themes (empty space for clustering)
  • Actions (a table with columns: Action | Owner | Due | How we'll know it's done)
  • Parking Lot
  • Feedback: a 1–5 scale for "Was this retro worth our time?"
• Give each person a sticky-note color (or keep notes anonymous if you prefer; see "Handling Tricky Moments").
• Review last retro's 6 actions yourself first, and note any you already know the status of.
• Pick a timekeeper. Ask a volunteer (not you) to watch the clock, or use Miro's timer so everyone can see it.
• Have the Prime Directive ready to paste into Zoom chat.

Timed Agenda

Facilitator Script

1. Set the Stage (5 min)

Say:

"Thanks, everyone, especially our Lisbon folks, since this is the end of your day. I'll be honest: our retros have gotten a bit repetitive, so today we're trying something different. It's called the Sailboat. Before we dive in, quick check-in: in one word, how did this sprint feel?"

After the check-in, paste and read the Prime Directive:

"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."

Then explain the format:

"Our boat is the team. The wind is what pushed us forward. Anchors are what slowed us down. Rocks are risks ahead. The island is where we want to be. One more thing: today we'll leave with at most two actions, not six."

Check-in prompt options:

• "One word for this sprint?"
• "If this sprint were weather, what would it be?"

Timebox tip: Go round-robin by Zoom grid order or alphabetical. Don't let check-in become discussion, and say "We'll dig in shortly" if it starts.

2. Review Previous Actions (7 min)

Say:

"Last time we made six action items and, honestly, we didn't finish any. That's not on any one person. It tells us something about how we set actions. Let's quickly sort them: Done, Still Matters, or Let It Go."

Prompts:

• "Is this one still a real problem, or has it faded?"
• "What got in the way of these actions: time, unclear ownership, or too many at once?"
• "If we could keep just one of these six, which would it be?"
• "Did we ever check on these between retros?"

Timebox tip: Spend about 45 seconds per item. Anything in "Still Matters" becomes a candidate sticky in the Sailboat; don't solve it here. Capture the "why they stalled" answers, because they feed directly into the Decide segment.

3. Gather Data: Sailboat (15 min)

Say:

"For the next 7 minutes, silently add sticky notes to any part of the boat. One idea per sticky. No talking yet. I want everyone's thoughts on the board before anyone's voice shapes them. I'll add mine last."

Prompts (paste into Zoom chat while people write):

• "What made it easier or harder to hand work between design, development, and QA this sprint?"
• "Where did work wait or bounce back, and why?"
• "What's something we keep saying in retros but haven't changed? Put it on an anchor."
• "What risk could sink us next sprint if we ignore it?"
• "What would 'great' look like for us a few sprints from now? That's the island."

After