Two Tips for Better Retros - Add Specificity, Respect Uncertainty
Sep 5, 2023
auto_awesome
Learn two specific ways to enhance retrospective outcomes: specificity and respecting uncertainty. Avoid generic improvement statements and treat outcomes as experiments. Make specific adjustments based on hypotheses and accept and adapt to uncertainty by running experiments, measuring outcomes, and making adjustments accordingly.
Being specific in defining desired changes increases the likelihood of actionable tasks and measurable progress in retros.
Approaching retro outcomes as experiments and respecting uncertainty allows for iterative improvements and ongoing learning.
Deep dives
Be Specific in Retro Outcomes
One key tip for improving the outcomes of retros is to be specific in defining the desired changes. Instead of vague statements like 'We should do something about the noisy alert channel,' it is important to clearly specify what actions should be taken and by whom. Being specific increases the likelihood of turning the outcome into an actionable task that can be executed. It also helps avoid the trap of generic improvement goals, such as 'Do better next time,' which lack specificity and fail to drive meaningful change. By identifying specific actions or processes to implement, teams can effectively address the identified problems and make measurable progress.
Respect Uncertainty and Treat Retro Outcomes as Experiments
Another valuable tip is to approach retro outcomes with a mindset of respecting uncertainty and treating them as experiments. Instead of seeking a definitive fix or solution, retro outcomes should be viewed as hypothesis or adjustments to be tested and evaluated over time. Accepting that uncertainty is inherent in software development, teams can focus on iterative improvements. By formulating specific adjustments as experiments, teams can measure the effectiveness of the changes and make informed decisions about next steps. This approach embraces the reality that retro outcomes are not prescriptive solutions but rather opportunities for ongoing learning and improvement.
Your retros may feel like deadends where complaints go to die. If you're running retros and treating it only as an avenue for emotional support rather than continuous improvement, today's episode is for you.
Retros are for improving iteratively over time. That can only happen if your outcomes are aligned to that iterative mindset. Two simple adjustments can help drive that improvement.
📮 Ask a Question
If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.
If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!
🧡 Leave a Review
If you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode