Running a retro your team doesn't dread

A retrospective — a regular look back at how a piece of work went — is one of the highest-value meetings a team can run. It’s also one of the easiest to let rot into a box-ticking exercise where people list the same frustrations and nothing changes.

Keep it small and specific

Retro the last project, sprint, or month — a bounded thing people can actually remember. “How’s everything going in general” produces vague answers. “How did the client launch go” produces useful ones.

Three questions is enough

• What went well? Start here, genuinely. It sets the tone and surfaces things worth keeping.
• What was harder than it should have been? Not “what went wrong” — that invites blame. “Harder than it should have been” points at process.
• What will we change before the next one? The only part that matters.

Land on one or two changes, with owners

A retro that generates fifteen ideas changes nothing. Pick one or two, assign each to a person, and put them at the top of the next retro’s agenda: “last time we said we’d do this — did we?” That single accountability loop is what separates a retro that improves a team from one that just vents.

Make it safe

If people get in trouble for what they say in a retro, the honest ones stop talking and you’re left with a meeting that tells you nothing. The facilitator’s job is to keep it focused on process, redirect blame, and go first with their own mistakes.

Rotate the facilitator

The same person running every retro makes it their meeting. Passing it around keeps it the team’s.