Planning stakeholder engagement

Analysis tells you who matters and why. Planning decides what you will do about it. A stakeholder engagement plan sets out, for each significant stakeholder or group, where their engagement is now, where it needs to be, and the actions, owners and timing that will close the gap. It also aligns expectations early, before disagreements about scope, success criteria or trade-offs harden into conflict. This lesson covers the stakeholder engagement assessment matrix, writing engagement strategies, aligning expectations at the start of a project, and how planning differs across predictive, agile and hybrid delivery.

Levels of engagement

PMI guidance describes five levels of stakeholder engagement. They form a scale from no awareness to active advocacy, and they are the basis of the engagement assessment matrix.

Notably, the desired level is not always leading. A regulator should be appropriately engaged but independent; asking a safety regulator to champion the project would be inappropriate. Many stakeholders need only to be neutral or supportive. The target for each stakeholder depends on what the project needs from them.

The stakeholder engagement assessment matrix

The engagement assessment matrix lists stakeholders against the five levels and marks each person's current level (C) and desired level (D). The gaps show where effort is needed. A stakeholder whose C and D are in the same column needs maintenance, not intervention. A stakeholder whose C is two or more columns to the left of D needs a specific strategy and probably a named owner.

Writing engagement strategies

For each stakeholder with a significant gap, a good strategy answers five questions. What is their interest and concern? What do we need from them? What will move them from current to desired engagement? Who owns the relationship? When and how will we check whether it is working? Strategies should address the stakeholder's interests, not just the project's needs. A resistant stakeholder rarely becomes supportive because of more information about the project's benefits; they move when their own concerns are addressed or when they gain a real voice in decisions.

The stakeholder engagement plan collects these strategies with other content: the desired and current engagement levels, the scope and impact of change for each stakeholder, interrelationships between stakeholders (for example, unit managers follow the chief nursing officer's lead), information to be distributed and its format, and how the plan will be updated. Some content, such as strategies for resistant stakeholders, is sensitive and should not be shared widely.

Aligning expectations at the start

The exam outline's align stakeholder expectations task is about agreeing, early, what the project will deliver and how success will be judged. Misaligned expectations are one of the most common sources of later conflict. A sponsor who expects a full system replacement and a finance director who expects a minimal upgrade can both sign the same vague charter and discover the disagreement only when the first invoice arrives.

Practical alignment techniques include a kickoff meeting with key stakeholders that confirms objectives, scope boundaries, constraints and success criteria; explicit in-scope and out-of-scope lists; agreed acceptance criteria and a definition of done; a priority order for the constraints (for example, "the date is fixed, scope is flexible, budget has 10 per cent tolerance"); and a shared view of major risks and assumptions. Writing down trade-off priorities is especially valuable, because it gives the project manager a pre-agreed basis for decisions when something has to give.

Planning in agile and hybrid projects

Agile approaches build stakeholder engagement into the delivery rhythm. The product owner represents users and customers, maintains the backlog and makes priority decisions; sprint reviews give stakeholders a regular look at working results and a chance to change direction. Planning is lighter and more frequent: instead of a detailed engagement plan written once, teams review stakeholders at release planning and adjust each iteration. Personas, journey maps and story maps help the team keep real users in mind.

Agile does not remove the need for planning, however. Stakeholders outside the product owner's reach, such as regulators, security, finance and operations, still need deliberate engagement, and their requirements often arrive late if nobody plans for them. Hybrid projects commonly use a lightweight engagement plan for governance and external stakeholders alongside agile ceremonies for users.

When planning involves the public

Projects with public impact often follow a recognized engagement spectrum, such as the one published by the International Association for Public Participation (IAP2). It describes increasing levels of public influence: inform, consult, involve, collaborate and empower. The most important planning decision is to be honest about which level applies. Consulting the public while implying they will decide is a reliable way to destroy trust. Lesson 11 returns to public, Indigenous and international engagement in more depth.

Reviewing and updating the plan

An engagement plan should be reviewed on a rhythm and when triggers occur. A sensible rhythm is monthly on most projects and at each phase gate or release. Triggers include a change of sponsor or key executive, a new regulation, a major change request, a sudden drop in a stakeholder's engagement, a public complaint, and the start of a new phase that brings new groups into play, such as operations staff before go-live. Each review asks the same questions: Are the right stakeholders on the list? Have current levels changed? Are the desired levels still right? Are the strategies working, and do owners still have time to carry them out?

Keep a short change history in the plan, noting what changed and why. That history is useful in lessons learned and helps a new project manager understand why particular stakeholders are handled as they are. It also discourages the common habit of writing a plan at the start and never reading it again.