Every two weeks, teams gather to perform a ritual. Someone opens the board. Three columns appear: what went well, what didn't, action items. Everyone says something polite. The action items are written down. Nobody ever looks at them again.
The sprint retrospective isn't a practice anymore. It's theater. And we all know it.
I'm not against reflection — I'm against the performance of reflection. There's a difference, and most teams are doing the second one. The evidence is everywhere: the same complaints sprint after sprint, the action items that age like milk in the backlog, the facilitator asking "anyone else?" into silence while everyone stares at their cameras.
Why did this happen? A few reasons, and none of them are anyone's fault, exactly.
First: psychological safety became a slogan instead of a practice. Every company says they want honest feedback. But the retro happens in front of the same manager who does performance reviews, and everyone in the room can do that math. So people share the safe complaints — "too many meetings," "unclear requirements" — and keep the real ones — "our tech lead doesn't listen," "this deadline was fantasy" — for the group chat. The retro gets the press-release version of the truth.
Second: the action items have no teeth. "Improve communication" is not an action item; it's a wish. Real action items have an owner, a deadline, and a way to verify they happened. Most retro action items have none of these, because assigning them would require someone to actually change something, and changing things is uncomfortable. So the board fills up with good intentions and the team learns, correctly, that nothing said in a retro matters.
Third: the cadence is wrong. Two weeks is simultaneously too often and too rare. Too often for anything meaningful to have changed — you're just re-litigating the same sprint. Too rare for the things that actually need reflection, which are usually specific moments: the deploy that went sideways, the decision made in a hurry, the week the team worked nights. By the time the retro rolls around, the moment has cooled and the learning has evaporated.
So what does honest reflection actually look like? In my experience, it's smaller, more specific, and less comfortable.
It looks like a fifteen-minute conversation right after something happens, not a scheduled ceremony two weeks later. "That deploy was rough. What did we miss?" — while everyone still remembers.
It looks like the manager going first. Not "what could the team do better" but "here's what I got wrong." The fastest way to make a retro honest is for the person with the most power in the room to demonstrate that honesty doesn't get punished. Everything else is decoration.
It looks like fewer, harder action items. One thing, with a name attached and a date. If you can't name who's doing it and when it's due, it's not an action item — it's a feeling.
And sometimes it looks like admitting the format isn't working and trying something else. A written retro. A one-on-one. A "what should we stop doing" session with no "start doing" allowed. The format is not sacred. The honesty is.
I'm not saying kill the retrospective. I'm saying kill the ritual — the empty performance of a practice that used to mean something. The teams that reflect honestly don't need a template. The teams with a template usually aren't reflecting.
The retro is dead. Long live actually talking to each other.