Stakeholder Management: Analysis, Engagement and the Communication Plan

Projects rarely fail on technical grounds. They fail because someone with the power to stop them was surprised, ignored, or engaged too late. Stakeholder management is the discipline of finding those people early, understanding what they need, and deliberately moving them to the level of engagement the project requires.

The PMBOK® Guide (8th edition) treats stakeholders as a performance domain in its own right: effective engagement is an outcome you plan for and measure, not a by-product of sending status reports.

Who counts as a stakeholder?

Anyone who can affect the project, is affected by it, or believes they are. The last group matters most — perceived impact drives behaviour as strongly as real impact.

The stakeholder management process

1. 1Identify — brainstorm with the sponsor and team, review the charter, org charts, contracts and past lessons learned. Keep asking: who else will notice when this changes?
2. 2Analyse — record each stakeholder's interest, influence, attitude, and what they want from the project. Prioritise using a grid or salience model.
3. 3Plan engagement — decide the desired engagement level for each priority stakeholder, the gap from today, and the actions and communications that close it.
4. 4Engage — run the plan: one-to-ones, workshops, demos, reviews and decision forums. Listen as much as you broadcast.
5. 5Monitor — revisit the register at each phase gate and after major events. Engagement drifts; new stakeholders appear when the project changes shape.

Analysis model 1: power / interest grid

Analysis model 2: salience (power, legitimacy, urgency)

The salience model asks three questions: does this person have power to influence the project, a legitimate claim on it, and urgency — a time-sensitive need? Stakeholders with all three are 'definitive' and demand immediate attention. Those with power and urgency but no legitimacy are 'dangerous' — for example a senior manager outside your governance trying to redirect scope — and need careful handling through the sponsor.

The engagement assessment matrix

For each key stakeholder, mark where they are today (C) and where you need them to be (D). The gap is your engagement plan.

Building the stakeholder register

• Name, role and organisation — and who they listen to.
• Interest in the project and what success looks like to them.
• Influence: formal authority, informal influence, and control of resources or approvals.
• Current and desired engagement level, with the reason for the gap.
• Key concerns, likely objections and known history with similar projects.
• Engagement owner — the person on the team who holds the relationship.
• Preferred channel and frequency, plus the next planned interaction.

The communication plan

RACI, used sparingly

• Responsible — does the work. Can be several people.
• Accountable — answers for the outcome. Exactly one person, always.
• Consulted — two-way input before the decision.
• Informed — one-way notification after it.

Use RACI for decisions and deliverables that cross team boundaries, not for every task. A RACI with 200 rows is never read; one with the 15 decisions that cause arguments is used every week.

Handling resistance

Worked example: a finance system replacement

Illustrative scenario. A mid-sized company replaces its accounts-payable system. The finance director (high power, initially resistant) fears month-end close will slip during cutover. The AP team (high interest, low power) worry about job changes. IT security must approve the cloud vendor.

1. 1The PM met the finance director one-to-one, listened, and added 'no impact to month-end close' as an explicit success criterion and cutover constraint.
2. 2Two AP clerks joined design workshops and user testing; one became the super user and ran peer training.
3. 3The security review was started in week two, not at go-live, with a named owner and a date on the critical path.
4. 4The communication plan moved from monthly updates to weekly 'what changes for you' notes in the six weeks before cutover.
5. 5Result: the finance director moved from resistant to supportive and chaired the go/no-go meeting; the AP team adopted the new process with no rollback.

Measuring stakeholder engagement

• Movement on the engagement assessment matrix between phase gates.
• Decision turnaround time — days from request to decision by governance.
• Attendance and participation in workshops, demos and reviews.
• Pulse surveys or short sentiment checks with key groups.
• Escalations and complaints raised outside the agreed channels.
• Post-go-live adoption: usage, workarounds and support tickets by group.

Common mistakes

• Identifying stakeholders once at kick-off and never revisiting the list.
• Treating communication as engagement — sending reports is not the same as listening.
• Managing only up: pleasing the steering committee while users disengage.
• Hiding bad news from high-power stakeholders until it is unavoidable.
• Letting the PM own every relationship instead of assigning engagement owners.