Psychological Safety is Not Impunity: A Practical Guide to Protecting Your Team from 'Worst Actors'
Discover how to manage disruptive behaviors while preserving psychological safety in your team. This guide offers Scrum Masters and team leads practical steps for setting healthy boundaries and addressing toxic actions.
Introduction: What Happens When Psychological Safety is Misunderstood?
In Agile teams, psychological safety is the cornerstone of an environment where members feel safe to take risks, make mistakes, and express their ideas freely. However, this valuable concept can sometimes lead to misunderstandings, such as 'anything goes' or 'being immune to criticism.' This can cause other team members to feel unsafe, especially when one member exhibits disruptive behaviors.
Psychological safety fosters an environment where teams feel safe to take risks, make mistakes, and express ideas freely, but it does not equate to tolerating disrespectful or destructive behavior. To protect your team from a 'worst actor,' you must establish clear boundaries, communicate expectations transparently, intervene early, and ensure accountability when necessary. The goal is to strike a balance where everyone feels secure, yet irresponsibility is not condoned.
Psychological Safety is Not Impunity: Why the Confusion?
The concept of psychological safety was first defined by Amy Edmondson as 'a shared belief held by members of a team that the team is safe for interpersonal risk taking.' This means team members feel comfortable speaking up without fear of appearing ignorant, incompetent, intrusive, or negative. However, this definition is sometimes misinterpreted by leaders and team members as 'everyone can say and do whatever they want.' This misinterpretation can create fertile ground for toxic behaviors to flourish within a team.
Consider Mark, a developer, for instance. Mark consistently dismissed other team members' ideas in meetings, made sarcastic comments, and offered excuses for missed deadlines. Team members hesitated to speak up or share their thoughts around Mark, fearing his reactions. Mark's behavior negatively impacted the team's overall morale and productivity. The Scrum Master, believing Mark was merely 'direct,' hesitated to intervene, fearing it would undermine psychological safety. In reality, this inaction was further eroding the team's sense of safety.
Step 1: Define Boundaries and Clarify Expectations
The first step in preserving psychological safety is to clearly delineate the boundaries between acceptable and unacceptable behaviors. This ensures the team develops a shared understanding.
Work with your team to create a 'Team Agreement' that outlines how you want to work together, how you will treat each other, and how you will manage conflicts. This agreement should cover not only technical aspects but also communication norms, feedback mechanisms, and boundaries of respect.
Example clauses:
- Every idea is valuable and will be listened to respectfully.
- Constructive feedback focuses on behavior, not the person.
- Mistakes are opportunities for learning, not tools for blame.
- Active listening and participation are encouraged in meetings.
- Diverse perspectives are respected, and discussions are solution-oriented.
Step 2: Observe and Intervene Early: Catching Small Issues Before They Grow
Problematic behaviors often begin with subtle signals. As a Scrum Master or team lead, recognizing and intervening early is critical. Passivity allows issues to escalate, further eroding the team's psychological safety.
Observe behaviors: Who becomes tense and when? Whose voice shrinks? Who remains silent in meetings? Such observations can be harbingers of potential problems. Document behaviors objectively, without personalizing them. For example, instead of 'Mark constantly interrupts,' note 'Mark interrupted Sarah twice during her presentation in the last three meetings.'
Early intervention should typically take the form of a private, one-on-one conversation. These discussions should focus on understanding the impact of the observed behavior on the team and supporting the individual, rather than being accusatory. You might start with an approach like, 'I've noticed you've been interrupting frequently in meetings lately. Are you aware of the impact this has on the team?'
Streamline Your Feedback Process: When planning constructive feedback conversations with your team members or preparing for difficult discussions, consider using the AgileKoc Feedback Assistant. This tool helps you structure your observations and design an effective feedback process, making your early intervention steps more efficient. Try it now to strengthen transparent communication within your team!
Step 3: Intervene: Constructive Feedback and Accountability
If early intervention proves ineffective or the severity of the behavior escalates, a more direct and structured feedback process is necessary. Feedback should be delivered using the 'Situation, Behavior, Impact' (SBI) model. This model helps to depersonalize feedback, focusing on specific actions and their consequences.
Example: 'During yesterday morning's sprint planning meeting (Situation), you were constantly looking at your phone and making sarcastic remarks while Sarah was presenting (Behavior). This lowered Sarah's motivation and distracted other team members, reducing the meeting's effectiveness (Impact).'
After providing feedback, re-clarify expectations and explicitly state the steps that will be taken if the behavior recurs. This is a crucial part of ensuring accountability. If necessary, collaborate with HR or senior management to address the situation. Remember, tolerating one person's disruptive behavior negatively impacts the morale and performance of the entire team.
For additional resources and training that can help your team develop a healthier communication culture, visit our AgileKoc Learn page. Here, you'll find in-depth content on managing challenging team dynamics and strengthening psychological safety.
Step 4: Protect and Support the Team: Rebuilding Trust
While addressing disruptive behaviors, it is vital to protect and support the rest of the team. Take proactive steps to ensure team members feel safe, repair any damage, and prevent similar situations in the future.
Team retrospectives offer a powerful platform to address such situations. However, be cautious when discussing sensitive topics. Frame retrospectives around learning and improvement rather than blame. Provide team members with a safe space to voice their concerns. Anonymous feedback tools can be beneficial in this process.
Open communication is key to rebuilding trust. As a team leader, when you make tough decisions or take action regarding a situation, communicate transparently with team members (without disclosing personal information). This reinforces the team's trust in leadership and strengthens their belief in working in a fair environment.
Get Support on Your Scrum Master Journey: Dealing with challenging team dynamics and maintaining psychological safety is one of the biggest challenges for a Scrum Master. Our AgileKoc Scrum Master Coach tool offers personalized guidance and strategies to help you navigate these situations. Develop your leadership skills with tailored advice and create a safer environment for your team.
The Unseen Game: Trust, Rhythm, Purpose
A practical mini-book using a football-club metaphor to reveal the invisible system behind performance: trust, alignment, roles, and team rhythm.
English edition
Checklist for Maintaining Psychological Safety
Here's a quick checklist you can use to manage disruptive behaviors while preserving psychological safety in your team:
- Establish a Team Agreement: Clarify acceptable and unacceptable behaviors.
- Communicate Expectations Clearly: Ensure everyone knows the rules.
- Observe Behaviors: Spot small signals early.
- Intervene Early and Privately: Address issues before they escalate.
- Provide Constructive Feedback: Be specific and objective using the SBI model.
- Ensure Accountability: Demonstrate that behaviors have consequences.
- Protect and Support the Team: Make sure affected members feel safe.
- Communicate Transparently: Inform the team about actions taken regarding situations.
- Foster Continuous Improvement: Use retrospectives as a learning tool.
Conclusion: Finding the Balance
While psychological safety is vital for a team's success, it does not imply tolerance for all behaviors. Your role as a Scrum Master or team lead is to strike a balance where team members feel safe, but respect and accountability are also paramount. By setting clear boundaries, intervening early, and providing constructive feedback, you can protect your team from 'worst actors' and foster a healthy, productive work environment for everyone. Remember, a strong team culture embraces both freedom and responsibility.
Short answers
Does psychological safety mean I can say anything I want?
No, psychological safety is the freedom to express ideas respectfully and constructively, but it does not cover behavior that harms or disrespects others. It promotes open communication within healthy boundaries.
How should I document a team member's disruptive behavior?
Objectively note what the behavior was, when and where it occurred, its impact on the team, and what actions were taken regarding it. Focus on observable facts rather than emotions.
Continue from here
Learn Scrum, agility, leadership, and team dynamics through structured content.
Explore LearnThe Unseen Game: Trust, Rhythm, Purpose
A practical mini-book using a football-club metaphor to reveal the invisible system behind performance: trust, alignment, roles, and team rhythm.
Who is it for?
Scrum Masters, Agile Coaches, Team Leads, Product/Engineering leaders
English edition
Make your Scrum Master impact visible + free PDF
Get short, practical tips each week. Your first email includes the “Scrum Master Impact Dashboard” PDF to help make your contribution visible.
SCRUM MASTER IMPACT DASHBOARD
30 Metrics + 6-Week Plan + Manager Conversation Guide
This document solves a common challenge for early/mid-level Scrum Masters: “How can my contribution be measured?” Without obsessing over velocity, without blame, you'll build a practical system focused on impact.
- Start in 10 minutes
- First results in 6 weeks
- Minimum set with 5 metrics
Golden rule: A Scrum Master doesn't “sell speed.” They improve learning and flow.
How to use this PDF
- 1) Pick 5 metrics today
- 2) Capture baseline (10 min)
- 3) Follow the 6-week plan
- 4) Update the dashboard each sprint
- 5) Talk to your manager with 3 sentences + 1 table
Minimum starter set
- Psychological safety
- WIP
- Sprint goal
- Unplanned work
- Blocker time
How do you prove your impact as a Scrum Master?
Without obsessing over velocity: 5 metrics + a 6-week plan for a clear impact story.
- 5-metric impact dashboard
- 6-week execution plan
- Manager-ready talk track
We respect your privacy. We only use your email to send the PDF and weekly tips.
No spam. Unsubscribe anytime.
