BoardSnap is an iOS app that reads speedboat retrospective whiteboards and turns the engines-and-anchors format into a crisp team review with velocity drivers and drag removers as structured action items.
The speedboat retrospective is faster and more action-focused than the sailboat format. Two zones: engines (what's making us faster) and anchors (what's slowing us down). The anchor weight is often estimated in story points lost or hours wasted — which makes it uniquely actionable.
The anchors are the entire point. Removing drag is how you accelerate without adding resources. But capturing anchor weight estimates from a whiteboard requires reading the annotations, the numbers, the relative sizes — not just the sticky note text.
BoardSnap reads all of it.
Boat with a motor/engine area and a chain dropping to anchors below. Simple sketch. Label: Engines = what accelerates us, Anchors = what slows us down.
What's working? What gives the team velocity? Start positive — it sets a productive tone before moving to anchors.
What's dragging? Process overhead, unclear requirements, tech debt, tooling friction. One anchor per sticky note.
Optional but powerful: next to each anchor, write how many points or hours per sprint it costs. This turns anchors into quantified drag items — much easier to prioritize for removal.
Vote on the heaviest anchors. The top two or three become the sprint's improvement commitments.
BoardSnap reads engines, anchors, weights, and votes. Anchors with estimated costs become quantified action items — 'Remove X, estimated +N points/sprint.'
A two-section retrospective document: Engines (velocity drivers to sustain and amplify) and Anchors (drag items with estimated costs and removal action items). Top-voted anchors become immediate action items. Engine items become team commitments. Where anchor costs were estimated, they appear in the action item description.
Six anchors with estimated point costs ranging from two to eight points per sprint. BoardSnap's summary showed the team that their top three anchors were costing approximately fifteen points per sprint — the number that convinced leadership to approve two sprints of tech debt work.
A four-person startup team used the speedboat format to diagnose why they were shipping slower than expected. The anchor 'founder decision bottleneck' cost eight hours per sprint. BoardSnap's output framed it as a process change request, not a personal accusation.
The speedboat format (engines + anchors) is more stripped-down and action-focused. The sailboat format adds risks (rocks) and a vision (island). Speedboat is better when you want to move fast through the retro and focus entirely on velocity. Sailboat is better for strategic retrospectives where risk visibility matters.
Story points work well for engineering teams. For other teams, use whatever unit makes drag tangible: hours per week, delayed deliverables, customer complaints. The unit matters less than the act of estimating — it forces specificity and makes prioritization objective.
Use ranges. '2–5 points' is better than no estimate. BoardSnap captures ranges as written. The discussion about why there's a range is often the most valuable part of the exercise.
Once per sprint is fine if velocity is a persistent concern. For stable teams, once per quarter is enough to surface new drag. The format is designed to be fast — under thirty minutes with a crisp facilitator.
Snap the board, ship the action items in ten seconds.