5.4 Communication, Stakeholder Engagement & Change Management
Key Takeaways
- Communication is deliberate: what people HEAR matters more than what leadership SAYS, and the Project Manager should engage key influencers to learn the real message received.
- Engaging the vital few key influencers and building relationships including social aspects — even virtually — is how a Project Manager discovers what people actually hear.
- Stakeholder engagement follows five activities: identify, analyse (power/interest), plan engagement, manage and monitor.
- Change management in PRINCE2 7 is explicit and lives in the PID from initiation, planning how affected business-as-usual routines and people are led through change — not bolted on at closure.
- Project change control (Issues practice, baseline changes) is distinct from organisational change management (people adoption of new ways of working).
Communication: what is heard beats what is said
PRINCE2 7 makes a pointed claim about communication: what people HEAR matters more than what leadership SAYS. A Project Manager can issue a perfectly worded update and still have the team hear "the project is in trouble" or "my input isn't wanted." The method therefore treats communication as a deliberate activity — designed, checked and adjusted — rather than a by-product of good intentions.
Three practices make communication deliberate:
- Engage the vital 3% of key influencers. In any population affected by a project, a small number of people shape how the rest interpret messages. PRINCE2 7 calls these the vital 3% of key influencers. The Project Manager identifies them and checks what they are actually hearing — because what they hear is what the wider group will soon believe.
- Build relationships, including social aspects. Trust is built in unstructured time — lunch, corridor conversations, the five minutes before a call starts. The method explicitly names these social aspects and says they matter even when the team is virtual. A Project Manager who only ever communicates through formal agendas will never learn what people really hear.
- Check and adjust. Communication is not "send and done." The Project Manager closes the loop by observing behaviour and asking what landed.
Exam angle: A scenario where a Project Manager issues a clear update but team behaviour shows they have misunderstood the message is testing the hear-versus-say distinction. The correct response is to engage key influencers and rebuild the message, not to repeat the same update louder.
Stakeholder engagement: five activities
Stakeholder engagement in PRINCE2 7 is structured as five activities. You should be able to place a scenario action into the correct activity.
| Activity | What it involves |
|---|---|
| Identify | Who is affected by or can influence the project |
| Analyse | Map stakeholders using power/interest (or influence/interest) to prioritise attention |
| Plan engagement | Decide how, how often and by whom each stakeholder is engaged |
| Manage | Execute the engagement plan and build the relationships |
| Monitor | Check whether engagement is working and adjust |
Power/interest mapping
The power/interest grid is the standard analysis tool and you may need to read it in a scenario.
| Low interest | High interest | |
|---|---|---|
| High power | Keep satisfied | Manage closely — key players |
| Low power | Monitor — minimal effort | Keep informed — often the users |
A high-power, high-interest stakeholder (top-right) is a key player the Project Manager engages closely and frequently. A low-power, high-interest stakeholder (bottom-right) — often the end user — is kept informed because their adoption determines value even though they cannot direct the project.
Change management: explicit in v7
A significant addition in PRINCE2 7 is the explicit integration of change management. Previously, the method focused on project change control — controlling changes to baselines — and left the human side of adoption largely implicit. v7 brings organisational change management inside the method.
An explicit change management approach is now part of the PID from initiation. It is not a closure activity or a post-project handover. At initiation the project plans:
- Which business-as-usual routines are affected by the project's outputs.
- Who is involved in those routines and how their work will change.
- What the impact on people is — skills, behaviours, relationships, incentives.
- How those people will be led through the change — communication, training, support, reinforcement.
Planning this at initiation means the project is designed to produce adopted outcomes, not just delivered outputs.
Change control versus change management
The exam will test whether you can distinguish two things that share the word "change."
| Project change control | Organisational change management | |
|---|---|---|
| Practice | Issues practice | People element / change management approach |
| Object | The project baseline — scope, schedule, products | People and business-as-usual routines |
| Question it answers | "Should we change what we agreed to build?" | "How do we lead people to adopt the new way of working?" |
| When | Throughout delivery, via change requests | Planned at initiation, executed through and beyond the project |
A scenario that describes a Project Manager assessing a request to add a reporting field to the product is illustrating change control (Issues practice). A scenario that describes planning how finance staff will move from spreadsheets to a new system is illustrating change management (People element). Confusing the two is a common exam trap.
Why change management belongs at initiation
The decision to put change management in the PID from initiation is not cosmetic. It reflects a hard lesson from projects that treated adoption as a closure handover: by the time the project is ready to hand over, the receiving teams have already formed their own narrative about the change, usually a sceptical one. Planning change management at initiation means the project can:
- Involve affected people early — so the design reflects operational reality rather than surprising it.
- Sequence communication and training alongside product delivery — so people are ready when the product lands, not after.
- Identify resistance early — so it can be worked with as a leadership problem rather than fought at closure.
- Link benefits to adoption — so the Business Case recognises that a delivered output that nobody uses delivers no benefit.
This last point connects back to the performance element: PRINCE2 7 measures projects on benefits realised, not products delivered. A product that is delivered but not adopted has failed the benefits test, and change management is the practice that closes that gap.
Communication and change management working together
Communication and change management are related but not identical. Communication is the ongoing activity of making sure people hear what is happening and what it means for them. Change management is the structured plan for leading people from the current way of working to the new one. Good communication enables change management, but a project can communicate well and still fail adoption if there is no change plan — and a project can have a change plan and still fail if nobody hears the message. The Practitioner exam will sometimes present a scenario where one is strong and the other weak, and the correct answer is to strengthen the missing one rather than over-invest in the one that already works.
A Project Manager issues a clearly written status update, but over the next week the team starts acting as if the project is being cancelled. The update said nothing about cancellation. What is the best response, and why?
During initiation, the Project Manager documents which operational routines the new system will affect, which staff are involved, how their work will change, and how they will be supported through the transition. What is this, and where does it belong?
A team member submits a request to add a new field to the product's reporting screen. The Project Manager assesses the impact on scope and schedule and takes the request to the Project Board for a decision. Which practice and which type of change does this illustrate?