In Short
This article covers four frameworks that help managers confront toxic traits in their teams with structure, clarity, and authority rather than reacting in the moment.
- The L.E.A.D. Method: a four-step conversation structure for any serious leadership confrontation
- The S.B.I. Method: a feedback tool for naming toxic behaviour in observable, neutral terms
- The C.O.U.R.A.G.E. Method: a decision framework for high-stakes calls about team members who won't change
Toxic traits method refers to any structured system a manager uses to identify, name, and confront destructive behavioural patterns in a team member. Effective methods replace reactive confrontation with a repeatable process that preserves both honesty and professional authority.
A manager I once knew spent six months trying to handle a chronically undermining team member with patience, goodwill, and private conversations that never quite said the hard thing. She was not weak. She was not conflict-averse. She simply had no structure to reach for when the moment came, and so every conversation drifted into vagueness. The toxic traits spread. Two strong performers left. She lost the team before she ever lost her temper.
Here is the truth of it: when you face genuinely destructive behaviour in someone on your team, good intentions are not enough. Pressure compresses your thinking. Without a framework, you default to either aggression or avoidance. Neither works. What works is a system you have practised until it becomes instinctive, so that when the stakes are highest, the structure holds you steady.
In Say It Right Every Time, I introduce several frameworks built for exactly these moments. Chapter 7 covers the ones that matter most for leadership under pressure: the L.E.A.D. Method, the C.O.U.R.A.G.E. Method, and the S.B.I. Method. Together, they form a practical system for confronting toxic traits without losing the authority you need to lead.
Why Toxic Behaviour Resists Vague Conversations
Toxic traits survive in most teams for one reason: the conversations that should stop them are not clear enough. A manager senses something is wrong, calls the person in, and talks around the problem. The team member leaves with no precise understanding of what they did, what the impact was, or what must change. Nothing shifts. The behaviour continues. The manager loses a little more credibility each time.
Destructive patterns in a team are not just interpersonal irritants. They corrode the group's ability to function. Blame-shifting dismantles accountability. Public undermining of decisions destroys the manager's authority in front of the people watching. Persistent passive aggression, left unaddressed, teaches the whole team that standards do not apply equally. If you want to understand the full damage these patterns do to collective performance, the article on how to address passive-aggressive behaviour that's silently eroding team synergy gives you a detailed account.
The framework matters because it gives you a reliable path through a conversation that your instincts will try to derail. It does not remove the difficulty. It keeps you from losing your footing when the difficulty lands.
"The Conversation You're Avoiding Is the One You Need to Have."
"The Conversation You're Avoiding
Is the One You Need to Have."
Stop rehearsing conversations you'll never have. Say It Right Every Time gives you 115 word-for-word scripts and 16 proven frameworks to speak with confidence in every conversation that matters.
The Four Frameworks for Confronting Destructive Behaviour
Framework 1: The L.E.A.D. Method
What it is: A four-step structure for any serious leadership conversation about toxic traits. It keeps the conversation purposeful from the first word to the last.
Designed for: Any direct confrontation of a team member whose behaviour is consistently damaging to others, to team performance, or to trust in the team.
How it works:
Listen First. Open the conversation by giving the team member genuine space to speak. Not as a tactic, but because you need to understand their perspective before you can respond to it. Say: "Before I share what I want to discuss, I want to hear from you. How do you feel things have been going on the team recently?" Listen without interrupting. You will hear more than you expect.
Empathize. Acknowledge what they have said before you move into challenge. This is not agreement. It is recognition. "I hear that you have felt under-appreciated. I want to come back to that." Skipping this step puts people on the defensive before you reach the actual issue. A defended person cannot hear you clearly.
Articulate Your Vision. Now name the behaviour and its impact directly. This is where you use the S.B.I. structure (see Framework 2). Be specific. Be calm. Do not soften the message so much that the team member misses it. "In last Tuesday's team meeting, you interrupted Sarah three times and dismissed her proposal without letting her finish. The impact was that she fell silent for the rest of the meeting, and two other team members did the same."
Define the Next Steps. End with a clear expectation and a defined next action. "From this point forward, I need you to let people finish before you respond. In our next team meeting, I will be watching for that. Can you commit to that?" Clarity here is what separates a real conversation from a vague one.
When to use it: Any time you are sitting down with a team member specifically to address toxic traits. This is your primary conversation framework.
When not to use it: Not suited to a quick corridor correction of a minor misstep. That needs a simpler, shorter response. Reserve L.E.A.D. for the conversations that genuinely need structure and seriousness.
Worked example: A team member has been routinely taking credit for others' work in cross-departmental meetings. You call a private meeting. You open by asking how they see their recent contribution to the team (Listen). You acknowledge that they clearly want to be recognised for their work (Empathize). You describe three specific instances where they presented colleagues' outputs as their own (Articulate). You ask them to name a colleague's contribution by name in the next meeting they attend (Define Next Steps).
Eamon's note: I have used this framework dozens of times in the hardest conversations of my career. What I noticed every time is that the Listen step disarms people who come in expecting a fight. Most managers skip it. Do not skip it.
As outlined in Chapter 7 of Say It Right Every Time, the L.E.A.D. Method works because it mirrors how trust is actually built: you listen before you speak, and you name clearly before you demand change.
Framework 2: The S.B.I. Method
What it is: A three-part feedback structure for the Articulate step of L.E.A.D. It helps you describe toxic behaviour in terms the team member cannot deflect.
Designed for: Delivering the specific behavioural feedback at the centre of any confrontation conversation. Referenced in Chapter 5 of Say It Right Every Time and applied throughout Chapter 7.
How it works:
Situation. Name the specific context. "In Monday's project review..." Not "you always" or "you never." A time, a place, an observable moment.
Behaviour. Describe what the person did, not what you think they meant by it. "You interrupted the team lead twice and raised your voice when she pushed back." Stick to what was visible. Avoid inference.
Impact. Name the effect on others or on the work. "Two team members told me afterwards they did not feel safe speaking up. The decision that came out of the meeting was weaker because of it."
When to use it: Inside the Articulate step of L.E.A.D., and in any standalone feedback conversation about a specific toxic incident.
When not to use it: Not effective when the problem is systemic and long-standing with no specific incident to anchor the conversation. In those cases, you need to build a pattern from multiple S.B.I. examples.
Worked example: A manager confronting persistent blame-shifting says: "In Wednesday's client debrief [Situation], you told the client that the missed deadline was because your colleague had not given you the data in time [Behaviour]. The client's written feedback specifically mentioned they had lost confidence in the team's cohesion [Impact]."
Eamon's note: The Situation component is the one people skip. They say "you always" instead of naming a real moment. "Always" gives the other person an escape hatch. A specific situation takes it away.
If you want to work through the scripts for addressing team members who are actively undermining group cohesion, the resource on scripts for addressing team members who are undermining group synergy gives you ready-made language for these conversations.
Framework 3: The C.O.U.R.A.G.E. Method
What it is: A seven-step decision framework for the moments when toxic behaviour has escalated to the point where a high-stakes decision is required, such as performance management, role reassignment, or removal from a team.
Designed for: Managers who are facing a consequential decision about a team member with deeply embedded toxic traits and need a structured way to think it through before acting.
How it works:
Collect Information. Gather specific behavioural evidence before deciding anything. Document dates, incidents, witnesses.
Outline the Options. List every realistic course of action, from a final performance conversation to formal process to team restructure.
Understand the Impact. Consider the effect of each option on the individual, the team, and your own authority.
Review Your Values. Ask what you are willing to stand behind as a leader. This is not a soft question; it defines what you will say out loud and defend.
Act with Conviction. Make the decision and own it. Half-decisions made under pressure produce half-consequences.
Gauge the Reaction. After you act, read the response honestly. From the individual. From the team. Adjust your follow-through based on what you observe.
Explain Your Rationale. Be transparent about the reasoning behind the decision with the people it affects. Not every detail, but the "why."
When to use it: When the toxic behaviour has not changed after direct L.E.A.D. conversations and a consequential decision now sits in front of you.
When not to use it: Overkill for a first or second incident. This is for situations where the pattern has been named, the expectations have been set, and the behaviour has not changed.
Worked example: A manager has had three L.E.A.D. conversations with a team member who consistently excludes a colleague from information flows and undermines team decisions in group settings. The manager uses C.O.U.R.A.G.E. to decide whether to escalate to formal performance review, restructure the team's communication process, or have a final direct conversation before formal action. The framework keeps the decision from being driven by frustration rather than clear thinking.
Eamon's note: Most managers skip to Act with Conviction and miss Gauge the Reaction. You are not done when you make the decision. You are done when you have seen what it produced and responded to that honestly.
Framework 4: The Neutral Problem Statement
What it is: A single framing tool for opening a confrontation conversation in a way that names the issue without triggering immediate defensiveness.
Designed for: The opening of any difficult conversation about toxic traits, before you move into the full L.E.A.D. structure.
How it works:
Name the observable pattern without judgement. "I want to talk about something I have noticed in team meetings over the past three weeks." No accusations. No adjectives like "toxic" or "disrespectful."
Separate the person from the behaviour. "This is not about who you are. It is about a specific pattern I need us to address."
State your intention. "My goal in this conversation is to find a way forward that works for you and for the team."
When to use it: Before L.E.A.D., to set the frame for a difficult confrontation conversation.
When not to use it: If the situation has already escalated beyond a first confrontation and the team member knows what the meeting is about, skip the neutral frame and move directly into L.E.A.D.
Worked example: A manager opens a meeting about a team member's chronic exclusion of a colleague: "I have noticed a recurring pattern over the past month where certain decisions are made and communicated to some team members before others. I want to understand that together, and I want to address it directly."
Eamon's note: The Neutral Problem Statement is a short tool. Do not stretch it into a preamble that lasts ten minutes. One to two sentences, then move forward.
The full detail on delivering this kind of opening is in the article on how to deliver a neutral problem statement that stops team conflict before it destroys synergy.
Framework 5: The Honest Accountability Script
What it is: A short verbal structure for the end of any confrontation conversation, designed to secure a genuine commitment rather than a vague agreement.
Designed for: Closing the "Define Next Steps" phase of L.E.A.D. with precision.
How it works:
State the expectation in one sentence. "From this conversation forward, I need you to allow every team member to finish speaking before you respond."
Ask for a direct commitment. "Can you commit to that?" Wait for an answer. Do not fill the silence.
Name the consequence of non-compliance. "If I see this pattern continue after today, I will need to escalate this to a formal performance conversation."
Document the exchange. After the meeting, write a brief record of what was said, what was committed to, and what the stated consequence was.
When to use it: At the close of every L.E.A.D. conversation about toxic traits.
When not to use it: Not appropriate for exploratory conversations where you are still gathering information. This is a closing tool, not an investigative one.
Worked example: After a full L.E.A.D. conversation about a team member who has been publicly dismissing colleagues' ideas, the manager closes with: "I need you to respond to colleagues' proposals with a genuine question before you offer a counter-argument. I am asking you to commit to that today. If I observe the same pattern in the next team meeting, I will initiate a formal performance review. Are we clear?"
Eamon's note: The silence after "Can you commit to that?" is hard to sit with. Sit with it. The answer you get there is the truest one you will hear in the whole conversation.
How to Pick the Right Framework for the Situation
Different toxic traits call for different entry points. This table gives you a quick read on which framework fits which situation.
| Situation | Start Here | Use Also |
|---|---|---|
| First confrontation about a specific incident | Neutral Problem Statement | S.B.I. inside L.E.A.D. |
| Pattern of toxic behaviour over weeks | L.E.A.D. Method (full) | Honest Accountability Script at close |
| Delivering specific behavioural feedback | S.B.I. Method | Inside L.E.A.D.'s Articulate step |
| Escalating decision: formal process or exit | C.O.U.R.A.G.E. Method | L.E.A.D. for the final conversation |
| Blame-shifting or deflection in meeting | Neutral Problem Statement | L.E.A.D. follow-up privately |
| Chronic passive aggression | L.E.A.D. Method (full) | S.B.I. for naming specific incidents |
The short version: the Neutral Problem Statement opens a confrontation. S.B.I. names the behaviour with precision inside the conversation. L.E.A.D. structures the full exchange from start to close. C.O.U.R.A.G.E. governs the hard decisions when conversations alone have not changed the behaviour.
For the full architecture of how L.E.A.D. applies across all kinds of leadership conversations, not just those involving toxic traits, the article on how to use the L.E.A.D. Method to drive team synergy through every leadership conversation takes you through the broader application.
The Mistakes Managers Make When Confronting Toxic Behaviour
Structure helps, but only if you apply it correctly. Here are the four errors I see most often.
The mistake: Waiting for certainty before acting.
Why it happens: Managers fear being wrong about a person and causing harm.
What to do instead: You do not need certainty. You need a pattern. Two clear instances, documented, is enough to begin a L.E.A.D. conversation.
The mistake: Using character language instead of behavioural language.
Why it happens: Frustration turns specific incidents into global judgements. "You are undermining this team" instead of "In Tuesday's meeting, you dismissed Sarah's proposal before she had finished presenting it."
What to do instead: Return to S.B.I. every time. Situation. Behaviour. Impact. No adjectives about character.
The mistake: Ending the conversation without a clear, named consequence.
Why it happens: Managers worry that naming a consequence sounds threatening and damages the relationship.
What to do instead: A consequence is not a threat. It is honesty. Without it, the team member has no real reason to change, and you have no line to hold.
The mistake: Having the conversation once and assuming it is resolved.
Why it happens: The relief of having said the hard thing leads managers to step back and wait.
What to do instead: Follow up within a week. Acknowledge improvement if you see it. If you do not see it, have the second conversation immediately. Silence after the first conversation signals tolerance.
Managers who have lost confidence in their own authority after letting toxic behaviour run too long will find the framework for rebuilding trust in the article on how to use the L.E.A.D. Method to restore synergy after a team has lost confidence in leadership.
Building Fluency With These Frameworks Over Time
You will not apply these frameworks perfectly in the first conversation. That is not the goal. The goal is to practise enough that pressure no longer strips the structure away.
Weeks one and two: Use S.B.I. alone. Apply it in every feedback conversation, even low-stakes ones. Name the Situation, the Behaviour, and the Impact every time you give developmental feedback. You are building the habit of behavioural language before you need it in a harder context.
Weeks three and four: Add the Neutral Problem Statement. Use it to open any awkward or challenging conversation, not only those involving toxic traits. Notice how a neutral frame changes the temperature at the start of a difficult exchange.
Weeks five and six: Run a full L.E.A.D. conversation in a one-to-one meeting, even on a less serious topic. Practise listening without planning your response during the other person's turn. Practise the silence at the close of the Define Next Steps step.
Beyond six weeks: The frameworks become instinctive enough that you can adapt them under pressure. You will still feel the pressure. You will just have the structure to stand on.
Using "I" statements effectively throughout these conversations keeps the focus on observable impact rather than blame. The article on how to use 'I' statements in team conversations to prevent synergy-breaking blame cycles gives you the language patterns to practise alongside the frameworks above.
It also helps to understand how toxic traits surface differently when a team is going through change. The articles on how to communicate a strategic change to your team in a way that preserves synergy and how to use the L.E.A.D. Method to restore synergy after a team has lost confidence in leadership address the context in which destructive patterns most often intensify.
What to Take Forward
Confronting toxic traits is not a talent some managers have and others do not. It is a skill. It is built through preparation, through the right frameworks applied at the right moment, and through the courage to say the clear thing when the comfortable thing would be to say nothing.
In Say It Right Every Time, I wrote this: "Your job as a leader is to be clear, not to be comfortable." That is the whole of it. Clarity protects the people who are being damaged by toxic traits. Clarity protects the team's ability to do good work. And clarity, applied consistently through a reliable toxic traits method, is what separates managers who hold authority from those who lose it, one avoided conversation at a time.
Reach for the structure. Have the conversation. Hold the line.
Frequently Asked Questions (FAQ)
What is the toxic traits method for managers?
The toxic traits method for managers is a structured approach to naming and confronting destructive behaviour in a team. The L.E.A.D. Method, covered in Chapter 7 of Say It Right Every Time, gives managers four clear steps: Listen First, Empathize, Articulate Your Vision, and Define the Next Steps.
How do you use the L.E.A.D. Method to address toxic behaviour?
You open by listening without judging, then name the emotional impact honestly, then describe the behaviour and its effect on the team, and finally set a clear expectation with a defined next step. The method keeps the conversation structured so pressure does not strip away your authority or your clarity.
When should a manager confront toxic traits in a team member?
Confront toxic traits as soon as a pattern is clear, not after the third or fourth incident. Waiting signals tolerance. The right moment is after you have observed at least two specific instances and can describe the behaviour in neutral, factual terms rather than reacting emotionally to a single event.
What are the most common toxic traits that undermine a team?
The most damaging toxic traits are blame-shifting, persistent undermining of colleagues, chronic passive aggression, public dismissal of team decisions, and deliberate exclusion of others. Each erodes trust differently, but all of them share one feature: left unaddressed, they teach the rest of the team that destructive behaviour carries no consequence.
How do you confront a toxic team member without losing authority?
You keep authority by staying calm, specific, and direct. Name the behaviour, not the character. Use the S.B.I. framework to anchor the conversation in observable facts. Set a clear expectation and a defined consequence. Follow through every time. Authority is not volume; it is consistency.
What is the difference between the L.E.A.D. Method and the S.B.I. Method?
The L.E.A.D. Method structures the full leadership conversation from opening to close. The S.B.I. Method handles one specific component within that conversation: delivering the feedback itself. You use S.B.I. inside L.E.A.D., when you reach the Articulate step and need to name the toxic behaviour with precision.
How do you build fluency in confronting toxic behaviour over time?
You practise each framework separately before combining them. Start with S.B.I. in low-stakes feedback conversations. Then use the L.E.A.D. structure in a one-to-one review. After six weeks of deliberate use, the sequence becomes instinctive enough that pressure no longer strips it away when the conversation turns difficult.
