Broken Car Breakdown Retrospective

Diagnose what's stalling your team and get moving again.

Try this retrospective live

The Engine

What is driving us forward and keeping us moving?

Our daily stand-ups are tight and focused, so everyone knows the plan for the day.
The pairing sessions between dev and QA have caught bugs early. They're a real power source.
Strong product owner support means we rarely get blocked waiting on decisions.
Flat Tires

What is slowing us down or stopping us completely?

Flaky CI builds kept failing randomly and cost us hours of rework.
Too many unplanned interruptions pulled people off their sprint commitments.
We waited days for environment access, which stalled the whole feature.
Warning Lights

What risks or early warning signs should we watch?

Tech debt in the payments module is growing and starting to slow new work.
A key team member is the only one who understands the legacy service, a bus-factor risk.
Customer support tickets have crept up over the last two sprints.
Fuel

What do we need to keep going and recover?

More reviewers trained so approvals don't bottleneck on one person.
Dedicated time each sprint to chip away at tech debt.
Clearer acceptance criteria agreed before work starts.

What is the Broken Car Breakdown retrospective?

The Broken Car Breakdown retrospective treats your team like a car pulled over on the side of the road. Everyone knows what a breakdown feels like, so the metaphor gives the whole team, technical or not, a shared way to talk about what's slowing you down and what you need to get going again. The board has four parts. The Engine is what drives you forward. Flat Tires are the blockers holding you back right now. Warning Lights are the risks that aren't critical yet but could cause a breakdown if you ignore them. Fuel is what the team needs to recover. People add notes to each part, then the team groups them, votes and turns the top items into actions. Use it when work has stalled, when the same problems keep coming back, or when your usual retrospectives have gone stale. Give Warning Lights proper time: it catches the tech debt and single points of failure that a "what went wrong" list tends to miss until they turn into flat tires.

Broken Car Breakdown retrospective format

The Engine

What is driving us forward and keeping us moving?

The Engine is the strengths, processes and people powering your team's progress. Ask what's working and what the team wants to protect. Starting here sets a constructive tone before you get to the problems.

Flat Tires

What is slowing us down or stopping us completely?

Flat Tires are the blockers and friction slowing the team down. Ask people to be specific and keep it about the issue, not the individual. These are the items most likely to become actions.

Warning Lights

What risks or early warning signs should we watch?

Warning Lights are the dashboard alerts: issues that aren't critical yet but could cause a breakdown if ignored. Use this section to raise emerging risks, tech debt and signals the team should keep an eye on.

Fuel

What do we need to keep going and recover?

Fuel is what the team needs to repair and get back on the road, whether that's support, resources or a change in how you work. Turn these into actions with owners so the next sprint runs more smoothly.

When to use this retrospective

  • When your team feels stuck and you want a clear way to find the blockers.
  • When standard retrospectives have gone stale and you want a metaphor that gets people talking.
  • When the same problems keep coming back and you want to find their causes and early warning signs.
  • After a hard sprint or project phase where momentum dropped and the team needs to reset.
  • When new members join and need an easy way to talk about team friction.

Suggested icebreaker questions

  • If your team were a vehicle right now, what would it be: a sports car, a minivan, or a car up on bricks?
  • What's the longest road trip you've ever taken, and what kept you going?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Explain what each part of the car stands for before anyone adds notes.
  • Keep Flat Tires and Warning Lights blameless. Talk about processes and situations, not individuals.
  • Time-box each section so the problems don't take the whole meeting and you still have time for Fuel.
  • Group similar notes before voting so the biggest issues stand out and you don't discuss the same thing twice.
  • Give every Fuel item an owner and a next step, or good intentions never leave the garage.
  • Allow anonymous input so quieter team members can raise what they'd keep to themselves in an open discussion.

Frequently asked questions

How long does a Broken Car Breakdown retrospective take?
Plan for 45–60 minutes for a team of five to eight people. Allow extra time for a larger group or a long list of blockers.
When should I use the Broken Car Breakdown format?
Use it when your team feels stuck, momentum has dropped or the same problems keep appearing. The car metaphor suits sessions about blockers and friction.
How is it different from a standard sprint retrospective?
It frames the conversation around a car: the engine, flat tires, warning lights and fuel. The metaphor makes problems easier to raise, and Warning Lights gets the team talking about risks before they turn into blockers.
What do the four parts of the car represent?
The Engine is what drives you forward, Flat Tires are what slows you down, Warning Lights are emerging risks to watch, and Fuel is what the team needs to recover and keep going.
Can remote and hybrid teams run this retrospective?
Yes. In TeamRetro everyone adds ideas, groups them and votes, live or asynchronously, so a distributed team can run it as easily as a team in one room.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live