The Speed Car and Abyss retrospective template combines a look back with a hard look at what comes next. Engine captures momentum from recent work, Parachute shows the drag, Abyss names a credible danger ahead, and Bridge collects the steps that could keep the team on course.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
Which practices, decisions, or conditions gave the team momentum during the period under review?
What slowed the team down, created drag, or consumed effort without moving the work closer to its goal?
Which specific risk ahead could derail the next sprint, release, or milestone if the team leaves it alone?
Which action, decision, or source of support would reduce the leading risk enough for the team to cross it safely?
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint or milestone under review and the next destination. Explain that Engine and Parachute look back, while Abyss and Bridge look ahead.
Give everyone quiet time to add one observation per card. Ask for evidence from recent work in Engine and Parachute, then a concrete future risk and response in Abyss and Bridge.
Share the recent evidence, group cards that describe the same force, and clarify what effect each item had on the work.
Read the risks aloud and sharpen vague cards into credible events. Vote for the risk with the greatest combination of impact and urgency.
Connect Bridge cards to the leading Abyss. Use an Engine strength when it helps, then choose a small preventive step the team can carry out before the risk arrives.
Give the chosen bridge step one owner, a due date, and a signal that will show whether the risk has fallen. Record where the team will review it.
Set the release as the destination. Fill Abyss with readiness and recovery risks, then build each Bridge from a check, rehearsal, decision, or fallback plan.
Run Engine and Parachute after a sprint. Revisit Abyss and Bridge during planning so the chosen response becomes visible work.
Collect Engine, Parachute, and Abyss cards before the meeting. Use the live session to compare risks and design the Bridge together.
Before the retro
It is a retrospective and futurespective built around four parts of a road metaphor. Engine and Parachute examine recent momentum and drag. Abyss and Bridge surface a future risk and the response that could reduce it.
The four columns are Engine, Parachute, Abyss, and Bridge. They cover momentum, drag, danger ahead, and the actions or support that could help the team cross safely.
Add a specific, credible risk that could derail the next sprint, release, or milestone. A missing rollback plan, concentrated operational knowledge, or an unconfirmed dependency gives the team something concrete to assess.
Both formats explore momentum, drag, and risk. Speed Car and Abyss puts extra weight on connecting one serious danger to a preventive Bridge, while Sailboat also asks the team to define its shared destination.
Plan for 45–50 minutes with four to twelve people. The team needs enough time to review recent forces, compare future risks, and give one preventive action a clear owner.
Open the four ready-made areas, compare the forces on the team, and build one owned bridge across the biggest risk ahead.
