In this post I refer to retrospectives as a type of meeting inspired by the 12th agile principle “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”.
Many factors–specific to your context–can reduce the effectiveness of a retrospective and cause frustration and mistrust in the group. In this brief blog post I will describe how psychological safety, purpose, preparedness and collaboration can help make your retrospectives even more effective.
I want to highlight this is not a checklist. And depending on what system/subsystem your retrospective is working with you might need to switch between lens/approaches for complicated or complex domains. I’ll probably followup on that in a separate post.
This post is for retrospective facilitators and regular team members that want to take on that role. You don’t need to be a trained facilitator, scrum master or product manager to introduce changes and make your retrospective even more effective.
Amy Edmondson has done extensive research since the 90s on the subject–and published a book in 2018–The Fearless Organization–Norm Kerth talks about a “Create Safety” exercise in his seminal Project retrospectives book published in 1999.
Have you ever felt your retrospective is a blame game more than a reflection? Let me start from the foundation. Your retrospective outcomes will always be subpar if your team or organization does not support psychological safety.
If people are punished when speaking up they will withhold information or play the blame game fostering a low energy retrospective. Improving psychological safety at the organizational level is outside the purpose of this post but there are strategies you can use to assess and improve psychological safety at the team level.
Assess the team psychological safety
Start by collecting data on the psychological safety level of the group. Try to have one-on-ones with team members before the retrospective and take notes about their feelings. Try to run an anonymous activity (like Explorer, Shopper, Vacationer, Prisoner or Elephant in the room) when you set the stage of your retrospective to anonymously collect the safety levels.
If the the psychological safety level is low–say a room full of Prisoners in ESVP–you should switch the focus of the retrospective to increase the safety level. Try to run an anonymous brainstorm on “what is one thing that would have to change to make you all not be prisoners?”. It’s possible that the outcome of the whole retrospective will be a team norm document to ensure people feel comfortable to speak up… and that’s great! If you decide to continue with the original retrospective plan–despite a room full of disengaged folks–remind the group they will have a chance at the end of retro to provide feedback to make the next one safer.
Establish a safe space with the Retrospective Prime Directive
There are a multitude of activities to set a safe stage for your retrospective, one is to read “The prime directive” by Norm Kerth:
“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”
For some groups printing the directive, reading it and asking for a verbal “yes I believe it”–or alternatively “I believe for the duration/sake of this retrospective”–is sufficient to set a safe positive stage. In more dis-engaged groups some will say yes just to move on… but they truly believe someone messed up… they truly believe it’s someone’s fault. At times their fault. What do you believe as the facilitator? If you–the retrospective facilitator–doubt the directive then it’s nonsensical to ask for a group agreement on it. You can read an article I wrote that dissects the prime directive and better understand its roots. There is also a retrospective activity to challenge the retrospective prime directive with the group so instead of just a verbal yes you’d have a conversation about it.
The prime directive is similar to bounded rationality and when embraced allows the group to shift from looking for a culprit to collaboratively looking at the context and generate insights.
The retrospective purpose
If people don’t know why they’re in a retrospective and what they will get out of it they will be disengaged.
Have you ever felt your retro is more like a happy hour then a reflection? Very often teams go through the motions and always run retrospective to “reflect on what could be improved from the last iteration”. For a 3 or 4 people team and smaller challenges that could work for a little while but I’ve seen that purpose lead to premature convergence. I’ve seen retros where people would discuss for the same amount of time items like “someone left a glass on the desk and there is now mold in it” and “we should refactor the reservation class based on the application’s bounded contexts”.
I think spending 2 minutes discussing an item is not reflection. The problem I see is that people only share information during retrospective so you end up with a lot of those smaller items. I call whack-a-mole retrospective when the team generates lots of mad/sad/glad items and try to fix all the sad with rushed action items. The outcomes I’ve seen are too many action items–carrying over from one iteration to the next–and people never getting to them.
There are at least a couple of options.
Agree on a real time agenda
Check if the group is ok to try a retrospective with a real time agenda (aka lean coffee). This helps because once the topics are listed the group can create clusters with a silent mapping activity, run a poll to prioritise what to talk about first. In this format the group decides if they want to keep talking about a topic of move on.
A critical piece–where the facilitator or an action item taker can help–is to acknowledge when a discussion ie. “we should refactor the reservation class based on the application’s bounded contexts” will not fit in the allocated timebox and agree to have a separate meeting dedicated to that topic. You must be clear about the purpose of the followup meeting. Is it to share information? Advance the thinking? Provide input? Make decisions? Improve communication? These goals are from Sam Kaner’s “Facilitator’s guide to participatory decision making” another great resource about having clear meeting is “Where the action is”.
Pick a retrospective topic
Another approach would be to focus the retrospective on a topic agreed with the team before the meeting–but that assume there was some preparation. When we focus the retrospective someone in the group might still want to talk about off-topic items. If people feel strongly about sharing something with the group let them do it. I think a better strategy is to run daily 10 minutes retrospectives–for teams of 4 or 5–so the team has space to share information during the week and focus on overarching issues during the iteration retrospective.
A retrospective is a meeting and to run a good meeting you need a clear purpose and some preparation. Your plan might not survive contact with the team–and their evershifting context–so it’s ok to improvise at that point. The facilitator should not go in and improvise activities by default or come in unprepared.
Going in to retrospective without a clue of what happened during the iteration should be an exception.
In small (5/6 people teams) I like to prevent that by taking one-on-one time with the group before retrospective to see what’s on their mind and prepare a retrospective plan that fits where they are at this time. For larger teams you can collect information with the help of co-facilitators.
I once was in a retrospective where the facilitator was trying to explain Jean Tabaka’s Sailboat activity while reading it on the phone. The group was pretty confused. When I pick up a new activity I write down a little script to explain the activity purpose and what the individuals are expected to do. If it involves drawing I practice it beforehand.
I think too often people focus on the retrospective activity rather than on the framework.
Know your retrospective framework instead of activities
A framework gives structure to your retrospective and a clear start and end. I base my retrospectives plans on Derby/Larsen’s 5 steps framework and I pick activities that fit the group’s journey. I’ll briefly describe the 5 steps and you can look up other options like ORID by The institute of cultural affairsor Adaptive Action by Human system dynamics.
- Set the stage purpose: the group understands the goal of the retrospective, the room has psychological safety, roles are assigned, team norms acknowledged
- Gather data purpose: ensures the group is on the same page about what happened about the topic we’re focused on or the timespawn we’re looking at. The outcome should be a snapshot of all perspectives about what happened and hopefully mutual understanding. If the group doesn’t reach mutual understanding I’d spend more time until you get there. Reading “Facilitator’s guide to participatory decision-making” can give strategies to bring a group to mutual understanding.
- Generate insights purpose: the group finds focus on a topic with affinity mapping, polling, prioritization to allow the team to go past the immediate solutioning and have a deeper conversation about no more than 1/2 topics. The outcome should be a set of ideas to formalise into an experiment for change.
- Decide what to do purpose: the group comes up with a specific, measurable and time bound experiment (aka action item) or acknowledging if the topic is too broad and the time left during retrospective is not sufficient to come up with a detailed plan. If so schedule a followup meeting with its purpose and its desired outcome.
- Close out purpose: the group acknowledges what was achieved in the meeting and is clear about next steps and responsibilities. Now is a good time to end on a high note with a round of appreciation. To speed up time in larger groups you can try having folks share appreciations via post-it notes or Jurgen Appelo’s Kudos cards
This is a great time to run a quick retro on your retrospective, I use a +ΔROTI. ROTI came from Esther Derby and it’s a Return Of Time Invested activity where you collect between 0 to 4 how well spent the time was. I ask the group to write the number on a post it note, and add a short sentence next to a Δ sign for the one improvement that would have made their ROTI go up by 1, and a short sentence next to a + for something they liked about today’s retro - 0: complete waste of time, I learned nothing - 1: mostly a waste of time but I learned one thing - 2: broke even, satisfactory retrospective - 3: better then an average, I learned quite a few things - 4: awesome, best retrospective of my life
If you’d like to learn more about the framework read Derby/Larsen’s book about “Agile Retrospectives”. If you want to learn the origin of the 5 steps framework you can listen to my interview with Diana Larsen on my Retrospective facilitation podcast here.
As the facilitator you’re not alone. If the retrospective is in a safe environment and there is a purpose and you are prepared the group should be there to help.
If you’re trying to juggle time keeping, note taking and action item collection while facilitating you can ask for volunteers for those tasks! That way there is a shared ownership of the process.
If you are the facilitator but also a team member–scrum master/product manager/lead/whatever–you have a hard job to keep your biases under control. I know I do as the team product manager–and previously principal engineer–I had very strong opinions on team topics we talked in retrospective I was facilitating. When I had something that I felt was critical for the group to hear I would say: “I am taking my facilitator hat off and as a PM I think…”. I usually try to keep it to a brief sentence to give more colour and then go back to my facilitator role unless more context is required. It might be good to have a backup facilitator if you feel your stakes are too high and you might not be an impartial facilitator.
You can ensure there is collaboration by having silent activities. For example instead of having an open discussion–where introverts and less loud people would be having a harder time contributing–use an activity like 1-2-4-all. Its purpose, having individuals brainstorm–ideas or topic–alone, then in pairs, then 4 then with the whole group. There are a multitude of activities out there, Liberating Structures or Retromat are good repositories.
Remember the facilitator skills:
- Encourage full participation
- Promote mutual understanding
- Foster inclusive solutions
- Cultivate shared responsibility
In order for a retrospective to become more effective your organization and team should foster psychological safety, as the facilitator try to prepare and define a clear retrospective purpose to ensure the group stays engaged and takes on targeted action items. Ultimately a retrospective requires collaboration and the facilitator (you?) is there to make sure the ride goes smoothly.
If you want to tackle organizational issues remember the team is part of a system. Look up Larsen/Shore’s agile fluency maturity model and Snowden’s Cynefin sense making framework for seeing issues and contexts from different lenses.
There are a lot of resources out there if you’re interested in the topic of reflection, retrospectives and facilitation. Here’s a few links:
- Derby/Larsen Agile retrospectives book
- Kua’s The Retrospective Handbook: A guide for agile teams
- Kaner’s Facilitator’s Guide to Participatory Decision-Making
- Retrium’s video guide to retrospectives by David Horowitz
- Retrospectives Podcast
What challenges do you face in your retrospectives? What are the part of this post that you won’t be able to use? Why?