How to Run a Retrospective That Actually Sparks Change
Retrospectives are one of Agile’s most powerful practices, but many teams treat them as a checklist item. When run well, they become a space for innovation and growth. When run poorly, they drain energy and lead to disengagement.
Signs of ineffective retrospectives:
- The same issues come up every sprint
- Action items are vague or ignored
- Discussions feel flat or repetitive
How to spark real change:
- Frame retrospectives around outcomes, not just complaints. We all need to vent from time-to-time, but I always ensure that my teams understand that we’re not there to complain without also committing to some sort of action to fix the problem area.
- Ensure that the team leaves with at least one action item that is clear, measurable, and owned. This often gets skipped and teams end up frustrated with the retrospective process because they don’t get to realize the value.
- Vary the format to keep energy and creativity high. Just like snowflakes, no two retrospectives should be the same. Okay – maybe that’s a bit extreme. However, I find that switching it up helps people think about the things they want to improve differently. Plus, it’s more fun to do something different each time!
Executives can help by giving teams the space to reflect and backing up the time needed to follow through on identified improvements. A culture of continuous improvement must be supported, not rushed.
Want to see how I run retrospectives? Reach out and I’d be happy to show you!
