Stakeholder Management vs Stakeholder Engagement
Two lines turn up in more or less every status report: stakeholder engagement, rated green, and a note that the stakeholder register is current. The second is usually true. The first is usually an inference drawn from the second, and the week that inference fails tends to be the week something arrives from a direction the register had already mapped.
The two words describe different things. Stakeholder management is the organised work a project does about the people around it: identifying who they are, analysing what they need and what influence they hold, planning how each will be communicated with, recording all of it, and monitoring whether the plan is being followed. Engagement is what exists between the project and those people: whether they involve themselves, whether they tell you things before those things become your problem, whether they will spend their own effort on your work. Management is evidenced by artefacts. Engagement is evidenced by behaviour and by nothing else.
One of them you can do at a desk
The practical difference shows up in who has to be present. A project manager can complete a full stakeholder analysis alone in an afternoon: forty names, roles, interests, influence, preferred channel, engagement approach, review date. It can be a genuinely good piece of work. It has also changed nothing about the project's relationships, because none of the forty people were involved in producing it.
Engagement needs the other party, which means it needs their time, the resource no plan ever budgets for. It is also hard to hand on. A communications lead can run a communications plan perfectly well on a project manager's behalf, while a sponsor relationship passed to somebody else comes back thinner than it went. That is why stakeholder work fails quietly at a change of project manager: the management artefacts transfer intact and the engagement does not transfer at all.
Section 2.5.1 of the PMBOK® Guide Eighth Edition sets out the key concepts under the Stakeholders domain, and it keeps the two words doing separate jobs, one naming the systematic work a project performs, the other naming the state of the relationship that work is meant to produce. Holding them apart is what stops a project reporting its own activity and calling it a result.
What tells you engagement is real
Since engagement shows up only in behaviour, it helps to know which behaviours count. Three of them are reliable.
The first is early warning. An engaged stakeholder tells you about the thing that will affect your project before it affects your project: the reorganisation being discussed upstairs, the budget about to be reallocated, the objection a colleague is drafting. A stakeholder who is merely well managed finds out when you do, often from your own bulletin.
The second is who they send. A stakeholder who cannot attend and sends somebody with the authority to decide is telling you the project matters to them. One who sends somebody to take notes is telling you the opposite, whatever the attendance record shows.
The third is when the argument happens. Engaged stakeholders argue with a plan while it is still a draft, which is inconvenient and cheap. Managed stakeholders argue with it at the approval gate, or after it, where the argument costs a re-plan. A run of frictionless approvals followed by a late objection is good evidence that the relationship was never established.
The permit that nobody saw coming
A water company was replacing domestic meters across a district, roughly nine thousand properties over fourteen months, through a rolling programme of street works. The stakeholder register was thorough. The local authority highways team was on it, correctly assessed as high influence, with an engagement approach of monthly programme updates by email, sent without fail.
Three weeks before the second phase, the highways permit for a group of streets was refused. The reason was a resurfacing programme covering the same streets that summer, published by the authority a year earlier, which nobody at the water company had read because reading it was not part of anyone's plan. The monthly update had been arriving in an inbox that received forty others like it.
The repair cost one morning. The project manager drove to the highways depot and spent two hours with the officer who issued the permits, and came away with the resurfacing schedule marked up, an informal understanding that the two programmes would share a sequence where they overlapped, and a name and a number. The register did not change. Three streets moved in the programme, one phase was resequenced around the resurfacing, and no permit was refused after that. The engagement approach in the plan still reads monthly programme updates, which is fine, because the plan was never the thing that had been missing.
For a PMP® candidate, the distinction earns its place by changing what a situation is asking. A project with a complete register, a communications plan and a stakeholder who has just escalated over the project manager's head is not describing a documentation failure, and adding a stakeholder review to the plan answers a question nobody asked. Which of the two is thin decides the response, because the answer to weak management is an artefact and the answer to weak engagement is a conversation somebody has to go and have. Telling them apart in a situation built to look like either one takes rehearsal, and a structured PMP exam preparation course is where that rehearsal usually happens.
Testing it takes five minutes. Take the five stakeholders who could most damage the work and ask, for each one, when they last told you something you did not already know. If the answer for three of them is never, the engagement is not there, whatever the register says, and the remedy is a visit rather than a revision. Going to where somebody works is worth an hour of meeting-room time, because constraints are usually visible at the place they apply and invisible everywhere else.
Interested in going further?
A complete stakeholder plan and a project that nobody tells anything to can sit side by side for months before the gap shows. Omega's PMP® Exam Preparation works through stakeholder situations where the right move depends on which of the two has gone missing.
The Stakeholders Performance Domain and the key concepts under it are set out in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A135: Stakeholder Power Is Not the Same as Engagement
A082: Tailoring Stakeholder Engagement
A141: Tailoring Stakeholder Engagement for Different Contexts
A132: The PMBOK 8 Stakeholders Performance Domain: What It Really Covers
A137: When Stakeholders Disagree: What Should the PM Do First?
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
