The Climbs

What were the toughest uphill challenges we faced?

Migrating the legacy database felt like a never-ending mountain pass.
Onboarding two new team members mid-sprint stretched our capacity.
The shifting requirements made it hard to find a steady rhythm.
The Descents

Where did we gain momentum and things flowed easily?

Our new CI pipeline let releases fly through with no manual steps.
Pair programming helped us cruise through the tricky API work.
Daily standups were short, sharp and kept us moving fast.
The Punctures

What slowed us down or caused us to stop unexpectedly?

Flaky tests kept failing the build and stalling deployments.
Unplanned support escalations pulled us off course repeatedly.
A key dependency wasn't ready, forcing us to wait.
The Yellow Jersey

Who or what deserves recognition this stage?

Huge thanks to Priya for leading the breakaway on the payment feature.
The whole QA crew earned the jersey for catching critical bugs early.
Sam's calm under pressure during the outage kept us all going.

What is the Tour de France Challenge Retrospective?

The Tour de France Challenge Retrospective looks at your last sprint or project as a stage of the race. Some stretches were hard climbs, some were fast descents, and somewhere along the way you probably got a puncture. The board has four columns. The Climbs are the toughest challenges the team ground through. The Descents are where momentum picked up and work flowed. The Punctures are the unexpected breakdowns that stopped you, and The Yellow Jersey, named after the jersey the race leader wears, goes to the people and moments that deserve recognition. Separating the climbs from the punctures is the useful part. A climb is work that was always going to be hard, while a puncture is something that shouldn't have happened, like flaky tests or a dependency that wasn't ready. Treating them differently helps you decide which problems need an action and which deserve credit for the effort. It's a good fit when your team is tired of the usual format, or while the real race is on each summer.

Tour de France Challenge retrospective format

The Climbs

What were the toughest uphill challenges we faced?

The Climbs are the steep, demanding stretches: the work that took extra effort or persistence. Treat them as challenges the team got through, not failures, and ask what made each one so hard.

The Descents

Where did we gain momentum and things flowed easily?

The Descents are where the team picked up speed and things went smoothly. Celebrate what worked and ask what made it work, so you can repeat it on the next stage.

The Punctures

What slowed us down or caused us to stop unexpectedly?

Punctures are the unexpected breakdowns that brought progress to a halt, such as blockers, interruptions or recurring issues. Dig into the root cause of each one so the team can fix it before the next ride.

The Yellow Jersey

Who or what deserves recognition this stage?

The Yellow Jersey goes to the standout riders and moments of the stage. Invite kudos for individuals, collaborations and achievements, and make sure recognition comes from across the team.

When to use this retrospective

  • When your team needs a change from its usual retrospective to beat retro fatigue.
  • After a demanding sprint or project with both big wins and tough challenges to talk through.
  • When you want recognition and team spirit to get time alongside honest talk about blockers.
  • During themed sessions, such as while the real Tour de France is on.

Suggested icebreaker questions

  • If your week were a Tour de France stage, would it be a flat sprint, a brutal mountain climb, or a relaxing recovery ride?
  • What's one thing that would have made your ride smoother this sprint: a better bike, a stronger team, or a clearer route?

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

Ideas and tips for your retrospective meeting

  • Explain each cycling metaphor at the start so everyone knows what belongs in each column.
  • Use cycling language through the session to keep the theme going.
  • Timebox each stage so the team doesn't spend the whole session on The Climbs.
  • Keep The Punctures on root causes and fixes, not on who caused them.
  • Give everyone a chance to award a Yellow Jersey so recognition doesn't come only from the loudest voices.
  • Turn the biggest climbs and punctures into actions with an owner so the next stage goes more smoothly.

Frequently asked questions

How long does a Tour de France Challenge retrospective take?
A typical session runs 45–60 minutes for a team of five to eight people. That's enough time to brainstorm across all four columns, group ideas, vote and agree on actions.
When should I use this retrospective format?
It works best after a demanding sprint or project with a mix of big wins and tough challenges, or when your team is tired of its usual retrospective format.
How is it different from a standard sprint retrospective?
It covers the usual ground (what went well, what slowed you down and who deserves credit) inside a cycling race metaphor. Splitting hard work (climbs) from breakdowns (punctures) gives the team a clearer picture than a single what-went-wrong column.
Do team members need to know about cycling to take part?
No. The facilitator explains each metaphor at the start, and climbs, descents, punctures and the yellow jersey are easy to map to everyday work.
Can I run this retrospective with a remote or distributed team?
Yes. In TeamRetro everyone adds ideas independently, live or asynchronously, so distributed teams can take part as easily as people in the same room.
Ready to run this retrospective?Try this retrospective live