Handle Difficult People Smartly

1Name the pattern, not the person's soul

Calling someone 'toxic' or 'impossible' freezes the problem as identity. Naming the pattern — interrupting every update, reneging on agreed scope, looping the same complaint without an ask — keeps the problem changeable.

In a Bengaluru engineering sync, 'Ravi is difficult' helps nobody prepare. 'In the last three standups, Ravi has redirected the update into a side debate before blockers are heard' is a pattern you can address.

Patterns are dated and countable. If you cannot point to two or three instances, you may be reacting to one bad day — treat that as a single feedback conversation, not a difficult-person strategy.

No diagram — the move is verbal: swap an identity label for a dated, countable behaviour. 'He is impossible' freezes the problem; 'scope changed live in the last two client calls' can be addressed. The identity-vs-pattern table carries the rewrites.

2State the boundary line you need

A boundary is a clear line about what you will and will not do in the interaction — not a speech about who they are. 'I can discuss the scope change after standup, not during others' updates' is a boundary. 'Stop being so aggressive' is a demand with no edge.

Good boundary lines are short, behavioural, and about the next occurrence. They sound calm even when the content is firm, because volume is not what makes a boundary real.

In a Mumbai client-services pod, a useful line is often about channel: 'If the feedback is about my deliverable, please bring it to me directly before the group thread.' That protects both the work and the relationship.

No diagram — a boundary is a sentence about the next occurrence: short, behavioural, calm. 'I can discuss the scope change after standup, not during others' updates.' The boundary-lines table carries the lines.

3Grey-rock bait; engage when the work needs it

Not every jab deserves a full reply. Grey-rock means brief, neutral, non-entertaining responses to bait — 'Noted', 'Happy to take that offline', one factual line — so the bait earns no show.

Engage when the content is about real work: a wrong figure, a blocked decision, a client risk. Grey-rocking a genuine work conflict looks like avoidance and can hurt the team.

In a Hyderabad standup, needling about your 'always late updates' is bait if it is performance. A question about whether the blocker is still open is work — answer it. The test: does a short factual reply move the project, or only feed the scene?

Figure. The test that picks the response. If a short factual reply would move the project, engage with the one fact. If the remark only feeds the scene, grey-rock it — brief, neutral, nothing to perform against.

4Escalate with facts and asks, not venting

Escalation is a structured ask to someone who can change the system — usually your manager or theirs — not a gossip tour of peers. Bring dates, quotes, impact, and what you have already tried.

A clean escalate in an Indian IT services setting sounds like: 'On 12 and 19 June, agreed scope was changed live on the client call after we had locked it. I asked privately on both days for a pre-call align. I need your help requiring pre-call scope flags.'

Venting to random peers feels like support and often becomes a second problem. One factual CC or one manager conversation beats a whisper network that the other person eventually hears without a path to fix.

Figure. Escalation is a package, not a vent: dated instances, what you already tried, the impact, the ask. On 12 and 19 June, agreed scope was changed live after it was locked; a private pre-call align was asked both days; the ask is requiring pre-call scope flags.

Clean escalation pack

1. Dates and instancesTwo or three dated examples, not a mood summary.
2. What you already triedPrivate ask, boundary line, offline conversation — show the ladder.
3. ImpactClient, sprint, or people cost in plain terms.
4. The askWhat you need the escalated person to do — a rule, a mediation, a reassignment.

5Protect your energy — you need not win every exchange

Some patterns will not resolve in one meeting, and treating every jab as a trial you must win burns the week. Protecting energy means choosing which hills are work-critical and which are ego theatre.

Useful protection looks ordinary: shorter replies, fewer after-hours debates, taking walks between heated calls, declining optional forums where the pattern thrives. It is not silent suffering — it is budget.

In a Noida shared-services team, the person who answers every sarcastic remark in Slack often looks engaged and leaves exhausted. The charismatic move is often the boring one: answer the work question, skip the performance.

No diagram — the budget is a set of choices, not a chart: answer the work ask and skip the jab, park the 8 pm thread until morning, decline the forums where the pattern thrives. The energy-budget table carries the trades.

6Script the boundary line before the meeting

Under pressure, people either freeze or over-explain. A two-line script written before the meeting — pattern in one sentence, boundary in one sentence — is what keeps your voice steady when the room heats.

Write it literally. 'In the last two client calls, scope changed live. Going forward I need a five-minute pre-align before we join the client; I will not confirm new scope on the call without that.' Practice once out loud.

In a Pune vendor review, the script also stops you from collecting new grievances mid-meeting. You came with one pattern and one ask; stay with that package unless a new fact truly changes the work.

Figure. Write two sentences before the meeting: the pattern in one, the boundary in one. 'In the last two client calls, scope changed live. Going forward I need a five-minute pre-align before we join the client.' Say it once out loud so the voice stays on that package.

Pre-meeting script

1. Write the pattern sentenceOne dated, countable behaviour — not a character label.
2. Write the boundary sentenceWhat you need on the next occurrence, in behavioural terms.
3. Say it once out loudHearing your own voice reduces the chance you soften into fog under pressure.
4. Decide grey-rock vs escalate triggersKnow in advance what you will not debate in the room.