Perhaps it’s because we are approaching the end of the quarter and reviews are top of mind for many; a theme that came up in multiple conversations this week was how to handle a passive-aggressive stakeholder in the room, in real time.
It usually plays out something like this. In a launch readiness assessment meeting with senior leadership, an engineering leader from an adjacent team drops a cynical comment:
“I am sure we will make this deadline. Third time is the charm after all.”
Your irritation instantly flares up, and your brain fires off a number of responses you know better than to say out loud. You don’t react in the room because you know how it shapes others’ perceptions of you, but you spend the afternoon replaying the comment on a loop, wondering what the leadership team heard and what they really think of you after it.
People get away with passive-aggressive behavior because it comes with an exit. They get to register their doubt or irritation publicly, and if you push back, it’s easy to claim they were just joking or that you’re being sensitive. Any approach that works has to take this exit away, and do it without making you look rattled in front of the people whose opinion matters.
In my coaching work, the approach that holds up has four parts: what you say in the room, what you say afterward in private, what you write down, and when you bring in your manager.
What to do in the moment
Notice whether you are reacting or you’re responding. A reaction is fast and emotional, whereas responding is a tad slower because you are being deliberate and mindful.
In trying not to react, some swing to the other extreme and let it slide. Don’t do that. When someone signals doubt about your work in front of senior leaders and the challenge goes unaddressed, people tend to fill in the blank themselves, and they rarely do so in a way that gives you the benefit of the doubt.
A good response answers the concern with facts and gives leadership confidence. Stick to the content of the comment and don't speculate about the speaker's motives, which is a slippery slope in public.
"Fair question on the timeline. We're on track for October 12th. The major risk here is the vendor integration, and we have a fallback if it slips. Happy to go deeper if there's a specific concern."
You addressed the doubt without acknowledging the snark, and you sound like the person who knows the plan best.
If the room is mostly your peers rather than executives, a neutral question works well: “Sounds like you have a concern about the timeline. What is it?” It turns the spotlight on them and forces a choice. Either they back off, or they tell you what’s actually bothering them.
If the concern is fair but the delivery isn't, take the point and ignore the packaging. If delivery did slip before, acknowledge it and explain what’s different this time. You will earn credibility for owning it, and the passive-aggressiveness loses its power.
If the comment is unjustified, the reason why it’s unjustified matters.
If the premise is wrong, correct it once and move on. Keep your voice steady, and state the facts.
“Small correction. We’ve hit both of the prior milestones as targeted earlier this quarter. We are on track for a launch on October 12th.”
Resist the temptation to add “As I mentioned earlier” or deliver a long rebuttal that tells the room that the comment got to you. A brief, one-line statement of fact will do the job far more efficiently.
The harder problem is if the snark was an effort to deflect attention and blame. For example, if the timeline is at risk because of a dependency on the other team, stick to the facts and skip the finger-pointing.
“The main risk is API readiness, which we are expecting on September 25th. If that holds, we are on track for the launch on October 12th.”
Sticking with the facts makes you appear professional, and anyone following the conversation will read it for exactly what it is. You can defer specifics about the dependency to a later date, potentially to a smaller audience or a 1:1 where you can explain without causing public fallout.
If every response of yours is met with a new question trying to go further down the rabbit hole, decline to engage by saying, “Let’s take the details offline so we can be respectful of this group’s time.” The VPs will usually be relieved not to have to witness a public squabble among their reports.
Follow up with a 1:1
Plan to keep the conversation short and specific, and assume positive intent even if you’re not sure it’s warranted. Open by stating the observed behavior.
“In the review yesterday with the Senior Leadership Team, you raised the question about our ability to meet the deadline. I'd rather hear concerns like that before the meeting so we can sort them out together. I may have missed something in how we rolled this out.” The last sentence lowers the other person's guard and makes it easier for them to be honest. Then stop talking. Do not fill any silence; wait for the other person to respond.
If they name something specific like “the API team is already running behind,” deal with that.
If they respond vaguely or suggest you may have misinterpreted their comment, recognize there may be something else going on. Ask follow-up questions that give them room to volunteer information about specific motives. Some examples:
"What would need to be true for you to feel good about this timeline?" If the answer is concrete, the concern is probably about the work. If they can't name anything, it probably isn't.
"Is there anything about how this plan came together that bothered you?" This opens the door to feeling left out or an old grudge about a decision.
"Is your team getting questions about this from above?" This surfaces when they're carrying someone else's message.
"What does this deadline mean for your team's workload?" This gets at overload, which people often won't raise on their own because it sounds like complaining.
Most of the time, this conversation will surface something, whether it's a real worry about the plan or frustration that they weren't consulted on an earlier decision. Some of that you can fix. And some people just stop, because the behavior only works when nobody names it. If you fix what they said worried them and the comments continue, the stated concern wasn’t the real one, and it’s time to start documenting.
Document your position
If you already send meeting notes, include the key fact in the recap after any meeting where this comes up: “Confirmed in today’s review: on track for a launch on October 12th, dependent on the API handoff on September 25th.”
The recap corrects the record for anyone who left with the wrong impression. If the pattern continues, it also becomes your evidence, and you’ll want evidence if you need to escalate to your manager.
If you don't usually send meeting notes, a sudden recap can look pointed. Frame it as next steps, or send it only to the people who need it. A note titled “Next steps from today’s launch readiness review” with dates and owners of action items is useful to all attendees. The key fact ("launch on October 12th, dependent on the API handoff on September 25th") sits inside it as an action item and doesn't look like a response to anyone.
Or, if the topic is not one that fits neatly into a follow-up to the group, send an email to the other person after your 1:1 along the lines of “Thanks for talking this through. To confirm, we're planning around the API handoff on September 25th. Let me know if that date moves." It documents what you both agreed to, and it's hard to object to.
Either way, keep a private log of dates, who was in the room, and the exact comments as best you can recall them.
When to escalate
If the snark happens a second time, or a third time if you're more patient, it’s time to escalate. Don't wait past this point. It’s easier to fix it early than later.
Offer specifics and a clear ask when you escalate: "This has happened three times. Here's what I've tried, and here's what I sent afterward. I need your help."
Then specify what kind of help you want. It might be advice on handling it yourself, or it might be a direct conversation with the other person.
Managers respond much better to a well-defined request than to a general complaint about someone's attitude.
Most passive-aggressive colleagues are counting on you to either stay quiet or get defensive. If you do neither, the behavior usually stops.
What's worked for you when someone took a shot at your plan in front of leadership?
The distinction between reacting and responding is the whole game, I think. The passive-aggressive comment is designed to get a reaction, and once you give one, the room stops evaluating the comment and starts evaluating you. Two small additions to your recap idea: keep the follow-up note boringly factual, no adjectives, and keep a private log with dates and who was present even before it feels serious. It is much easier to escalate later with three dated entries than with a feeling. I wrote a book called WorkWars that covers this territory, composure and documentation when a colleague keeps taking shots. Happy to share details if anyone messages me [book].