Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches Episode: How Upper Management Can Destroy a High-Performing Team in Minutes | Somya Mehra Host: Vasco Duarte Guest: Somya Mehra Release Date: August 12, 2025

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in a candid conversation with Somya Mehra, an experienced Scrum Master, about the fragile dynamics between upper management and high-performing Agile teams. Titled "How Upper Management Can Destroy a High-Performing Team in Minutes," the episode delves deep into the subtle yet destructive behaviors that can erode team trust and efficiency overnight.

Somya’s Inspiring Journey

Somya begins by sharing her foundational inspiration: the book Agile Retrospectives: Making Good Teams Great by Diana Larsen and Esther Derby. She emphasizes the book's impact on her approach to retrospectives, highlighting its practical frameworks and adaptability beyond traditional Scrum practices.

Somya Mehra [01:36]: "It's not about the format but telling you how to make an effective retro for your team... you can use it anywhere throughout your profession and personal and any part of your life."

The High-Performing Team Before the Incident

Somya recounts her experience working in a startup focused on developing exam evaluation software for universities. Despite being a non-traditional Scrum team, they exhibited strong collaboration, timely deliveries, and effective backlog refinements. The team comprised relatively young developers under a tech lead who was not a part of their immediate team structure.

Somya Mehra [05:05]: "Everything was running on time, and the team was delivering as expected."

The Catalyst: Upper Management’s Intervention

The harmony within the team was disrupted when upper management, including the CEO, expressed concerns over perceived padding in the team's story point estimates. This accusation was communicated to the tech lead and the Scrum Master, setting the stage for conflict.

Vasco Duarte [06:50]: "When you say they started challenging, did they come to a retrospective or did they just make a comment to the team lead?"

The Confrontation and Its Aftermath

During the critical meeting with upper management present, the tech lead unilaterally blamed the developers for inaccurate estimates without seeking their perspective or understanding the context behind the numbers. This public shaming led to a swift breakdown of trust within the team.

Somya Mehra [08:34]: "He just threw the whole devs under the bus. Totally devs."

The CEO's reaction further compounded the issue, undermining the team's credibility and fostering an environment of distrust and fear.

Somya Mehra [08:36]: "Now the team feels like, okay, you can't trust your tech lead... you've lost all your reputation in front of the CEO."

Consequences of Leadership Failure

The incident led to several team members contemplating leaving their roles to protect their professional integrity and mental well-being. Somya reflects on the pivotal role of leadership in either nurturing or dismantling team dynamics.

Somya Mehra [10:05]: "It's the leadership who destroys the team sometimes... you feel helpless and then the team is just gone because you did not show the true leadership when the time was needed."

Lessons Learned: Embracing Servant Leadership

Somya shares crucial lessons from this experience:

1. Empathy in Leadership: Understanding and respecting the unique capacities of each team member is paramount.

   Somya Mehra [11:32]: "If I think like I can do this work in one day, I won't say like the others can do it in one day. It can take five days for them."

2. Advocacy as a Scrum Master: The Scrum Master should defend the team’s integrity and facilitate transparent, constructive dialogues with upper management.

   Somya Mehra [12:00]: "As a Scrum Master, you should have come forward to help your team... explain what you are talking is not being agile."

3. Proactive Communication: Regular, open conversations can prevent misunderstandings and mitigate conflicts before they escalate.

   Vasco Duarte [13:06]: "These are the conversations we should be having every single day... create the opportunity for improvement rather than the opportunity for blaming."

Conclusion

This episode serves as a poignant reminder of the delicate balance required in Agile environments. It underscores the profound impact that upper management's perceptions and actions can have on team morale and performance. By fostering empathetic leadership and proactive communication, Scrum Masters can safeguard their teams against such destructive patterns.

Key Takeaways

• Leadership Accountability: Effective leadership is crucial in maintaining team trust and morale, especially during conflicts.

• Scrum Master’s Role: Beyond facilitating processes, Scrum Masters must advocate for their teams and ensure their voices are heard in higher-level discussions.

• Proactive Problem-Solving: Addressing potential issues early through open dialogue can prevent catastrophic breakdowns in team dynamics.

Notable Quotes

• Somya Mehra [01:36]: "You can use it anywhere throughout your profession and personal and any part of your life."

• Somya Mehra [05:05]: "Everything was running on time, and the team was delivering as expected."

• Somya Mehra [08:34]: "He just threw the whole devs under the bus. Totally devs."

• Vasco Duarte [13:06]: "Create the opportunity for improvement rather than the opportunity for blaming."

This comprehensive exploration by Somya Mehra offers valuable lessons for Scrum Masters and Agile Coaches, emphasizing the importance of resilient leadership and the protection of team integrity against external pressures.