Speedboat retro
Definition
A retrospective format where the team imagines their work as a speedboat and identifies anchors — impediments, friction points, and blockers — then votes on which to cut to move faster.
The speedboat retro is a focused variant of the sailboat metaphor. While the sailboat retro covers wind, anchors, rocks, and the island, the speedboat retro zooms in on a single question: what is slowing us down, and which slowdowns are most worth fixing?
Structure: The facilitator draws a speedboat on the whiteboard — sometimes with an engine labeled with the team's goal or ideal velocity. Participants write anchors on sticky notes and post them below the waterline. The team then dot-votes on the anchors causing the most pain. Top-voted anchors become action items for the next sprint.
Why anchors only: The single-zone constraint forces specificity. Teams that run start / stop / continue sometimes spend too much time celebrating wins and not enough time diagnosing friction. The speedboat format deliberately removes the positive column — wins are assumed; impediments are the focus.
When to use it: Mid-project health checks, velocity post-mortems, or any retro where the team already knows something is wrong and needs to name it cleanly. Pairs well with a root cause analysis session if the top-voted anchor is systemic.
Facilitator tip: After voting, ask the team to estimate how much speed each anchor is costing. This converts emotional complaints into rough prioritization data.
Snap the speedboat whiteboard with BoardSnap — the AI identifies and ranks the anchor items by vote count and generates action items for the top three.
Examples
- Anchor: waiting on legal review slows every release by a week. Anchor: the test environment is broken 30% of the time. Anchor: no clear owner for API documentation.
- A team running at below-average velocity uses the speedboat retro to surface the three biggest process blockers in 20 minutes.
- An engineering manager shares the BoardSnap summary of the speedboat retro with the VP of Engineering as evidence for hiring a dedicated DevOps role.
- A startup uses the speedboat retro monthly to keep the impediment backlog visible and prioritized.
Snap a speedboat retro. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.