Vigneshwar’s blog

The difficult person is not the problem

Every team has one. The person who derails meetings, dismisses ideas, takes credit, assigns blame, and leaves a trail of friction wherever they go. Most advice on this topic is either too soft to be useful or too aggressive to be safe. Neither helps you operate effectively in the environment you’re actually in.

The real question is not how to change them. It is how to stay effective despite them.


Context

Difficult people at work fall into a few recognizable patterns: the credit-taker, the blame-shifter, the meeting-hijacker, the chronic underminer, the passive blocker. The form varies. The underlying dynamic is usually the same — someone whose behaviour consistently creates cost for the people around them, often without consequence.

What makes this hard is not the behaviour itself. It is that most of it is ambiguous enough to survive scrutiny. Nothing is provably wrong. Everything is slightly off.


Insight

The mistake most people make is trying to solve the person. You cannot. You do not have that lever.

What you can control is the system around the interaction — the documentation, the structure, the visibility, and your own response pattern. Difficult people tend to operate in ambiguity: unclear ownership, undocumented decisions, private conversations, and rooms without witnesses. Remove the ambiguity, and most of the behaviour loses its grip.

There is a second insight worth naming: not every difficult person is the same problem. Some are insecure. Some are misaligned. Some are genuinely adversarial. Diagnosing which one you are dealing with changes the response entirely.


Implication

If you respond emotionally, you hand them the frame. You become the difficult one.

If you avoid them entirely, the friction does not disappear — it just moves underground and resurfaces at the worst time.

The operator’s job is to stay clear-headed about what is actually at stake, document the pattern without drama, and design the interaction conditions so the behaviour has fewer places to hide. This is not about winning. It is about maintaining your effectiveness in an environment that has a tax on it.


Action

Diagnose before you act. Is this person insecure, misaligned, or adversarial? The response to each is different. Treating insecurity as adversarial escalates unnecessarily. Treating adversarial behaviour as insecurity gets you managed.

Move conversations to visible surfaces. Verbal agreements disappear. Written ones don’t. Follow up every consequential conversation with a short written summary — not as a gotcha, but as a record. Do it consistently so it becomes your operating style, not a signal that you are building a case.

Name the behaviour, not the person. “In the last two reviews, the feedback changed direction after decisions were made” is something that can be addressed. “You always undermine the work” is something that gets denied and then turned back on you.

Remove ambiguity from shared work. Unclear ownership is where difficult behaviour thrives. Define who owns what, in writing, before work begins. When accountability is explicit, blame-shifting has nowhere to go.

Control your response pattern. The most effective move in most interactions with difficult people is a shorter, calmer response than they expected. It does not give them material to work with. It signals that you are not rattled. Over time, this changes the dynamic more than any confrontation would.

Know when to escalate — and do it cleanly. If the behaviour is creating material cost to the work, escalate as a business problem, not a personal one. “This pattern is affecting delivery timelines and team clarity” is a different conversation than “I find this person difficult to work with.”


The org’s responsibility — and yours within it

There is a version of this conversation that individuals are not equipped to resolve. Persistent, pattern-level difficult behaviour — the kind that survives escalation, outlasts team changes, and continues because nothing structural happens — is an org failure, not a personal one. The org either does not see it, does not believe it, or has decided the cost of acting is higher than the cost of absorbing it.

Your role within that is limited but not zero. Document the pattern objectively and escalate it as a business problem with evidence. Do it once, clearly, to the right person. Then do it again if it resurfaces. Beyond that, you have done what you can. The decision to act belongs to leadership, and if they consistently choose not to, that is information about the environment you are operating in — information worth having.

What you cannot do is carry the org’s failure as your personal burden. You are not responsible for fixing what the system will not fix. You are responsible for how you operate within it.


After you have done what you must

At some point, you have diagnosed the person, structured the interactions, documented the pattern, and escalated cleanly. You have done your part. What comes next is the harder discipline: deliver anyway.

Not despite them as a point of pride. Not in spite of them as a performance. Simply — the work is yours, and it needs to get done. The presence of a difficult person in your orbit does not change what you committed to deliver. It changes the conditions. Conditions are always imperfect.

The operators who build lasting credibility are not the ones who worked in clean environments. They are the ones who delivered in difficult ones and did not make the difficulty the story.

Do what you must. Then focus entirely on what you can control: the quality and consistency of your own output. That is the only thing that compounds.


Handle the person as much as the situation allows. Then stop measuring yourself against them. Measure yourself against the work.