Stop, Start, Continue: Mastering the Art of the Retrospective
In the world of delivery, if you aren't moving forward, you’re falling behind. Whether you are a "retro virgin" or an old hand, the retrospective is the single easiest technique to bring into your workflow to add immediate value.
Based on Barry Trish’s "Knowledge Blitz," here are the top insights and actionable tips to transform your retrospectives from a dry meeting into a powerhouse for growth.
1. Structure is Your Best Friend
Don't just wing it. A great retro follows a logical flow. Barry recommends Esther Derby’s Five-Stage Model to ensure you don’t just vent, but actually improve:
Set the Stage: Get people out of "doing" mode and into "thinking" mode.
Gather Data: Use facts, not just feelings. What actually happened?
Generate Insights: Analyze that data. Why did things happen the way they did?
Decide What to Do: Pick your experiments.
Close the Retro: Reflect on the session and celebrate your wins.
2. The Golden Rule: Data Over Opinion
"My data beats your opinion every time." Personal experiences are subjective, so bring evidence to the table. Use charts, plans, or recent artifacts to focus the team on reality. This expands everyone's view from their personal silo to the team's collective experience.
3. Facilitation: Be the Guide, Not the Player
It is incredibly difficult to facilitate and participate at the same time.
Stay Neutral: If you are facilitating, try to stay out of the contribution.
Bring in a Guest: If you want to get stuck in, ask a guest facilitator from another team to step in. They’ll bring a fresh perspective.
Avoid Groupthink: Make space for the quieter voices. Use "silent" techniques like 1-2-4-All or quick check-ins to give everyone permission to speak.
4. Psychological Safety is Non-Negotiable
You won't get honest feedback if people are afraid.
The Prime Directive: Start by reminding everyone: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could." It’s about the system, not the individual.
Privacy Matters: Keep the "busy-bodies" and observers out. You need a safe space for awkward conversations.
Demonstrate Vulnerability: If you’re the leader, lead by example. Admit your own hurdles.
5. Action Over Agitation
A retro that is just a "whinge-fest" is a waste of time. To make a real impact:
Limit your actions: Choose a maximum of three key things to fix. If you have 20 actions, you’ll achieve zero.
Drive Accountability: Put these actions on your Jira board or wherever your team tracks work.
Focus on Culture: Don’t just change the process; change the mindset.
Pro-Tips for Keeping it Fresh
Change the Scenery: Get out of the office, go to a different building, or even just stand up. Physical movement breaks down rigid thinking.
"Rubber Ducking": If someone is stuck, have them explain the problem to you as if you know nothing. Often, the act of explaining reveals the solution.
Retro the Retro: Not getting value? Run a retro on the retrospective itself. Ask a checkout question: "How could this session have been better?"
Recommended Reading
If you want to dive deeper, these are the "bibles" of the practice:
Agile Retrospectives (2nd Ed) by Esther Derby.
The Facilitator’s Guide to Participatory Decision-Making by Sam Kaner.
Final Thought: Improvement occurs best when it is small and often. Don't wait for a project to end to learn your lessons—by then, it’s too late to change the outcome.How is your team’s "growth mindset" looking lately? If you've been skipping your retros, there’s no better time to restart than today.
