You see the name on the meeting invite before you see the subject line. Your shoulders tighten. You haven’t even opened the calendar event yet and you’re already rehearsing how to phrase things carefully, already bracing for the tone, already tired. If you’ve felt that specific pre-emptive dread about one particular person, you already know this isn’t really about a single bad meeting. It’s cumulative, and it’s exhausting in a way that’s hard to explain to someone who doesn’t work with that person.
Most advice for this situation is the same regardless of what’s actually going on: be patient, stay professional, kill them with kindness, give them the benefit of the doubt. That advice isn’t wrong exactly, but it’s incomplete in a way that causes real damage, because it assumes all difficult coworkers are the same problem wearing different faces. They’re not. A coworker who’s short with you because they’re drowning in their own workload needs something completely different from a coworker who is quietly taking credit for your work in front of your manager. Responding to both with the same “be nicer, be more patient” strategy fails the second person badly and is honestly overkill for the first.
Why does the same advice not work on every difficult coworker?
Because “difficult” is not one behavior, it’s a category that contains at least four fairly distinct patterns, and each one has a different cause and a different fix. Treating them identically means you either under-react to something that’s actually serious, or over-react to something that was never personal in the first place.
The useful first move, before you decide how to handle anyone, is diagnosis. Not “is this person difficult,” which you already know, but “which kind of difficult is this.” That single question changes almost everything about what you do next.
What are the four real patterns behind difficult behavior?
Most workplace friction that gets labeled “this person is difficult” sorts into one of four buckets. Very little of it is genuinely novel once you look closely.
The overwhelmed and reactive coworker
This person snaps in meetings, answers messages tersely, seems irritated by questions that used to be fine. The key marker is that it’s situational and not targeted: they’re short with everyone right now, not specifically with you, and it tends to track with an obviously heavy period — a deadline, a headcount gap, a personal situation bleeding into work. This is not malice. It’s someone underwater who doesn’t have the bandwidth to manage their tone right now.
The appropriate response here is usually restraint, not escalation. A short, direct, low-stakes conversation (“hey, I noticed things feel tense, is everything okay on your end”) often does more good than any formal process, and sometimes the honest answer is that this resolves on its own once the pressure lifts. Escalating this to a manager or treating it as a conduct issue is usually disproportionate and can burn a relationship that didn’t need burning.
The chronically negative or critical coworker
This is a general disposition rather than a targeted behavior. They find the problem in every plan, the flaw in every proposal, the reason something won’t work. It can feel personal because you’re often on the receiving end of it, but it’s usually not about you specifically — this is how they show up for everyone and everything.
The useful move is not trying to fix their outlook. You will not talk a chronically critical person into being upbeat, and trying is a long, frustrating project with a poor success rate. What works better is limiting your exposure where you reasonably can, and consciously not absorbing their negativity as accurate personal feedback about you or your work. Hear the specific critique if there’s something useful in it, and let the general tone slide off rather than treating it as a verdict.
The actively undermining coworker
This is the serious one, and it’s different in kind from the other three. This person takes credit for your work, leaves you out of information you needed, undermines you in front of others, or otherwise works against your interests on purpose. This is not a mood or a disposition problem — it’s adversarial, whether or not they’d ever frame it that way to your face.
Patience is not the right tool here, and treating it like the overwhelmed-coworker case will just let it continue. This pattern calls for documentation, directness about specific incidents, and — if it continues — involving a manager with facts rather than feelings. More on exactly how below.
The style clash
Nobody is wrong here. This is the coworker who wants everything in writing when you prefer a quick call, who needs three days’ notice when you’re comfortable improvising, who processes out loud when you need quiet to think. Left alone, style clashes don’t resolve — they just generate quiet resentment on both sides, because each person keeps interpreting the other’s normal working style as inconsiderate.
What actually helps is naming it explicitly, out loud, as a difference rather than a fault: “I’ve noticed I like to think out loud and you seem to prefer time to process first — can we figure out a way that works for both of us.” That one conversation often does more than months of quiet irritation.
How do you know which pattern you’re actually dealing with?
Ask yourself two questions. Is this behavior consistent across time, or does it track with an obviously stressful period for them? And is it aimed specifically at you, or is it how they treat everyone? Overwhelmed-and-reactive is usually recent and universal. Chronically negative is usually long-standing and universal. Undermining is usually specific to you and tends to intensify rather than resolve. Style clash is usually consistent but symmetrical — you’re both a little frustrated with each other, not just you with them.
If you’re honestly unsure, that uncertainty is itself useful information: it usually means you’re not yet at the undermining category, because that one tends to leave a fairly clear trail once you start paying attention.
How do you actually raise the behavior with someone?
This is the step almost everyone skips. It’s uncomfortable, so people go straight to quietly resenting the person, venting to other coworkers, or escalating to a manager without ever having said anything directly to the person involved. That skip is understandable, but it means the person often has no real idea there’s a problem, and it means when you do escalate, it looks like the first time this has ever come up.
A direct conversation works best when it describes the specific impact of a specific behavior, not the person’s character. “You’re rude” invites defensiveness and rarely changes anything. “When you rewrote my section without flagging it to me, I ended up presenting numbers I hadn’t checked” is factual, specific, and much harder to argue with, because it isn’t a character judgment — it’s a description of what happened and what it cost.
Keep it short. State the behavior, state the impact, state what you’d like instead. Don’t pad it with apologies for bringing it up, and don’t let it turn into a personality debate. You’re not trying to win an argument about who they are; you’re trying to change one specific pattern.
Most people don’t skip this step because they don’t know how to do it — they skip it because it’s uncomfortable, and resentment feels easier in the moment than the conversation does.
When and how should you document what’s happening?
Documentation matters specifically for the undermining pattern. You don’t need a paper trail for someone who’s short-tempered during a hard month, but if someone is taking credit for your work or working against you, memory and feelings won’t carry the conversation if it ever needs to go further.
Keep it factual and boring: date, what happened, who else was present, and what the actual impact was. “March 4, team meeting, presented my Q1 analysis as their own work, manager and two other team members present” is useful. “They’ve been awful to me for months” is not, even if it’s true, because it can’t be verified or acted on the same way. Save relevant emails and messages as they happen rather than trying to reconstruct them later from memory.
How much of this is actually your job to fix?
Not much, and this is worth sitting with. You control your own responses, your own boundaries, and how much of someone else’s behavior you choose to absorb. You do not control another adult’s mood, disposition, or decision to undermine you. Trying to manage someone else’s temperament — cheering up the chronically negative person, walking on eggshells around the overwhelmed one indefinitely, hoping the undermining person will eventually come around — is usually a losing, exhausting project, because you’re trying to change something that was never yours to change.
This distinction is what keeps the whole approach sane. Your job is to respond well, set clear limits, and protect your own work. It is not to fix another person’s disposition, and treating it as your responsibility is a fast route to burnout with nothing to show for it.
When does it make sense to involve a manager?
Mainly for the undermining pattern, and mainly once you have specific, factual incidents rather than a general impression. A manager can act on “they presented my analysis as their own in the March 4 meeting, and it affected how my contribution to the project was perceived.” A manager has a much harder time acting on “they’re just difficult to work with,” because there’s nothing concrete to respond to.
Frame it around impact on the work, not personality. You’re not asking your manager to referee whether someone is a nice person — you’re flagging a pattern that’s affecting outcomes, attribution, or your ability to do your job, and you have specifics to back it up. That framing gets taken seriously far more often than a personality complaint does.
How do you protect your own work when someone is working against you?
Be visible about your own contributions, factually and without it turning into a defensive campaign. Send the recap email after the meeting. Put your name on the doc. Say “building on the analysis I put together last week” in the meeting rather than assuming credit will sort itself out. This isn’t about grandstanding — it’s about not leaving your work’s authorship entirely dependent on someone else’s account of who did what.
Don’t rely solely on the undermining coworker’s version of shared work reaching anyone accurately. If they’re the one summarizing a project to leadership, make sure your own contribution is visible somewhere else too — in the shared doc, in your own updates, in a direct conversation with your manager. This is protective, not petty.
Can you just avoid a difficult coworker instead of dealing with them?
Sometimes, and where the structure of the job allows it, reducing unnecessary contact with a chronically difficult person is a completely reasonable move. If you don’t need to be in every meeting they’re in, or you can route a request through someone else without it looking strange, do that. This is different from avoiding a working relationship you genuinely need to function in your role — that kind of avoidance just delays a conversation you’ll eventually have to have anyway, usually under worse circumstances.
The test is whether you’re limiting exposure to something optional, or dodging something necessary. The first is sensible self-management. The second tends to make the underlying problem harder to solve later, not easier.
What happens if you just put up with it indefinitely?
It tends to continue, and often it escalates, because nothing about staying silent signals to the other person that anything needs to change. If the pattern is overwhelmed-and-reactive, silence might be fine — it may resolve on its own. But for chronic negativity or active undermining, silence usually just confirms to the other person, consciously or not, that the behavior costs them nothing.
There’s a real cost to indefinite tolerance, and it’s not abstract — it’s the meetings you dread, the work you second-guess, the energy that goes into managing your own reactions instead of doing your job. That cost accumulates whether or not you ever name it out loud.
What if you’ve tried everything and it still isn’t getting better?
This happens, and it’s worth naming honestly rather than continuing to try indefinitely on the assumption that one more attempt will finally land. If you’ve had the direct conversation, adjusted your own exposure where you could, documented what needed documenting, and involved a manager where appropriate — and the pattern persists — that’s useful information, not a personal failure. Some situations genuinely don’t resolve no matter how well you handle them.
At that point, the relevant skill shifts from diagnosis to holding a line, which is really about protecting your own time and workload regardless of how the other person responds — see how to say no at work for the mechanics of that. And for the undermining pattern specifically, if it’s persistent and well-documented, it becomes a legitimate matter for HR rather than something to keep managing solo. In extreme, unresolved cases, it’s also fair to weigh whether the role or the team is worth staying in — that’s not giving up, it’s recognizing a fair attempt was made and the outcome is the outcome.
When the pattern is chronic and the workload keeps expanding to match it, making the trade-off visible is the next skill worth having.
Acas explains how grievance procedures are meant to work, which matters for the undermining case specifically.
Frequently asked questions
What if I misdiagnose which pattern I’m dealing with?
It’s not a one-time judgment call — keep watching. If you treat someone as overwhelmed-and-reactive and give them patience, but the sharpness continues well past any obvious pressure and starts looking targeted at you specifically, that’s new information. Adjust your response as the pattern clarifies rather than locking in your first read.
Is it okay to talk to other coworkers about a difficult person?
Venting occasionally is human, but there’s a difference between processing something with one trusted person and building a running commentary that spreads through the team. The second version tends to make you look like part of the problem, and it doesn’t replace the direct conversation you still need to have.
What if the difficult coworker is more senior than me?
The diagnostic still applies, but the direct-conversation step often needs more care in framing, and documentation matters more, not less, because the power imbalance makes it harder to be heard without specifics. Involving your manager sooner is also more reasonable in this case than it would be with a peer.
How long should I wait before raising something directly?
For a single bad interaction, give it a little room — everyone has an off day. For a repeated pattern, waiting rarely improves your position. If you can point to two or three concrete instances, you already have enough to raise it.
What if I raise it and their behavior gets worse instead of better?
That’s meaningful information, particularly for the undermining pattern. A reasonable response to a calm, specific conversation is some acknowledgment or change, even a small one. A response of increased hostility or retaliation is itself worth documenting and is a stronger reason to involve a manager.
Can a style clash turn into something more serious over time?
Yes, if it’s never named. Unaddressed style friction tends to curdle into genuine resentment on both sides, and resentment can start looking a lot like the negativity or undermining patterns even when that was never the original issue. This is exactly why naming it early, plainly, matters.