The speedboat retro is the most action-focused metaphor retro. Two elements: what drives the team forward and what drags it back. Every anchor is an impediment with a clear owner. Snap it and ship the fixes.
Use the speedboat retro when the team has a specific goal in sight and needs to remove the impediments standing between them and it. It's more focused than the sailboat retro — there are only two elements, which makes the session faster and the action items cleaner.
The speedboat is particularly effective when a team is in a sprint crunch or building toward a launch. The urgency of the speedboat metaphor matches the urgency of the moment.
Draw the boat in the center of the board. The speedboat represents the team — fast, goal-directed, capable. Write the sprint or release goal on or near the boat. This visual anchors the whole session: everything you discuss is in service of getting this boat to the destination faster.
What's powering the team? Good decisions, strong collaboration, technical clarity, customer feedback loops, great tooling, clear ownership. Draw engines or motor lines behind the boat. Name each one specifically — engines you can name are engines you can protect and amplify.
What's holding the team back? Unclear requirements, slow approvals, technical debt, missing access, cross-team dependencies, communication gaps. Draw anchors hanging below the boat, each labeled with the specific impediment. The weight of the anchor is the severity — draw bigger anchors for bigger impediments.
Draw a finish line or flag on the right side of the board representing the goal. Adding this element makes the stakes explicit and gives the anchors a sense of urgency: each anchor is the difference between reaching the goal and falling short.
Draw the speedboat. Write the sprint or product goal on it or next to it. Add a finish line if it helps the team feel the urgency.
Everyone writes engine and anchor stickies. Encourage at least two anchors per person — impediment identification is where the session's value lies.
Post and read the anchor stickies aloud. Cluster related anchors. For each cluster, size the anchor based on severity: how much is this slowing the team down on a 1–5 scale? Use the scale to prioritize which anchors to cut first.
Post and read the engine stickies. Name the specific practices and conditions the team wants to protect and amplify. These become the Continue column of the implied action plan.
For each top-severity anchor: who owns cutting it? What's the specific action? By when? Write the action next to the anchor. An anchor without an action plan is just a complaint.
Snap the board with BoardSnap. The AI reads the engine and anchor stickies, the severity scores, and the action plans — and outputs a structured impediment list with owners and deadlines.
The speedboat retro is about velocity. Digital tools slow the session down with load times, permission requests, and template navigation. A physical whiteboard is instant — draw the boat, start writing stickies, move fast. The format matches the metaphor.
BoardSnap captures the urgency intact. The anchor stickies, the severity scores, the action plan written next to each anchor — all of it reads as a structured impediment register with clear ownership. The session output becomes the daily standup agenda: 'which anchors got cut this week?'
The speedboat retro has two elements (engines and anchors). The sailboat retro has four (wind, anchors, rocks, island). The speedboat is faster and more focused — better for teams with limited time or a very specific impediment-removal goal. The sailboat adds risk identification (rocks) and a visual goal (island), which makes it better for broader strategic retrospectives.
Two to three. More than three and the team spreads its attention too thin. Pick the highest-severity anchors that the team can actually cut — some anchors are organizational or external and require escalation rather than team-level action. Focus the retro's action items on what the team can move themselves.
Name the escalation path. If an anchor is a slow approval process from another team, the action is: 'PM escalates to VP of Engineering by Friday.' The team can't cut every anchor themselves — but they can ensure the right person knows the anchor exists and how much it's costing the sprint.
Yes — it's one of the shorter retro formats. With a focused team and a clear sprint goal, 30 minutes is enough for the write, post, and action-planning steps. This makes it particularly useful for teams in crunch mode who can't afford a 60-minute retro but need the impediment-clearing conversation.
No exporting, no transcription. Snap the board, get the action plan.