Reflection Before Retro

How many retros have you sat through that changed anything?

Most retros are theater. Everyone shares. Someone takes notes. The doc gets filed. Nothing changes. But you have the power to make retros matter.

The problem isn't the format. It's the timing. Reflection requires space. When you go straight from "ship" to "retro," people are still in execution mode. They haven't had time to process. They give surface-level answers. "Communication could be better." "We should have more meetings." The real insights, the ones that could actually change behavior, stay buried. Imagine the breakthroughs you unlock when you create space for reflection.

Research on learning from failure shows that psychological safety is a prerequisite. People won't share what went wrong if they fear blame. But safety alone isn't enough. You need structure. You need prompts that go deeper. "What did we assume that turned out to be wrong?" "What would we do differently if we started today?" "What did we learn that we didn't expect?" You can create that structure.

The best retros start before the retro. Give people time to reflect. Send the questions in advance. Let them write. Let them think. Then when you meet, you're not starting from zero. You're building on reflection. Your team deserves that depth.

And close the loop. The retro isn't done when the meeting ends. It's done when the changes are implemented. One or two actions. Clear owners. Follow-up. If the retro doesn't produce action, it was a waste of time. You have the power to make every retro count.

Your next retro: send the questions early. Create space for reflection. Then make sure something actually changes. You have everything you need. Take the lead today.