The Hidden Drag Kit

The polished behavior that quietly undermines trust, clarity, and delivery.

For leaders dealing with a high-performing, well-liked, or politically protected person who creates drag but can't easily be removed. This kit helps you name the pattern, build clean evidence, address it without a character war, and repair the team.

One tolerated behavior can teach the whole team what leadership is actually willing to protect.

The hardest behaviors to address aren't the loud ones. They're polished: the person is talented, charming, technically valuable, or politically connected — and underneath the surface, decisions slow, accountability blurs, and people quietly work around them.

Because the surface looks fine, leaders hesitate. And every week of hesitation teaches the team a lesson about what leadership will tolerate. This kit gives you a way through that's fair, documented, and free of drama — focused on behavior and impact, never character.

The goal isn't to win a case against a person. It's to restore the standard — name the behavior, name the impact, set a boundary with a consequence, and repair the trust the tolerance cost.

A note on language: "Clean Saboteur" is useful internal shorthand for the pattern, but this kit stays disciplined about addressing observable behavior and its impact — not labeling anyone's character or intent.

Name It

Hidden Drag Pattern Map

Make the invisible visible. Name what's actually creating drag underneath the polished surface.

Who or what is creating the drag — a specific person, or a recurring pattern?

What's the polished surface? (well-liked, high-output, technically strong, politically connected)

What's the actual drag underneath? (slows decisions, confuses accountability, makes others work around them, erodes trust)

Where does it show up most — meetings, handoffs, decisions, morale?

Who is paying the cost — and who isn't noticing it?

What has leadership done so far, and what has that taught the team?

Name It

Clean Saboteur Signal Decoder

Hidden drag hides behind polish. These are the signals that look fine on the surface and cost you underneath.

Polished signal	What it looks like	The drag underneath
Always agreeable in the room	Nods, never objects, "sounds good."	Reopens or quietly undermines the decision afterward.
Technically right, relationally costly	Correct — and leaves a trail of bruised people.	Others stop raising ideas; collaboration narrows.
Helpful in a way that creates dependency	Jumps in to "save" things.	Work routes through them; no one else can own it.
Raises concerns that stall everything	Always one more risk, one more question.	Decisions never close; caution becomes paralysis.
Charming upward, corrosive sideways/down	Leadership sees a star; peers see something else.	The people with evidence have the least power to name it.
Volunteers, then martyrs	Takes on work, then signals overload and resentment.	Guilt and obligation quietly steer the team.
Reorganizes work around themselves	Becomes the indispensable hub.	Accountability blurs; removing them feels impossible.

Which signals match what I'm seeing — and what's the clearest example of each?

Name It

Behavior vs. Personality

You can address behavior and impact. You cannot — and should not — put someone's character on trial. This worksheet keeps you on the ground you can actually stand on.

Character story (avoid)	Behavior + impact (use)
"He's arrogant."	"In the last two reviews, feedback was dismissed without discussion. The impact: people stopped offering it."
"She's manipulative."	"Agreements made in the room were renegotiated privately afterward, three times this month."
"They don't care."	"Three committed handoffs were late without notice. The impact: downstream rework."

The behavior I'm seeing (observable, specific):

The story I've been telling about who they are (name it so you can set it aside):

The observable impact of the behavior:

Rewrite: "When [behavior] happens, the impact is [X]."

Build the Evidence

Trust Leak Evidence Log

Evidence, not adjectives. A log of behavior and impact turns "I have a bad feeling" into something fair, specific, and addressable.

Discipline: record observable behavior and its impact — not personality, motive, or hearsay. Keep it to things you'd be comfortable having the person read.

Date	What happened (behavior)	Observable impact	Who was affected / witnessed	First time or repeat?

Build the Evidence

Team Workaround Detector

The team has often already decided the behavior is real — they're just absorbing the cost silently. Their workarounds are the evidence.

What has the team started routing around this person?

What conversations now happen without them in the room?

What work has quietly moved to someone else?

What are people no longer raising, because of how it tends to go?

What is the real cost of these workarounds — time, morale, duplicated effort, lost ideas?

Workarounds are the team's vote. They've already concluded the behavior is real; they're paying for it in silence because naming it feels riskier than absorbing it. That silence is the cost of the tolerance.

Build the Evidence

Protected Performer Risk Guide

Some people are protected — by talent, politics, tenure, likeability, or fear of the gap they'd leave. Naming why, honestly, is how you weigh the real trade-off.

Why is this person protected? (talent, politics, likeability, tenure, fear of losing them)

What does leadership fear will happen if the behavior is addressed?

What is actually happening because it isn't being addressed?

The honest math: the cost of the behavior (trust, attrition, slowed delivery) vs. the cost of losing them. Which is larger?

One tolerated behavior teaches the whole team what leadership is actually willing to protect. The most expensive cost is rarely the person — it's what the team learns to expect.

Address It

Impact Without a Character Attack

The conversation works when it's about observable behavior and specific impact — and when it leaves the person their dignity while removing their ambiguity.

The structure

Name the behavior — observable and specific, not a label.
Name the impact — concrete, on the work and the team.
State the standard — what's required, clearly.
Invite their view — without surrendering the standard.
Agree the change and the signal — how you'll both know it shifted.
Name the follow-up — a date, not a hope.

Open with behavior + impact"In the last three planning meetings, commitments we agreed on were reopened afterward. The impact is that the team no longer trusts what 'decided' means. I need that to change."

Separate value from behavior"I'm not questioning your intent or your value here. I'm asking for a specific change in [behavior], because of [impact]."

Make the change measurable"Here's what I need to see different: [behavior]. Here's how we'll both know it changed: [signal]. Let's check in on [date]."

Avoid: character labels, "everyone says," ambush timing, and the apology that quietly erases your ask.

Address It

Boundary + Consequence Map

A boundary without a consequence is a preference. Map what must change, what happens if it doesn't, and who holds the line.

Behavior	The boundary (what must change)	Consequence if it doesn't	Who enforces	By when

Address It

Documentation Without Drama

Document to create clarity and fairness — not to build a case for war. Stick to behavior, impact, and what was agreed; keep it something you'd be comfortable for them to read.

Field	Entry
Date & setting
Behavior (observable)
Impact (specific)
What was discussed / agreed
Agreed change & signal
Follow-up date

Test before you save it: would this read as fair if the person, your boss, and HR all saw it? If not, it's a vent, not a record — rewrite it to behavior and impact.

Contain & Repair

When You Can't Fire Them: Containment

Sometimes removal isn't possible — yet. Containment limits the blast radius, protects the team's clarity, and makes the cost visible to those who keep protecting them.

Where can I limit the blast radius — scope, decision rights, team exposure?

What decisions or handoffs can be cleanly rerouted so they're no longer the bottleneck?

How do I protect my strong contributors from absorbing the drag (or leaving over it)?

What do I document now, so that when the window to act opens, the case is ready and fair?

How do I make the real cost visible to whoever is protecting them — in behavior-and-impact terms?

Contain & Repair

Repairing the Team After Tolerated Behavior

By the time you act, the team has already learned something about what leadership protects. Repair means naming that without blame, restoring the standard, and acknowledging who paid the price.

What did the team learn from how long this went unaddressed?

What standard am I now re-establishing — clearly and out loud?

What do I owe the people who absorbed the cost (acknowledgment, redistribution, recognition)?

What will I do differently the moment tolerance starts next time?

Naming it to the team"I know this went on longer than it should have, and I know some of you carried the cost. Here's the standard going forward, and here's what I'm changing about how I handle it."

A team doesn't recover because the behavior stopped. It recovers when the meaning of the tolerance is named, the standard is restored, and people see that leadership will protect the work, not just the talent.