Want To Get Participation In Your Retrospectives? Torpedo The Sprint

Even the most creative, engaging retrospective can fall flat if a team slips into complacency. Sometimes, no matter how fun or interactive you make the session, people become so comfortable that they stop seeing the need for improvement. The result? Retrospectives become a routine, with little to no real feedback or actionable ideas.

Complacency usually sets in when a team feels that things are “good enough” and can’t imagine how they could improve. Over time, this mindset leads to retrospectives filled with dead air. You can try every trick and facilitation tool in the book, but if the team believes there’s nothing left to improve, no one speaks up.

It’s easy to misinterpret this silence as a sign that everything’s perfect. However, it often serves as a warning sign that the team is coasting and missing opportunities for growth.

Here’s how it played out for one team: The Scrum Master had to take time off just as a sprint was about to start. Before leaving, they helped the team prep, review tickets, and estimate everything in advance. On paper, the team was ready—everyone knew what to expect and had a plan.

But when the sprint began, things felt “off.” Work was moving, throughput was high, but there was an underlying tension—like the calm before a storm. No one raised concerns, and no one addressed the strange vibe. The team assumed everything would sort itself out.

When the Scrum Master returned, they noticed the lack of engagement and scheduled one-on-one chats with each team member. Using clean language questions, they uncovered the real issue: previous successes had made the team overconfident. Each person had ideas for improvement, but they assumed someone else would bring them up, or that changes would just happen naturally.

In reality, the sprint suffered. The team didn’t complete everything they committed to, and the lack of open communication had quietly torpedoed their momentum.

At the next retrospective, participation was back. The team openly discussed what happened, shared their perspectives, and identified what needed to change. They realized that celebrating wins is essential, but so is staying vigilant for opportunities for improvement—even when things seem to be going well.

The Scrum Master thanked everyone for their honesty and highlighted the positives that emerged from the one-on-one conversations. He reminded the team that retrospectives aren’t just about fixing problems—they’re also about acknowledging what’s working and building on it.

After that, the team’s energy shifted. Communication flowed more freely, complacency faded, and the next sprint had a renewed sense of purpose.

Getting people to discuss improvement can be challenging, especially when things are going smoothly. But that’s exactly when you need to dig deeper. Don’t wait for a crisis—proactively use one-on-ones, ask the right questions, and stay vigilant for signs of complacency.

Tools like Clean Language can help uncover hidden issues, but the key is to tailor your approach to your team’s unique dynamics.

When you sense that “calm before the storm,” don’t ignore it, lean in, ask questions, and help your team evolve—before complacency torpedoes your progress.

Let’s discuss practical ways to energize your retrospectives, break through complacency, and foster a culture of continuous growth. Reach out at jberriault@berriaultandassociates.com, and let’s keep your team moving forward—together.