Why Hostile Stakeholders Still Need Engagement

Most project managers can name the person without pausing. They stated their position early, usually in front of other people, and nothing since has moved them. Every review carries a quiet expectation that they will object again.

The instinct at that point is to reduce contact. Route the decisions through the sponsor, keep the person on the distribution list, and treat their silence as something close to acceptance. It feels efficient, and it removes an uncomfortable conversation from the week. On most projects it is also the most expensive option available.

Opposition does not remove influence, and it does not remove information. Engaging a stakeholder who opposes the project is not an attempt to convert them. It is how you find out what the objection is actually made of, while the project can still do something about it.

Opposition and influence are separate measurements

A stakeholder's authority is one thing. Their current level of support is another, and the two get confused easily, partly because a single analysis exercise tends to produce both at the same time. Somebody who has publicly opposed the work may still hold a signing authority, control access to the staff whose time the project needs, chair the forum where adoption is decided, or simply be trusted by the people who will be asked to work differently. None of that lapses because they disagree.

This is the territory the PMBOK® Guide Eighth Edition covers in Section 2.5, the Stakeholders Performance Domain, which treats stakeholder work as continuous and relational rather than as a one-off identification exercise. The practical implication is straightforward. A stakeholder map is a hypothesis with a date on it. Positions move, sometimes because circumstances change and sometimes because somebody finally asked the right question. A register does not create engagement, and a person filed as resistant in month two is not necessarily resistant in month five, or resistant to the same thing.

Silence from an opponent rarely means the objection has gone away. More often it means the objection has found another route, and that route does not run through the project manager.

Separate the objection from what it is made of

Hostile is a strong word, and it is usually applied to a position rather than to a person. A stated position is a summary. Underneath it there is normally something considerably more specific, and the appropriate response depends entirely on which of these it is.

Something concrete may be going: a budget line, a headcount, floor space, or autonomy over a process the person is accountable for. There may be direct experience of a similar change that went badly, occasionally with the same supplier. There may be a professional or regulatory obligation that the design has not yet answered. The disagreement may be about the problem rather than the solution. The person may have been excluded from a decision they reasonably believed was theirs to make. Or the objection may simply be correct, and nobody has answered it.

That last category is the one to protect. The people who object most strongly are often the ones with the most specific information about how the work will actually land, because they are the ones who will have to live with it. Resistance and operational expertise turn up in the same person far more often than stakeholder theory tends to suggest.

Three questions usually get further than a persuasion attempt. What would have to be true for this person to be right? Is the objection to the outcome, or to the route being taken towards it? And has anybody actually asked them, rather than asked about them?

Engagement is not the same as winning agreement

PMP preparation can leave candidates with the impression that the goal of engagement is to move everyone into the supportive column. On real projects that target is often unrealistic and occasionally undesirable. A finance director who thinks the business case is thin may be doing precisely the job they are paid to do.

A more useful target is frequently informed and non-obstructive. The person understands what is happening, has had the objection heard and answered where it can be answered, and has a route by which they will raise the next one early. That is a lower bar than enthusiasm and a much higher bar than silence.

The mechanism differs by approach. On predictive delivery, engagement is usually structural: named points in the schedule where the person's accountability is genuinely engaged, rather than a copy of the monthly report landing in their inbox. The risk is that engagement quietly degrades into reporting. On adaptive delivery the demonstration does much of the work, because a working increment is harder to argue with than a set of intentions, and an opponent sitting in a review will tell you what is wrong faster than any survey. On hybrid delivery two routes are normally needed rather than one: a governance route where the decision sits, and a working-level route where the operational detail lives. The common failure is having only the first.

If you want to work through this kind of judgement systematically rather than case by case, PMP® Exam Preparation covers stakeholder engagement alongside the conflict and leadership situations it usually arrives with.

A ward manager, eight weeks before go-live

A hospital trust is changing its medicines management process on three wards. One ward manager objected at the second steering group and has objected at every one since. The project manager, reasonably enough, has been routing decisions around her through the clinical director.

When training needs to be scheduled, he stops doing that and goes to the ward at the end of a late shift instead. Two things come out inside twenty minutes. The new check step falls within the handover window, when two sets of staff are already accounting to each other for every patient on the bay. And the stock the process assumes is held centrally is in fact kept in a drawer on the bay, because the central store is a four-minute walk away and nobody has made that walk in years.

Neither point changes her opinion. She still thinks the timing is wrong, and she says so at the next steering group. What changed is that a genuine operational constraint reached the project eight weeks before go-live rather than two days after it, and a route now exists for the second constraint when it appears.

That is the return on engaging somebody who opposes you. Not agreement. Earlier information, from the person best placed to hold it.

The habit this builds

For a PMP candidate, the useful move is to recognise the situation rather than to memorise a response. In the 2026 PMP Examination Content Outline, the People domain accounts for 33% of exam items, and engaging stakeholders, aligning stakeholder expectations and managing stakeholder expectations appear as three separate tasks within it. That separation is informative on its own, because it treats engagement as several different activities rather than one.

When a scenario presents a stakeholder who is blocking progress, the reflex to escalate or to persuade tends to arrive before anybody has established what the objection is about. Understanding first is not passivity. It is what makes an escalation defensible if one is still needed afterwards, and it is what stops a project manager negotiating hard over the wrong thing.

The same habit pays on a live project, though less tidily. Engagement with an opponent occasionally tells you that they were right, and that something in the design has to change. That outcome is not a failure of stakeholder management. It is most of the reason for doing it.

Andre Malowney

Interested in going further?

Stakeholder resistance rarely arrives on its own. It usually comes attached to a conflict, a governance question and a schedule pressure at the same time, and deciding which of them to address first is the part that experience teaches slowly. PMP® Exam Preparation works through those combined situations rather than isolated definitions, using cases where the right first move is genuinely arguable.

The Stakeholders Performance Domain sets out the wider engagement, communication and trust material this article draws on, and the PMBOK® Guide Eighth Edition is where to read it in full.

Ad · Amazon affiliate link.

References

A132: The PMBOK 8 Stakeholders Performance Domain: What It Really Covers
A137: When Stakeholders Disagree: What Should the PM Do First?
A139: Communication Plans That People Actually Use
A134: Power/Interest Grid vs Salience Model
A082: Tailoring Stakeholder Engagement

PMP and PMBOK are registered marks of the Project Management Institute, Inc.