Speed Car Retrospective
A racing metaphor everyone gets instantly: what's flooring the accelerator, what's dragging like a parachute, and the cliff up ahead.
Free · No credit card · Guests join by link
The board
01
ENGINE
What is driving us forward?
02
PARACHUTE
What is slowing us down?
03
CLIFF
What risks lie ahead?
The Speed Car retrospective turns the sprint into a racing car heading for a finish line. The engine is everything giving the team momentum, a parachute is strapped to the back dragging you down, and a cliff waits somewhere ahead — the risk that could end the race.
Like other metaphor retros, it depersonalizes criticism: 'the parachute is our flaky test suite' lands very differently from blaming a person. The car framing is especially intuitive for teams who find boats or islands a stretch — everyone understands an engine and a brake.
You may also see it as the Speed Car and Abyss retrospective. That version calls the cliff an abyss and adds a fourth area, the bridge: what would get the team safely across. It's a close cousin of the Speedboat retrospective, which uses a motor and anchors instead.
When to use a Speed Car Retrospective
- Teams that want a fast, energetic metaphor without the nautical framing of Sailboat
- When momentum is the story of the sprint — what's accelerating vs. dragging
- Forward-looking checkpoints: the Cliff column captures future risk, not just past friction
- Delivery-focused teams racing toward a release or milestone
How to run a Speed Car Retrospective
- 1
Set the finish line
Before writing, the facilitator names the goal the car is racing toward — the release, the milestone, the outcome. In Retromik, put it in the board's focus question so it stays visible above every column.
- 2
Start with the engine
Ask people to add engine cards first. It warms up the room and records what the team should protect before the criticism starts.
- 3
Keep parachutes and cliffs apart
A parachute is already slowing you down. A cliff hasn't happened yet. When grouping, move any "cliff" that describes the past into the parachute column.
- 4
Vote where you can act
Spend votes on parachutes the team can cut and cliffs it can see coming, not on things outside its control.
- 5
Give every top card a next step
For a parachute: what will we remove or shrink? For a cliff: what early signal will we watch, and who watches it? For the engine: what keeps it running?
Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.
Example cards
What good cards look like for a software team. Specific, about the work, never about a person.
ENGINE
- Pairing on the payments refactor cut review time in half.
- Every story had acceptance criteria before planning.
- Design joined sprint planning, so fewer surprises mid-sprint.
PARACHUTE
- Flaky end-to-end tests blocked three merges.
- Two days waiting for staging access.
- Ad hoc requests from Sales landed mid-sprint.
CLIFF
- The release date is fixed but the API contract isn't signed off.
- Only one person knows the billing service.
- Half the team is out the last week before launch.
A 45-minute agenda
- 0–5 minSet the finish line
- 5–15 minWrite cards silently in all three areas
- 15–20 minVote, three votes each
- 20–35 minDiscuss the top parachutes and cliffs
- 35–45 minAgree actions: one owner per parachute you'll cut, one early-warning check per cliff
Common mistakes
- The cliff fills up with complaints about last sprint. Those are parachutes; move them.
- Every parachute becomes an action. Pick one or two the team will actually finish.
- Skipping the engine. Without it, the team loses track of what's working.
- A vague finish line ("ship stuff"). The car needs a destination for the cliff to mean anything.
Frequently asked questions
What is a Speed Car retrospective?
A visual retrospective format using a racing-car metaphor: the Engine (what drives the team forward), the Parachute (what slows it down), and the Cliff (risks ahead). It's a car-based cousin of the Sailboat and Speed Boat formats, mapping the team's momentum onto a single shared picture.
How is Speed Car different from Sailboat?
They share the same structure — accelerators, drags, and risks ahead — but swap the metaphor. Speed Car uses an engine, a parachute, and a cliff; Sailboat uses wind, anchors, and rocks. Pick whichever picture your team connects with; some teams find a car more immediate than a boat.
What goes in the Parachute column?
Anything dragging the team down: a slow pipeline, unclear requirements, constant context-switching, a dependency that keeps stalling. Framing it as a parachute strapped to the car makes it easy to name the drag without naming a person.
What's the difference between a parachute and a cliff?
A parachute is something already slowing the team down. A cliff is a risk that hasn't happened yet but could stop the team if nobody acts. Parachutes look back; cliffs look ahead.
How long does a Speed Car retrospective take?
About 45 minutes for a team of 5 to 9. Larger teams should allow an hour, mostly for discussion.
Is the Speed Car template free?
Yes. Retromik is free — create a board with the Speed Car template, set your finish line as the focus question, and share the link. Guests join without an account.
Related templates
Sailboat Retrospective
Wind · Anchors · Rocks
A visual metaphor the whole team gets instantly: what propels us, what drags us, what could sink us.
ViewStarfish Retrospective
More of · Less of · Keep
Calibrate instead of overhaul — dial behaviours up and down rather than starting from zero.
ViewMad, Sad, Glad Retrospective
Mad · Sad · Glad
An emotional check-in that surfaces how the team actually feels — before it becomes attrition.
ViewRun a Speed Car Retrospective with your team
Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.
Start free