How to work with a difficult colleague without losing your cool

Most jobs are made or ruined by two or three people, and one of them is rarely your manager. It is the colleague who presents your idea as theirs in the meeting you were not invited to, or the one whose “quick question” about your work reaches the director before it reaches you, or the one who agrees to everything in the room and then does none of it.

You cannot fire them, you probably cannot avoid them, and complaining about them makes you look like the problem. What you can do is diagnose the behavior, respond in ways that change the incentives, keep a record that protects you, and know exactly when to escalate. This guide covers the four types that come up most, with wording you can use, and ends with the uncomfortable check every one of us should run: whether the difficult colleague is, this time, you.

Start by separating the person from the pattern

Before you label anyone, watch for three or four weeks and write down specific incidents. Not “Sam is undermining me” but “Tuesday: Sam told the client the delay was due to my team, without checking; the delay was caused by procurement.” Specific incidents do two things. They tell you whether there is a pattern or just a bad fortnight, and they give you something concrete to say if you ever need to raise it.

Also ask what the person is getting out of the behavior. Almost nobody is difficult for fun. Credit-takers are usually anxious about their own standing. Blockers are often protecting something they are afraid of losing. Gossips trade information because it is the only currency they have. Passive-aggressive colleagues have usually learned that direct disagreement is punished where they work. Understanding the motive does not excuse the behavior, but it points to the response most likely to change it.

The credit-taker

This colleague summarizes your analysis in the leadership meeting as if they did it, thanks “the team” for work that was yours, or quietly moves their name to the top of the deck. Sometimes it is deliberate. Often it is a habit of speaking in the first person about anything they were near.

The fix is to make attribution automatic rather than something you have to fight for.

• Send work directly to the people who need it, copying the credit-taker rather than routing it through them. Put your name in the document, on the first slide, in the file name.
• Talk about your work before they can. A two-line update to your manager on Friday (“finished the pricing model, here’s the summary”) means the version of events is already on record when the meeting happens on Monday.
• In the meeting, add rather than accuse. “To build on that, when I ran the numbers the thing that surprised me was…” reclaims ownership in a sentence, without a scene.

If it keeps happening, say something in private, once, calmly:

“In the steering meeting you presented the forecast without mentioning I built it. I’d like to be named on work I do. Can we agree that going forward?”

Most credit-takers are embarrassed enough by this to stop. The ones who are not have told you they are doing it on purpose, and that moves you to the escalation section below.

The blocker

The blocker is the person whose sign-off you need and never get. They raise a new concern each time you address the last one. They “just want to make sure we’ve thought about” a scenario nobody has raised before. Nothing they say is unreasonable in isolation; the effect is that nothing ships.

Blockers usually have a fear underneath: of being blamed if it goes wrong, of losing control of a process they built, or of a change that makes their role less central. The strategy is to make saying yes safer than saying no.

• Ask for the full list of concerns in one go, in writing: “So we can plan properly, could you send me everything you’d need to see before signing off?” A list can be worked through. An endless drip cannot.
• Time-box the decision and say who owns the risk: “We need a decision by Thursday. If there are no further concerns by then, I’ll proceed and take responsibility for the outcome.”
• Give them a visible role in the success. If their name is on the project as a reviewer, the incentive flips.
• Bring the decision to a forum where the blocker has to state their objection in front of others. Vague concerns tend to evaporate when they have to be specific in public.

If a blocker sits outside your team and their approval is genuinely required, the escalation is not “they’re being difficult,” it is “this decision has been pending for three weeks and the deadline is at risk; can you help me get it unstuck.” Frame it as a process problem and let your manager draw their own conclusions.

The gossip

The gossip knows who is leaving, who is on a warning, and what you said in your one-to-one, or a version of it. They are often warm and easy to talk to, which is exactly the problem.

The rule is simple and hard to keep: give them nothing. Not a complaint about your manager, not a comment on a colleague, not your salary, not your job search. Assume anything you say to them will be repeated with your name attached. Be friendly, be boring.

When they bring you something, do not engage with the content:

“I’d rather not get into that. How’s the Henderson project going?”

Said pleasantly, twice, and you will drop off their route. If gossip about you specifically is circulating and it is damaging, go to the source rather than the network: “I heard there’s a story going round that I’m looking for another job. That’s not right, and I’d appreciate it if you didn’t pass it on.” You do not need to prove they started it. You need them to know you are paying attention.

Where gossip crosses into something more serious, such as spreading information about someone’s health, relationships or protected characteristics, it is no longer a personality issue but potentially a conduct or harassment matter, and it belongs with your manager or HR.

The passive-aggressive colleague

This one agrees in the meeting and then misses the deadline, sends the two-word email that somehow lands like a slap, replies “fine” when it is not, or offers “help” that is actually a public correction. Confronting them directly produces “I don’t know what you mean, I was just trying to help.”

Passive aggression thrives in ambiguity, so the tactic is to remove it. Everything specific, everything written.

• After any verbal agreement, send a one-line confirmation: “Thanks, so you’ll have the draft to me by Wednesday noon.” Now the deadline is a fact, not a memory.
• When the barbed email arrives, respond to the content only, flatly and briefly. Do not match the tone and do not decode it. If they wanted to say something, they can say it plainly.
• If a pattern of missed commitments builds, address the behavior, not the attitude: “The last three handovers have come after the agreed date. What’s getting in the way, and what would make the dates workable?” This gives them a way to raise the real grievance, which is often something legitimate they did not feel able to say.

You will not fix a passive-aggressive colleague’s personality. You can make it very hard for them to hurt your work.

When to involve your manager

The general rule: try direct conversation first, once, and go to your manager when the behavior is affecting delivery, when it involves conduct rather than style, or when you have tried and it has not changed.

When you do go, bring the incident list, not the feelings. Lead with the impact on the work:

“I want to flag something that’s affecting the project. On three occasions in the last month [specific incidents]. I’ve raised it directly with [name] and it hasn’t changed. I’m not asking you to take sides, but I’d like your advice on how to handle it, and I wanted you to be aware in case it comes up.”

That framing asks for help rather than punishment, gives your manager a heads-up before the other person’s version arrives, and shows you tried to resolve it yourself. Managers dislike being asked to referee, but they dislike being blindsided more.

If the manager is part of the problem, or the difficult colleague is more senior than you, the calculation changes. Our guide to dealing with a bad manager covers that ground, including when HR is the right route and when it is not.

Protecting your own record

Difficult colleagues rarely get you fired directly. They get you a reputation for being “hard to work with,” which is fatal at promotion time and impossible to disprove because it is never said to your face. The defense is a record that speaks for itself.

• Keep your own written log of what you delivered and when, and send a short weekly summary to your manager. This is the single most protective habit in any workplace.
• Confirm agreements by email. Confirm deadlines by email. Confirm scope changes by email. Not aggressively, just consistently.
• Keep your side clean. No sarcasm in writing, no venting in chat channels, no “per my last email.” Assume every message you send will be read aloud in a meeting you are not in.
• Build relationships across the organization, not just in your team. When five people know you as reliable and pleasant, one person’s whisper campaign has nowhere to land.
• If you have to say no to a difficult colleague’s demand, do it in the way that protects you. Our piece on saying no at work has scripts for exactly that.

The check: is it you?

Every office has someone who has had a “difficult colleague” in every team they have ever worked in. Statistically, some of them are the constant.

Run this honestly. Do you find the same type of person difficult everywhere you go? Are you the one who sends the “just checking” email, or who corrects people in meetings, or who “needs to be kept in the loop” on things that are not yours? Have two different people, in two different jobs, given you feedback about tone? Do you describe most of your colleagues in terms of their flaws?

None of that makes you a villain. It might mean your standards are high and you have never been taught to hold them without bruising people, which is one of the most common developmental notes in mid-career reviews. If you recognize yourself, ask one trusted colleague, someone who has no reason to flatter you, a direct question: “Is there anything about how I work with people that I should know?” Then say thank you and do not argue with the answer.

What to do this week

Pick the one colleague who costs you the most sleep. Write down the last three specific incidents, with dates. Decide which type they are closest to and choose one tactic from that section, just one. Try it for two weeks and note what changes.

Then decide whether the situation is improving, tolerable, or worth an escalation. Most difficult-colleague problems are tolerable once you stop taking them personally and start managing the mechanics. A few are not, and for those, the record you have been keeping is what makes the conversation with your manager short, calm and effective.