Difficult stakeholders, and what each one needs

What difficult behaviour tells you

A stakeholder who blocks, ghosts or nitpicks is treated by most plans as friction to be managed. The more useful reading is diagnostic: the behaviour tells you what they hold at stake, and the response that works depends entirely on which of 4 modes you are looking at. Applying one universal answer, usually "more engagement", is how a workable situation becomes a difficult relationship.

The modes are opposed, disengaged, overloaded and scarred. The decision tree separates them on observable behaviour, and each has a matching response.

The decision tree

What you see	The separating question	The diagnosis	The response that fits
Objects in the room, argues against the project, recruits others	Do their objections name a real cost they will bear?	Opposed	Put the objection on the table while decisions are still open; trade where trading is possible; escalate cleanly where it is not
Silent, absent, delegates everything downward	Have they ever said no, or do they simply never say anything?	Disengaged	Shrink the ask to one specific decision, taken to the channel they already use; if they still do not engage, record Inform and stop performing Involve
Willing in principle, cancels in practice	Do they engage when the ask is small enough?	Overloaded	Cut the format cost: written pre-reads, decisions by exception, short fixed slots reserved for the decisions that need them
Resists this project, but supported something similar before	What happened last time, and did your organisation keep its promises?	Scarred	Name the history plainly, acknowledge the specific failure, and rebuild with small commitments that are kept

The modes combine. The veteran who has seen this fail before and has no room in their calendar is scarred and overloaded at once, and the response has to respect both. Misdiagnosis is expensive in a specific way: a charm offensive aimed at an opposed stakeholder confirms their read of you as a salesman, and piling process onto a scarred one re-enacts the original injury.

The signs that resistance is present at all

The tree above assumes you have noticed something. Active opposition is easy to notice, which is exactly why it is rarely the version that damages a project. The dangerous resistance is quiet.

The Teal Book, the UK government's project delivery standard, lists 4 signs worth watching for:

• unwillingness to engage: missing meetings and events, not responding to requests, silence
• attacking the detail: asking for more and more detail, finding multiple flaws to undermine the work, inflating minor issues to discredit the whole concept
• promising action, then doing nothing
• negative briefing: internally, criticising the work to others or spreading unfounded rumours; externally, private briefings with other stakeholders, comments on social media, unattributed press stories

Its own caution belongs with the list, and it is the same caution the 4 modes exist to enforce. These signs have innocent explanations. People miss meetings because of workload or something happening in their life. Critical comment frequently reflects genuine concern and a wish to get the work right. Where you are in doubt, the Teal Book's instruction is to ask, or to seek other feedback, rather than to infer.

Read against the modes, the signs are diagnostic to different degrees:

The sign	What it usually means
Silence and non-attendance	Any of disengaged, overloaded, or opposed without appetite for the argument. The least informative sign on its own
Attacking the detail	Opposed, or scarred and checking because a previous promise failed. Sometimes a careful person doing their job
Promising action, then nothing	Usually overloaded. Occasionally opposed, avoiding an open refusal
Negative briefing	Opposed, reliably. It is the one sign that rarely has an innocent reading

Attacking the detail deserves its own note, because the decision tree above has no row for it and teams routinely file it as personality. Someone who cannot stop the work directly can often slow it to a halt through legitimate-looking scrutiny, and the tell is proportion. Questions that would change a decision are engagement. Questions that multiply regardless of the answers are resistance wearing the costume of diligence.

The Teal Book also notes that growing signs of resistance usually mean more, or different, engagement is needed, and not always with the person concerned. Sometimes the necessary conversation is with whoever they have been briefing.

Opposed

Someone who bears the costs of your project has a legitimate reason to oppose it. Engagement does not mean converting them. It means their objection enters the decision while the decision is still open, which is the honesty the IAP2 levels in the stakeholder engagement framework are for.

Two things follow. First, ask what they would need changed to make the project survivable for them; sometimes the trade is small and real. Second, when the opposition is irreconcilable, escalate it as a decision rather than a personality problem: the sponsor weighs the cost of proceeding against a named, on-record objection. The distinction between engaging someone and managing them is covered in engagement versus management, and it is sharpest exactly here.

Disengaged

Silence is rarely opposition. Most disengaged stakeholders are not withholding judgment; they are spending their attention somewhere their own performance is measured. Diagnose the size of your ask before their character.

The fix is to shrink the ask until it fits. "Attend the monthly steering group" becomes "approve or amend this one paragraph by Thursday". Take it to the channel they already read, from the person they already answer. If they still do not engage after two honest attempts, write Inform beside their row and behave accordingly. Relabelling silence as consultation is the failure the framework's review habit exists to catch.

Overloaded

The overloaded stakeholder is the one teams misread most often. Their cancellations look like low priority. The reality is high priority with no bandwidth, and the response is to protect their involvement rather than protest it.

Reserve them for the 2 or 3 decisions that genuinely need their authority, and remove every other demand on their attention: written pre-reads instead of live walkthroughs, decisions by exception instead of standing meetings, short fixed slots instead of open-ended ones. The trap is moralising about their diary. Their time is the scarce resource your project is asking for, and spending it well is your job, not theirs.

Scarred

Organisations underweight their own history. If the last programme promised simplification and delivered redundancy, the people affected remember, and their resistance to your project is rational memory rather than obstinacy.

The response is to name the history explicitly: what was promised last time, what actually happened, and what is structurally different now. Then rebuild through small kept commitments, because trust only accrues through signals that were kept, and the first ones need to be small enough to be kept certainly. A scarred stakeholder who watches one modest promise get kept becomes your most rigorous ally, because they are the person in the room who checks.

What makes all 4 worse

The universal mistakes are the same regardless of mode: treating more engagement as the answer, running charm offensives in place of trades, escalating around the person to their boss without telling them, which works once and poisons the well, and relabelling whatever silence you get as consent. Each saves a conversation now at the cost of the relationship later.

The role boundaries matter too. Whose job it is to hold the escalated trade-off is covered in stakeholder engagement roles, and it is usually the sponsor, not the project manager.

Name the stakeholder you are avoiding

Name the stakeholder you are currently avoiding. Write their mode, or modes, with the behavioural evidence beside it. Then take the smallest first move that matches: the open-objection conversation for opposed, the one-paragraph approval for disengaged, the protected calendar slot for overloaded, the named-history conversation for scarred. One move, this week, is worth a quarterly plan for their feelings.