Scripts for Addressing Team Members Who Are Undermining Group SynergyShare

There is a moment most people recognise: you leave a team meeting knowing that one person just set the group back by two weeks, and nobody said a word. Having the right script ready changes that moment completely.

These scripts work because they are grounded in a principle I have spent decades testing: when you name the behavior clearly, connect it to its impact on the team, and ask for a specific commitment, you give the other person something real to respond to. Vague frustration creates defensiveness. Specific, calm language creates accountability. That is the difference between a conversation that repairs and one that simply escalates.

Find the script that matches your situation. Read the context and the "Why this works" note before you open your mouth. Practice it out loud at least twice. These words read differently than they sound, and you need to hear yourself say them before the real moment arrives.

If you are still deciding whether to have the conversation at all, the piece on why avoiding difficult conversations is the hidden enemy of team synergy will help you settle that question first.

In Say It Right Every Time, I introduce the D.E.A.L. Method and S.B.I. framework in Chapter 6 as the structural backbone for exactly these conversations. Both appear throughout the scripts below. The full approach is detailed in Say It Right Every Time.

How to Use These Scripts

Before you use any of these scripts, follow these steps.

1. Find the situation that matches yours as closely as possible.
2. Read the full script and the context note before speaking or writing.
3. Adapt the words to your natural voice: keep the structure, change the tone.
4. Practice out loud at least twice. Scripts read differently than they sound.

The most common mistake people make with word-for-word scripts is reading them verbatim without adjusting for the relationship or the emotional temperature of the moment. A script you deliver robotically will feel scripted, and the other person will shut down. Use the structure. Own the words.

Script 1: Addressing Someone Who Dismisses Others' Contributions

Situation: Use this script when a team member consistently talks over colleagues, rejects ideas without engaging them, or creates a pattern where others stop speaking up. The group dynamic is suffering because one person's presence is shrinking the room.

Why this works: This script uses the S.B.I. structure from Chapter 6 of Say It Right Every Time: Situation, Behavior, Impact. It stays factual rather than personal. You are not attacking the person; you are naming what happened and showing them the cost to the team.

Standard version:

"[Name], I want to talk with you about something I've noticed in our team meetings. In the last few sessions, when [colleague's name] or others have raised ideas, you've cut them off or moved past them before they could finish. I know that might not be intentional, but the impact is that people have started holding back. We're losing contributions we need. I need that to change. Can we talk about how you want to handle it differently going forward?"

Formal version:

"[Name], I'd like to discuss a pattern I've observed in our recent team meetings. On several occasions, including [specific meeting], you interrupted colleagues before they could complete their points, and several ideas were not given the consideration they deserved. The impact of this on the team's dynamic is significant: participation has dropped, and people are not contributing at the level we need. I'm asking you to commit to a different approach. What would that look like from your side?"

After you use it: A good response includes acknowledgment, even reluctant acknowledgment, and a willingness to name what they will do differently. A difficult response is denial or deflection. If that happens, say: "I'm not here to debate what happened. I'm telling you what I observed and what needs to change."

Eamon's note: The words "I need that to change" are the most important in this script; do not soften them.

Script 2: Confronting Repeated Missed Commitments

Situation: Use this script when a team member has missed deadlines, failed to follow through on agreed tasks, or consistently let the group down on deliverables. This is not a one-off lapse. The pattern is real, and the team is absorbing the cost.

Why this works: As I outline in Chapter 6 of Say It Right Every Time, a verbal agreement is not enough. Accountability requires a locked-in commitment with specific language and a follow-up mechanism. This script builds that structure directly into the conversation.

Standard version:

"[Name], I need to talk with you about the last three sprints. You committed to delivering [specific tasks] by [dates], and on each occasion it didn't happen. I'm not here to pile on; I want to understand what's getting in the way. But I also need you to know that the team is carrying the cost of this, and it can't keep going. Can you tell me what's actually happening on your end, and then let's agree on what you can realistically commit to going forward?"

Formal version:

"[Name], I want to address a pattern that has developed over the past [timeframe]. You committed to [specific deliverables] on [specific dates], and on each occasion, those commitments were not met. This has had a direct impact on the team's ability to deliver on our shared goals. I'd like to understand the barriers you're facing, and then I need us to establish a clear, specific commitment with an accountability check-in. Are you ready to do that?"

Casual version:

"[Name], I have to be straight with you. The last few times you said you'd have [task] done, it didn't happen, and the team's been picking up the slack. I'm not angry. I just need to know what's going on and figure out what you can actually commit to. Can we do that now?"

After you use it: Watch for whether they offer a reason or an excuse. A reason acknowledges their part; an excuse redirects blame. If they commit to a specific change, confirm it in writing immediately after the conversation. If they resist entirely, involve a senior leader or HR.

Eamon's note: This is the conversation that most managers delay until it is too late; have it at the second missed commitment, not the fifth.

Script 3: Opening a Direct Conversation About Disruptive Behavior

Situation: Use this script when a team member's behavior is creating consistent friction: dominance in group settings, dismissal of agreed decisions, or creating coalitions against certain colleagues. The behavior is open, repeated, and known to the group.

Why this works: In Say It Right Every Time, I describe conflict as a form of energy: left uncontrolled, it destroys; structured correctly, it produces growth. This script channels that energy by naming the problem calmly and opening a structured conversation using the D.E.A.L. Method: Define the Issue, Explore Perspectives, Agree on a Solution, Lock in the Commitment.

Standard version:

"[Name], I need to talk with you directly. Over the past [timeframe], I've noticed [specific behavior: e.g., 'you've been pushing back on team decisions after they've been made, and taking that pushback to other colleagues rather than back to the group']. I understand you may have real concerns; I want to hear them. But the way this is playing out is creating friction that's hurting how we work together. I'd like us to go through what's actually bothering you, and then agree on how we handle disagreements as a team going forward."

Formal version:

"[Name], I'd like to have a direct conversation about something that's been affecting our team's ability to function cohesively. I've observed [specific behavior] on [specific occasions]. I want to understand your perspective, and I also want to be clear: the current pattern is not something we can continue with. My goal today is to define the issue clearly, hear your view, and agree on a specific path forward. Can we do that?"

After you use it: If they engage genuinely, move through the D.E.A.L. steps: let them give their perspective without interrupting, then work toward a concrete agreement. If they become defensive or escalate, slow the conversation: "I think we need to step back for a moment. This isn't working if we're both reacting. Can we take five minutes and come back to this?"

Eamon's note: The phrase "the way this is playing out" keeps the focus on behavior and effect, not character; it is doing a great deal of work in that script.

Script 4: Responding to a Passive-Aggressive Pattern

Situation: Use this script when a team member's undermining is indirect: sarcastic comments, pointed silences, eye-rolling in meetings, or emails that communicate displeasure without naming it. The behavior is real, but it operates in the space between what is said and what is meant.

Why this works: As I describe in Chapter 6 of Say It Right Every Time, passive-aggressive behavior thrives on plausible deniability. This script removes it. You name what you observed, invite them to clarify, and make clear that you expect direct communication going forward. The companion piece on how to address passive-aggressive behavior that's silently eroding team synergy covers the broader pattern.

Standard version:

"[Name], I noticed [specific moment: e.g., 'the comment you made in this morning's meeting about people not pulling their weight']. I want to check in with you directly: if that was directed at me or at the team, I'd really rather we talk about it openly. If there's something bothering you, I want to hear it. Can you tell me what was behind that?"

Formal version:

"[Name], I'd like to follow up on [specific comment or behavior] from [specific context]. I want to understand whether there is a concern you'd like to raise directly. If there is, I want to hear it. What I'd ask going forward is that if you have a concern about how the team is working, you bring it to me or to the group directly rather than addressing it indirectly. Can we agree on that?"

After you use it: Some people will deny any intent and back down, which ends the immediate behavior. Others will open up and share a real concern, which is the best possible outcome: you have now surfaced an unspoken expectation that was quietly poisoning the dynamic. If they deny it and continue the behavior, address the next instance immediately and in writing.

Eamon's note: "Unspoken expectations are premeditated resentments" is one of the truest things I have ever written; this script is built to clear them out before they take root.

Script 5: Addressing Two Team Members in Ongoing Conflict

Situation: Use this script when two team members have an unresolved dispute that is now affecting the whole group: the tension is visible in meetings, work is being duplicated or avoided, and others are being pulled into sides. You are acting as the leader or senior colleague who needs to bring them to the table.

Why this works: This situation calls for the B.R.I.D.G.E. Method from Say It Right Every Time: Begin with an Apology, Reaffirm the Relationship, Identify the Breakdown, Discuss New Expectations, Gain Agreement, Establish a Follow-up. This script initiates that process. The full approach to mediation is covered in the article on how to mediate between two team members to preserve group synergy.

Standard version:

"Thank you both for being here. I've spoken with each of you individually, and it's clear that there's a situation between you that needs to be resolved: not just for your own working relationship, but because it's affecting the whole team. My goal today is not to decide who is right. It's to help you both find a way to work together that actually works. I'm going to ask each of you to share your perspective without interrupting, and then we're going to find a path forward together. [Name], I'd like to start with you."

Formal version:

"I appreciate you both making time for this. The situation between you has reached a point where it is affecting the team's ability to deliver, and that requires us to address it directly and constructively. I will ask each of you to share your perspective in turn, without interruption. I will then summarise what I have heard, and we will work together to agree on specific new expectations for how you interact going forward. There will be a follow-up check-in in [timeframe]. Let us begin."

After you use it: Watch for whether both parties engage genuinely or whether one stonewalls. A productive session ends with specific, named agreements: not "we'll communicate better" but "we'll copy each other on client emails within 24 hours." Follow up in writing the same day. For deeper guidance on rebuilding the team afterward, see how to rebuild team synergy after conflict or organizational change.

Eamon's note: A solution imposed on one person is not a solution; it is a temporary ceasefire, and this script is designed to get you past that.

Script 6: Setting Clear Expectations After a Pattern of Undermining

Situation: Use this script when you have already had an initial conversation with someone about their behavior, and the pattern has continued. This is the follow-up: firmer, more specific, and with named consequences if the behavior does not change. Use the L.E.A.D. Method from Chapter 7 of Say It Right Every Time: Listen First, Empathize, Articulate Your Vision, and Define the Next Steps.

Why this works: When a first conversation does not produce change, the second one must be more structured and more direct. This script applies the L.E.A.D. Method: it listens, acknowledges reality, states clearly what the team needs, and locks in specific next steps. The piece on how to give feedback that strengthens team synergy instead of breaking it offers additional support for this stage.

Standard version:

"[Name], we spoke about [specific behavior] on [date], and I want to follow up because I've seen [specific instance] happen again since then. I want to understand if something has changed or if there's something I can do differently to support you. But I also need to be clear: the impact on the team is ongoing, and I need it to stop. From today, I need you to [specific behavior change]. I'll check in with you on [date]. If I see [specific behavior] again before then, we will need to involve [HR / senior leadership]. I'm telling you that now so there are no surprises."

Formal version:

"[Name], following our conversation on [date] regarding [specific behavior], I want to address the fact that [specific instance] has occurred again on [date]. I want to give you the opportunity to share whether there are circumstances I should be aware of. That said, I need to be direct: the behavior has continued, and the impact on the team's cohesion and performance requires a firm resolution. The expectation going forward is [specific behavior]. I will follow up with you on [date]. If the behavior recurs prior to that, the matter will be escalated to [HR / senior leadership]. I want us to resolve this without reaching that point."

After you use it: Document this conversation in writing immediately: date, what was said, what was agreed. Send a brief follow-up email confirming the commitment. If the behavior recurs, you now have a clear record. For guidance on de-escalating if the conversation becomes heated, see how to de-escalate team conflict without destroying synergy.

Eamon's note: Your team is watching how you handle this; naming the consequence clearly is not a threat, it is respect for everyone in the room.

Adapting These Scripts for Your Situation

Every script in this article is a starting point, not a final word. The structure is what holds; the language is yours to shape.

Adjust for relationship length. A script delivered to someone you have worked with for five years will land differently than one aimed at a new team member. With a long-term colleague, you can be warmer and reference shared history. With someone newer, stay closer to the script's neutral register.

Match the register to the stakes. The formal versions are designed for situations involving HR, senior leadership, or written records. The standard versions suit most peer and direct-report conversations. If you reach for the formal version in a casual peer relationship, you will create unnecessary distance.

Remove any phrase that does not sound like you. Read each script out loud and mark the phrases that feel forced. Replace them with your own words; keep the structure. The goal is a conversation that sounds like a prepared, confident version of you, not a script recited from a page.

Slow down for the hard parts. The sentences that name the impact on the team are the ones people rush through because they feel uncomfortable. Those sentences are the most important. Practice them at a pace that gives them weight.

The goal is for these words to sound like a better, more prepared version of you, not like someone else.

Common Mistakes When Using Scripts for Team Conversations

The biggest way scripts fail is when people read them as written rather than owning them in the room. The words become a wall between you and the other person, and the conversation collapses.

• Reading verbatim without eye contact. If you are looking at notes instead of the person, you have already lost the conversation. Know the structure cold enough that you can deliver it while staying present.
• Skipping the listening phase. Several of these scripts open a space for the other person to respond. Do not rush past that moment. Genuine curiosity about their perspective is not weakness; it is what makes the conversation real. The signs your team lacks synergy and how to fix it article covers why this matters at a team level.
• Softening the impact statement. The line that names what the behavior is doing to the team is the line people water down. "It's kind of affecting things a bit" is not the same as "the team is absorbing the cost of this." Say the true thing.
• Forgetting to lock in the commitment. A conversation without a specific agreed change is just an exchange of feelings. Every script in this article ends with a question or a clear expectation. Use it. The how feedback loops boost team synergy piece explains how to structure the follow-up.
• Waiting too long. The most common mistake is not in the delivery; it is in the delay. By the time most people reach for a script, the behavior has been running for months. Address it at the second instance, not the tenth.

A script is a tool. Use it like one: with skill, not rigidity.

Frequently Asked Questions (FAQ)

What does undermining group synergy mean in a team?

Undermining group synergy means one person's behavior is actively reducing the team's ability to work well together. It can be deliberate or unintentional. Common forms include dismissing others' ideas, missing commitments, creating side conflicts, or dominating decisions without buy-in.

How do you address someone who is undermining group synergy without making it worse?

Address the behavior directly and privately, using specific examples rather than general accusations. Focus on what you observed and how it affected the team, not on the person's character. Scripts built on the S.B.I. method — Situation, Behavior, Impact — are effective because they stay factual and forward-focused.

What should you say to a team member who keeps undermining group synergy?

Name the specific behavior, describe its impact on the team, and ask for a clear commitment to change. Avoid vague language like "you need to be a better team player." Instead, say what you saw, when it happened, and what needs to be different going forward.

When is the right time to have a conversation about undermining group synergy?

Have the conversation as soon as possible after the behavior occurs, within 24 to 48 hours. Waiting allows the behavior to become normalized. Choose a private setting and a moment when both of you are calm. Never address it publicly or in the middle of a tense situation.

What if someone denies that they are undermining group synergy?

Stay grounded in specific examples and avoid debating intentions. Say: "I'm not here to argue about intent. I'm telling you what I observed and how it affected the team." If denial continues, document the conversation and involve HR or a senior leader if the behavior persists.

Can scripts really help you address someone who is damaging team synergy?

Yes, if you use them as a framework rather than reading them word for word. Scripts give you a structure that keeps the conversation focused and prevents emotional derailment. Adapt the language to your relationship and tone, but keep the core structure: name the behavior, describe the impact, ask for commitment.

Here is the truth of it: the hardest part of addressing someone who is undermining group synergy is not finding the words. You have them now. The hardest part is deciding that the conversation matters enough to have. It does. The team you are trying to protect is watching, even when they seem not to be. Use these scripts, practice them, and trust that a prepared, direct conversation is the single most powerful act of leadership available to you.