Every team has one: the handover that never quite works, the estimates nobody believes, the deploy process everyone sighs about. It gets raised, discussed with real energy, sometimes even agreed on — and then, four or six weeks later, it is back on the table looking freshly discovered.
The instinct is to blame the problem for being hard, or the team for being undisciplined. Both diagnoses are usually wrong, and both lead nowhere. What actually keeps a problem alive is simpler and more fixable.
Why do recurring problems feel new every time?
Because meetings have no memory. Each discussion starts from a blank page, so the issue arrives with no history attached — no record that it was raised in March, half-solved in April, and quietly abandoned in May. Without that history, the group does the only thing it can do: it discusses the problem from scratch, with the same sympathy and the same twenty minutes it gave it last time.
The people in the room half-know this is happening. That is where the sighing comes from. But half-knowing is not the same as seeing it written down, and nothing changes until it is written down.
What does discussing a problem actually cost?
More than it looks. Twenty minutes, six people, once a month — that is two full working days a year spent on a single conversation that never concludes. Most teams carry three or four of these. The real cost is worse than the hours, though: every re-discussion teaches the team that raising things changes nothing, and that lesson generalises.
A team that has watched the same problem survive five discussions stops raising new ones. Not in protest — just quietly, the way people stop putting suggestions into a box that is never opened.
How do you make a recurring problem visible?
Count it. Keep one running page for the group with two columns: what we agreed, and what came up again. When an issue is raised, check the page before discussing it. If it has been raised before, say so out loud, with the number: “this is the fourth time since March.”
That sentence changes the conversation completely. “Our handover is messy” invites another twenty minutes of shared complaint. “This is the fourth session in a row we have discussed handover” invites a decision — because being counted turns a topic into a pattern, and groups respond to patterns differently than they respond to topics.
What are the only three honest ways forward?
Once a problem has been named as recurring, the group has exactly three honest options:
- Fix it properly — with a named owner, a date, and a check next session. Not “we should improve this,” but “Maya rewrites the handover checklist by the 14th and we look at it together on the 15th.”
- Accept it explicitly — decide, out loud, that this is a cost of how the team works and it is not going to change. That sounds like defeat; it is actually relief. An accepted problem stops consuming twenty minutes a month.
- Escalate it — because some recurring problems recur precisely because they cannot be fixed at this table. Naming that is progress; re-discussing it is not.
The one dishonest option is the default one: discuss it warmly, agree vaguely, and put it back in the drawer for next month. A group that can see the count stops choosing that option, because the count makes the choice embarrassing.
Who should keep the score?
Someone without a side. This is the awkward part: the natural scorekeeper is the team lead, and the team lead is usually part of at least one recurring problem. When the person holding the record also has a stake in what the record shows, entries soften. “Raised for the fourth time” becomes “ongoing discussion.”
If a neutral human is available — a rotating scribe, a facilitator from another team — use them. The rotation matters less than the neutrality. The record only works if everyone trusts that it counts everything, including the things the scorekeeper would rather not count.
Common questions
Isn't re-discussing a problem sometimes useful?
Re-discussing with the history on the table is useful — you are adding to an investigation. Re-discussing from scratch is not; you are repeating one. The difference is whether anything carries forward.
What if the recurring problem really is unfixable?
Then say so explicitly and stop discussing it. An accepted constraint costs nothing at the next meeting. An unacknowledged one costs twenty minutes a month forever.
We keep a retro board already — why doesn't it help?
Boards record what was said in one session. Recurrence lives between sessions, so it needs a record that spans them and someone who reads the old entries before the new discussion starts.
How do you raise the count without blaming anyone?
State it as arithmetic, not accusation: “fourth time since March” is a fact about the group, not about a person. That is also why it works best coming from someone — or something — with no side.
I'm building Facilitable, a facilitator for groups that meet regularly. It keeps the running record across sessions and says the “fourth time since March” line so nobody on the team has to. It isn't ready yet. If you'd like to see it when it is: