Managing Stakeholder Engagement Is a Continuous Job
The clearest sign that engagement has lapsed is hearing a stakeholder describe your project accurately, in the words you used at kick-off, nine months after those words stopped being true. Nobody misled them. The design moved, the sequence moved, two assumptions turned out differently, and the version of the project living in their head is the one they were handed and never had updated.
Active engagement during delivery is the work of keeping that gap closed. It has three parts, and they recur every few weeks for as long as the project runs: re-telling the project as it currently stands, surfacing concerns while they are still questions, and renegotiating expectations when something has changed enough to warrant it. None of the three appears in a plan as a task, which is why all three are the first to go when delivery gets busy.
Expectations drift without anyone being careless
Two mechanisms do most of the drifting. The first is ordinary design evolution. A decision taken inside the team in week fourteen, entirely correctly, changes what a stakeholder will eventually receive, and the team absorbs it so completely that nobody thinks to say it out loud to anyone outside. Everyone in the room updated at the same moment, so the updating feels as though it has already happened.
The second is the distance between a project's language and a stakeholder's stake. A status line reporting that the interface design has been simplified is accurate and tells an operations manager nothing, because her question is whether her team still needs the second screen on the packing bench. The information went out. The translation did not. Across nine months, a stakeholder receiving twenty accurate reports can finish up materially misinformed about the one thing they care about.
What it actually takes up, week to week
Section 2.5.2 of the PMBOK® Guide Eighth Edition carries Manage Stakeholder Engagement among the processes in the Stakeholders domain, and what it describes is nearer to a standing obligation than a scheduled activity: keeping people's understanding of the project matched to the project as it stands today.
Re-telling is the cheapest part and the most neglected. Every couple of months a stakeholder should hear the project described from the start in three minutes, with whatever has changed since they last heard it named explicitly. Almost nobody asks for this, because asking implies they should have been keeping up, so it has to be offered.
Surfacing concerns means going after what people have not said. A stakeholder with a reservation keeps it to themselves while it still feels like a doubt and states it publicly once it has hardened into a position, and the interval between those two states is where a project manager can still do something useful. The question that works is narrow and slightly leading: what about this is going to give you trouble? Asking whether somebody is happy invites the answer yes.
Renegotiating is the part people avoid, because it feels like an admission. When a project has changed enough to alter what a stakeholder receives, that change has to be put to them as a change, with whatever options remain attached to it. Sending it as an update and hoping it lands is a decision to find out later what they made of it.
Eleven weeks of knowing
A life sciences company was installing a new packaging line at a UK site. The validation approach had been agreed at kick-off with the site quality lead, built on the protocols used for a comparable line two years earlier, which suited everybody: known documents, known effort, a known timeline.
In month six the vendor's control system turned out to differ enough from the earlier one that a straight reuse of those protocols would not stand up. The project team understood this in the week it emerged and then spent eleven weeks working out what the replacement protocols should contain, which was sensible engineering. The quality lead found out when the draft protocols arrived for review.
Her response was conservative and entirely defensible. She required additional qualification runs and a longer review, adding about five weeks. Told in the first week of those eleven, she had options that had expired by the time she was asked: a phased protocol approach she had used before, and an early conversation with the auditor about what evidence would satisfy them. Neither was open at draft review.
The technical problem cost very little. The expense was eleven weeks of a stakeholder working from a version of the project that had stopped being true, while the people who knew were busy solving something else.
For a PMP® candidate, the thing worth carrying is that information has a timing requirement as well as an accuracy requirement. A situation in which the project manager issued accurate reports and the stakeholder was surprised anyway is describing an engagement failure, and answering it with another report or a wider distribution list misses what happened. Before settling on a response, ask what the stakeholder needed in order to act and when they needed it. A structured PMP exam preparation course will put situations in front of you where the reporting looks impeccable and the engagement has still failed.
On a live project, one change does most of the work. When something shifts that affects what a stakeholder will receive, tell the two or three people it affects that week, by phone, before it appears in a report. It takes twenty minutes and it turns a piece of news into a conversation they can still do something with. Everything else in engagement is a refinement of that.
Interested in going further?
Knowing that a stakeholder should have been told sooner is easy in hindsight and hard in the week it matters, when the team is still working the problem. Omega's PMP® Exam Preparation works through situations where the timing of the conversation is the decision.
Manage Stakeholder Engagement sits with the other stakeholder processes in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A132: The PMBOK 8 Stakeholders Performance Domain: What It Really Covers
A133: Stakeholder Management vs Stakeholder Engagement
A134: Power/Interest Grid vs Salience Model
A135: Stakeholder Power Is Not the Same as Engagement
A136: Why Hostile Stakeholders Still Need Engagement
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
