Rate of Improvement Retrospective

See where your team's effort actually paid off.

Try this retrospective live

Highest ROI

In which areas did we have the highest ROI?

Our new code review process made deployments noticeably faster.
Pairing on that complex feature paid off, and we delivered it ahead of schedule.
The training workshop taught us skills that helped us refactor that legacy system much faster.
Lowest ROI

In which areas did we have the lowest ROI?

We spent too much time debating architecture without a clear decision framework.
Constant context switching between projects really slowed our momentum.
Lack of clear requirements led to rework that diminished our overall progress.
Potential ROI

Where can we improve our ROI?

If we automate more tests, we can get faster feedback and spend less time manually verifying changes.
More collaborative workshops could help us solve problems faster as a team.
Dedicating more time to knowledge sharing will spread expertise so we're not relying on one or two people.

What is the Rate of Improvement retrospective?

The Rate of Improvement (ROI) retrospective asks where your team's effort has produced the most progress, and where it hasn't. The name plays on return on investment: instead of money, you're weighing how much improvement the team got back for the time and energy it put in. The board has three columns. Highest ROI is for the areas where effort paid off quickly, like an automated test suite that cut bug-fix time or a planning format that made delivery more predictable. Lowest ROI covers the effort that didn't move things forward, such as long architecture debates with no decision or constant context switching. Potential ROI looks ahead to where a change would pay off next. Because the format asks people to compare returns, it works best with evidence: cycle time, throughput, escaped defects or anything else your team already tracks. Use it when progress feels slow, after a big project, or as a periodic check alongside your usual retrospectives, and finish by turning the most promising Potential ROI ideas into actions with an owner.

Rate of Improvement retrospective format

Highest ROI

In which areas did we have the highest ROI?

Look at where the team made the most progress for the effort it put in over the last period. Ask for specific examples and, where possible, numbers to back them up. Understanding what made these efforts work tells you what to do more of.

Lowest ROI

In which areas did we have the lowest ROI?

Find the areas where effort didn't turn into real progress. Ask why: was it the wrong problem, the wrong approach or something outside the team's control? Naming these bottlenecks is the first step to deciding whether to fix them or stop spending time on them.

Potential ROI

Where can we improve our ROI?

Look ahead to where the team could get more improvement for its effort. Welcome bold ideas, but ask what evidence suggests each one would pay off. Turn the most promising into actions with an owner and a date.

When to use this retrospective

  • When the team feels its progress has stalled or slowed in some areas
  • After a major project or initiative, to see which efforts paid off
  • Every few months, alongside your usual retros, to check where improvement effort is going
  • When a change in strategy or priorities means the team should rethink where it spends its improvement time

Suggested icebreaker questions

  • If our team were a vehicle, what would it be and why?
  • What's one new skill you've picked up recently that made your work faster?

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

Ideas and tips for your retrospective meeting

  • Bring metrics like cycle time, throughput and escaped defects so claims of high or low ROI rest on evidence
  • Don't confuse high effort with low ROI; some hard problems need more investment before they pay off
  • Make it safe to admit that an effort didn't work, or the Lowest ROI column will stay empty
  • Turn the best Potential ROI ideas into action items with an owner
  • Use it alongside formats that look at process, teamwork or technical practice, not as a replacement

Frequently asked questions

What is a Rate of Improvement retrospective?
It's a three-column retrospective where your team looks at where improvement effort had the highest return, where it had the lowest, and where it could pay off next. The aim is to put more effort into the changes that work.
Does ROI mean return on investment in this retrospective?
Here ROI stands for Rate of Improvement: how much progress the team got for the effort it put in. It borrows the idea of a return, but there's no financial calculation involved.
How do you run a Rate of Improvement retrospective?
Share any relevant metrics first, then have everyone add notes privately to the three columns. Discuss the highest and lowest returns, vote on the Potential ROI ideas and turn the top one or two into actions.
When should I use a Rate of Improvement retrospective?
Use it when progress feels stalled, after a major project, every few months as a check on where improvement effort goes, or when a change in strategy means the team should rethink its priorities.
Do we need metrics to run it?
No, but they help. Even a few numbers, like cycle time or bug-fix time, stop the discussion from becoming a contest of opinions.

Related templates

Four Ls Retrospective

Reflect on what your team Liked, Learned, Lacked and Longed for

What? So What? Now What? Retrospective

Go from what happened to what you'll do next.

Agile Retrospective

Four questions to review your last sprint and plan changes.

Start Stop Retrospective

Two questions: what to start, and what to stop

Ready to run this retrospective?Try this retrospective live