How to spot a saboteur before your reputation pays for it

Throughout the meeting, he nodded along as people spoke. He said "sounds good" twice. Then at 7:40 that night the recap email arrived, copied to your boss, and somewhere in the third paragraph your proposal had turned into "an option the team had some reservations about." You had been in the room and heard no reservations at all. That's exactly the trick. Those doubts were written for one reader, and it wasn't you.

Every impulse pushes you toward a hot-headed response sent to everyone on the thread. That usually backfires, because it shifts a problem with the written record into a problem with a person. Your boss now watches two colleagues bicker about a meeting she didn't sit in, and whoever sounds level-headed comes out ahead. He sounds level-headed. He got there first.

First. Then the recap lands in inboxes and slyly reshapes what was actually decided.

A tempting retort would be: "That's not how we left it, and you're fully aware of that."

A stronger approach: "For the record, we settled on advancing with the Q2 plan." Glad to go over any concerns I might have missed."

Why: one clear sentence corrects the record in writing, with your boss copied, and it reads as a courtesy rather than a fight. The second sentence gives him the chance to name concerns he never raised, which he usually can't do.

Second. Right in front of your supervisor, he insists "I assumed we were aligned on this."

A tempting reply: "We were, right up until your email went out."

A stronger reply: "We were lined up on the plan." Let's lock it in right now so nobody is left reconstructing it afterward.

Why this works: you kept attention on the decision instead of on him, and you got a confirmation spoken aloud before the people who matter. Saboteurs rely on vagueness. Remove that visibility and their maneuvers lose their effect.

Third. He endorses decisions openly, then expresses doubts once the room is empty.

A tempting move is acting as though those private doubts never reached you.

A stronger move: "I hear you had some reservations after the meeting." Let's put them on next week's agenda so everyone on the team can contribute.

Why: you pulled the private conversation into the open, where it can actually be answered. Not one word of that points a finger at him. It gives his concerns a place and a time, which is what honest concerns need and what quiet ones avoid.

Fourth. Your credit disappears when the recap goes out.

A tempting line: "To be precise, that idea came from me."

A stronger line: "Some background for everyone: this originated in the analysis my Nashville team completed in March." The full deck is attached for anyone who wants to dig into the specifics.

Why this works: studies on the likability penalty consistently show that identical requests sound assertive from a man and demanding from a woman, so back up your claim with evidence instead of adjectives. A presentation sent along with an email is very tough to push back on.

Fifth. You opt to talk it over with him in person.

An appealing starting line: "Why are you always getting in my way?"

A stronger opener: "Two times now, the recap has failed to reflect what was said in the room." From here on, let's draft it together before anything is sent.

Why: a direct question invites a denial. A proposal invites a yes. He is free to decline co-writing the recap, but he would then owe your manager an explanation, a talk he'd much prefer to skip.

The rule underlying all five, as seen across Nashville and the rest of Middle Tennessee, is the same.

Whoever drafts the minutes shapes how the meeting is remembered. Rather than debating what was said, get it in writing first, in a manner polite enough that nobody could label it a dispute. You aren't accusing anyone. You are simply keeping the record accurate, and only one person here has cause to push back.

Forward this to the coworker who keeps puzzling over why her ideas disappear in email.