Your retro added five action items. Your team had room for one.

Marco van Hout · 4 min read

Retros keep adding work to teams that are already full. A 60-minute format with a capacity check, a stop list and a cap of three action items, plus rules you can check at the next retro.

Most retrospectives end with a list. Five action items, sometimes eight. Two weeks later the next retro opens with that same list, half of it untouched. Someone says the team really needs to follow up this time. Then the team adds four more.

This is rarely a discipline problem. The retro plans as if everyone's calendar were empty. Every action item is new work, and it lands on people who are already full.

Korn Ferry's Workforce 2026 report, a survey of more than 16,000 professionals in 11 countries, puts numbers on how full. 62% say their workload got significantly heavier over the past two years. 45% say they are too busy to deliver meaningful results. 61% are doing the work of more than one role. A retro that hands that team five extra tasks is not a learning meeting. It is a backlog generator.

A retro also has to decide what stops

In Harvard Business Review, Melody Wilding writes about teams that have more work than they can handle. Her advice to managers: involve the team in deciding what can be paused, scaled back or cut, and make the criteria explicit so people can act without asking every time. That is a retro question. The people who did the work know which meetings and reports produced nothing.

So change one rule. Every action item that goes in needs room. Room comes from something that goes out, or from spare hours the team can actually name.

A 60-minute retro that fits the calendar

For a team of 4 to 10 people, every two to six weeks.

  1. 0-5 min. Check the last list. Mark each previous action item done, dropped or open. No discussion yet. Output: three numbers.
  2. 5-12 min. Capacity check. Everyone writes on a card how many hours they can really spare in the next two weeks. Zero is a valid answer. Add the cards up without names. Output: one number for the team.
  3. 12-27 min. What happened. Five minutes of silent writing on what helped and what got in the way, one point per sticky note. Then cluster them together. Output: three to five clusters.
  4. 27-40 min. Stop list. For each cluster, ask what the team does now that it could stop, shrink or hand back. Everyone proposes one candidate. Dot vote, two dots each. Output: one or two stops, each with the date it takes effect.
  5. 40-52 min. Capped start list. Pick action items in order of votes until their estimated hours exceed the hours from the capacity check plus what the stops free up. Output: at most three items, each with an owner, an hour estimate and a first step that takes less than a day.
  6. 52-60 min. Close the old list. Every open item from last time is either dropped on purpose, with one sentence on why, or swapped for an item on the new list. Nothing carries over by default. Output: one list that fits.

Rules you can check at the next retro

  • No more than three action items per retro. If the capacity check came out at zero, one item, and only next to a stop.
  • At least one stop per retro, written down with a start date.
  • The hour estimates of all action items add up to no more than the available hours.
  • At least two of three items are done by the next retro. Below 50% two retros in a row: halve the cap.
  • An item that has been open for two retros is dropped, with the reason in one sentence.

When someone wants to add everything

A good retro produces more ideas than the team can carry. That is fine. Put the rest on a parking list with no owner and no date, visible to everyone. If an idea is still there and still relevant two retros later, it comes back on its own. If nobody misses it, it was never that urgent.

When the stop is not the team's call

Often what should stop is a report or meeting someone else asked for. Do not drop it on your own, and do not leave it off the list either. Turn it into a request: what the team wants to stop, what it costs per month in hours, who decides, and by when. One person takes it to that decision-maker within a week and reports back at the next retro.

The first capped list will look thin. Check the completion rate after two rounds before you judge it.

Where to start

Open Session Studio with your team size and the 60 minutes you have, and ask for a retrospective that includes a capacity check and ends with a stop list next to no more than three action items.

Sources

Design your own session

METODIC turns ideas like these into a complete session agenda with activities, timing, and materials — for workshops, meetings, offsites, and team sessions.

Try METODIC free