Never surface feedback for the first time in a retro.
The moment a criticism lands in public, ego activates and the retro turns into a defense session. One change to the format fixes it.
The failure mode of most retros is predictable.
Someone raises a pain point. The person it’s about hears it — publicly, for the first time. Ego activates. They get defensive. The room splits. And the retro, which was supposed to be a place to get better, becomes a place to survive.
The problem isn’t the feedback. It’s the timing.
When someone hears hard feedback for the first time in front of the whole team, they can’t process it — they can only manage it. The public setting triggers a threat response. They stop being problem-solvers and start being self-protectors. The conversation goes nowhere useful.
My fix: decouple hearing from discussing.
Before the retro, anyone who has an improvement point about another person does a quick 1:1 with them first — in private. They share the feedback directly. The good and the bad. Then they loop me in to confirm the alignment happened.
By the time the retro starts, there are no surprises. The point is already on the table — it just hasn’t been publicly discussed yet. The person receiving it already knows it’s coming, already has some context, maybe already has a response. Their ego is intact. The conversation can go straight to the pain and how to fix it.
The retro stops being a venue for revealing things. It becomes a venue for solving things.
I’ve been running this format for about six months. The quality shift is consistent: retros that used to stall in cross-team blame finish with actual agreements. The format itself didn’t change — lean coffee, same as before. The pre-alignment step changed everything.
There’s a useful side effect for me as the EM: the “confirm with me” step means I always know what’s coming into the retro before it starts. No ambushes. No moments where I’m reading the room trying to figure out what just happened.
One small process step. One significant change in what the retro actually produces.
Do you run retros where feedback lands publicly for the first time? What does that moment look like for your team?