Making Retrospectives Effective with Small Concrete Actions and Rotating Facilitators
#DevOps

Making Retrospectives Effective with Small Concrete Actions and Rotating Facilitators

DevOps Reporter
4 min read

Natan Žabkar Nordberg shares practical strategies for running retrospectives that drive real improvement: focus on 1-2 concrete weekly actions, rotate facilitators to build ownership, and frame bigger changes as 4-6 week experiments with clear voting outcomes.

Making retrospectives effective requires more than just gathering the team in a room to discuss what went wrong. Natan Žabkar Nordberg, speaking at QCon London, shared practical strategies that transform retrospectives from complaint sessions into engines of continuous improvement.

The Problem with Traditional Retrospectives

Many teams fall into a common trap: retrospectives become venting sessions where frustrations are aired but nothing changes. As Žabkar Nordberg explained, "If you do not complete actions, retrospectives can turn into a negative spiral, where all we do is complain about our situation, and nothing improves."

This creates an echo chamber of complaints that erodes team morale and trust in the process. The solution isn't to eliminate venting entirely—occasional emotional release is healthy—but to prevent it from becoming the default pattern.

Focus on Small, Concrete Actions

The cornerstone of effective retrospectives is focusing on 1-2 concrete weekly actions. Žabkar Nordberg emphasized that smaller, continuous improvement helps more in the long term than the occasional grand gesture.

This approach works because:

  • Small actions are more likely to be completed
  • Weekly progress builds momentum
  • Team members see tangible results
  • The process becomes self-reinforcing

When teams consistently complete small improvements, retrospectives shift from complaint sessions to planning meetings for positive change.

Rotate Facilitators to Build Ownership

Another key insight is rotating retrospective facilitators. While it might seem easier to have one person always lead, Žabkar Nordberg argued this approach builds ownership and engagement across the team.

"It is challenging to fairly represent one's own ideas and opinions while facilitating the retrospective, as every person brings their own unique perspective," he noted. Different facilitators naturally highlight different discussion topics and bring fresh energy to the process.

For team members interested in developing meeting facilitation skills, retrospectives provide a perfect starting point. They're similar and well-defined, allowing new facilitators to inject their own ideas while following a proven structure.

The Experiment Framework for Bigger Changes

One of the most innovative aspects of Žabkar Nordberg's approach addresses a common retrospective challenge: agreeing on actions for fundamental changes in ways of working. When people have strong preferences, reaching consensus can be difficult or impossible.

His solution is to frame bigger changes as 4-6 week experiments. This timeframe is short enough that the whole team can commit to trying something new, regardless of their initial stance, yet long enough to see real impact.

The critical element is what happens after the experiment period ends. Teams hold a retrospective specifically to vote on one of three options:

  1. Keep the change
  2. Keep the change but tweak it
  3. Revert the change and return to previous methods

If agreement cannot be reached, the default is to revert the change. This ensures that no one feels changes are being forced upon them and maintains the experimental nature of the process.

Practical Implementation Tips

For teams ready to implement these strategies, Žabkar Nordberg offered several practical suggestions:

  • Start with one or two small actions per retrospective
  • Ensure completion before the next meeting
  • Rotate facilitators regularly, giving everyone a chance to lead
  • For recurring issues, choose retrospective formats that fit the problem
  • When bringing an agenda as facilitator, listen to the team rather than pushing predetermined solutions

The Cultural Foundation

Underlying these practical techniques is a deeper understanding of team culture. As Žabkar Nordberg explained in earlier work, people thrive in different environments—some need autonomy, others structure. Trust must be given first, not earned. Leaders should guide rather than control, fostering autonomy and safety.

A "session 0" can help set expectations and ensure everyone approaches the team in a compatible way. This foundational work makes the retrospective techniques more effective because they operate within a culture of psychological safety and mutual respect.

Getting Started

For teams not currently doing retrospectives, Žabkar Nordberg's advice is simple: start now. "It really is one of the easiest ways to continuously improve your work environment and culture."

The beauty of these techniques is their accessibility. Any team can begin focusing on small actions, rotating facilitators, or running experiments without special training or tools. The key is consistency and commitment to the process.

By implementing these strategies, teams can transform retrospectives from dreaded meetings into powerful tools for continuous improvement, building a culture where everyone feels heard and progress happens week after week.

Comments

Loading comments...