Difficult stakeholders take many forms: hostile, disengaged, scope-creeping, micro-managing, undermining, indecisive.
Diagnose first. Difficult behaviour often signals unmet needs:
- Hostile — feels their concerns aren't heard, feels threatened by the change.
- Disengaged — doesn't see value, has competing priorities.
- Scope-creeping — has unmet needs the original scope missed.
- Micro-managing — doesn't trust the team or feels accountable for outcomes.
- Undermining — political reasons, lost a battle earlier.
- Indecisive — overwhelmed, lacks authority, fears blame.
The right response depends on the diagnosis.
Strategies:
For hostility:
- Engage 1:1 outside meetings. Listen for the underlying concern.
- Acknowledge the concern, even if you can't satisfy it.
- Find common ground — they want the project to succeed too, just differently.
- If they have a legitimate concern, address it.
For disengagement:
- Find their personal stake. What's in it for them?
- Highlight relevant features, demos that touch their world.
- Sometimes accept low engagement; route around with proxies.
For scope creep:
- Acknowledge new needs as legitimate.
- Run them through change control; defer to Phase 2 with explicit commitment.
- Don't dismiss; the underlying need is usually real.
For micro-management:
- Increase visibility — more dashboards, more updates, more demos.
- They want control because they don't trust; build trust.
- Set clear escalation paths so they know when they need to weigh in.
For undermining:
- Address directly in private: "I've noticed X — what's going on?"
- Bring conflict to the sponsor if it's hurting the project.
- Sometimes politics requires accepting an adversary; minimise their leverage.
For indecisiveness:
- Frame decisions with clear options and recommendations.
- Provide a deadline; if not decided, default applies.
- Escalate to a higher level if a decision is genuinely critical and stuck.
General principles:
- Don't take it personally. They're behaving the way they're incentivised to.
- Lead with curiosity, not judgement. Ask why; understand before reacting.
- Document interactions. When stakeholders are difficult, paper trails matter.
- Engage their boss when needed. Sometimes only the sponsor can move them.
- Know when to walk. Some stakeholders sabotage projects — escalate, don't try to win them alone.
The hardest case: a stakeholder who agrees in meetings then undermines outside them. Hard to address; eventually the sponsor must intervene.
A senior consultant treats difficult stakeholders as a normal part of project work. Most projects have at least one. The skill is reading the situation and applying the right response.