Retrospectives running out of steam: 7 signs, and how to revive them
Same topics, same voices, sessions that overrun: seven signs a retro is going through the motions, and what gets it moving again.
Blog4 min read
No retrospective runs out of steam all at once. It wears down, session after session, until the day someone suggests “skipping it just this once, we’re swamped”. On that day, the problem isn’t the workload: it is that the team no longer sees what the retro gives it.
Here are seven signs a retro is going through the motions, and for each one, what gets it moving again.
1. The same topics come back every session
“Too many meetings” for the fifth time. It isn’t a lack of ideas, it is an admission: the action items decided on that topic changed nothing, or weren’t done.
What helps: devote a whole session to that one topic, and come out of it with a smaller action item that actually gets done. Then check, at the next session, that it was. The details are in why retro action items never get done.
2. It is always the same people talking
Three people run the session, the others nod along. It isn’t necessarily shyness: in an open discussion, those who think before they speak arrive after the topic has been settled.
What helps: a period of silent writing where everyone writes their cards without seeing anyone else’s, then a vote. Everyone’s voice is then on the board before anyone has spoken, and it is the votes, not the loudest voices, that decide what gets discussed.
3. Nobody dares say what is wrong
The cards are polite, the problems are “minor”, and the real topics get discussed at the coffee machine. Psychological safety is missing: speaking up seems riskier than staying quiet.
What helps: run a session anonymously, for everyone. Remind people at the opening that you are examining practices, not people. And ask yourself whether a manager’s presence in the session has something to do with it.
4. The session always overruns
Planned for one hour, it lasts an hour and a half, and the last half hour, the one for action items, happens standing up and in a hurry. The team takes away that the end of the retro is optional.
What helps: time each step, with a timer everyone can see, and protect the time for action items by putting it out of reach of the discussions. Better to discuss two topics and come out with two action items than to skim over six.
5. The cards write themselves
“Good atmosphere”, “Good communication”. After months of the same format, the team answers the columns on autopilot.
What helps: change format. A Speedboat makes the team look forward, a Mad / Sad / Glad gets people talking about feelings, the 4Ls about lessons learned. See six retrospective formats and when to pick each one.
6. It is always the same person facilitating
The facilitator ends up with their own habits, questions and pace, and the session becomes predictable. If they are also the manager, the retro becomes their meeting rather than the team’s.
What helps: rotate facilitation. Everyone learns to run a session, and a change of facilitator is often enough to refresh the tone.
7. The retro only talks about what is going wrong
Session after session, the retrospective becomes the list of problems. It is exhausting, and it is inaccurate: what works also deserves to be named, if only to be preserved.
What helps: a format that makes explicit room for recognition, such as Kudos & Kaizen, and an opening that starts with what the team is proud of.
What they have in common
In almost all of these cases, the problem isn’t the team’s goodwill but the frame of the session: who speaks, in what order, for how long, and what is left of it afterwards. That frame is what the facilitator holds, and what the guide to running an agile retrospective covers step by step.
It is also SquadRetro’s approach: a facilitator who moves the phases along, cards hidden during the brainstorm, a vote that decides the order of discussion, anonymity as a session setting, six ready-to-use formats, and the option to hand over facilitation without restarting the session.