A change project can have a sensible plan and a clear sponsor, yet still run into avoidable difficulty because the people affected were only considered as an audience for announcements.
A stakeholder map is a practical way to avoid that. It helps you see who will experience the change, who has knowledge you need, who can influence progress and where a conversation matters more than another presentation.
The point is not to create a complicated matrix for its own sake. It is to give the project team a more accurate view of the human system around the work. That matters particularly when a new process, technology or AI-enabled tool changes everyday roles as well as project milestones.
Begin with the work that will change
Start by describing the work that will be different. Who performs it today? Who receives it, checks it, manages it or depends on its output? Who supplies information to the process? Asking these questions produces a better first list than starting with the names of senior people already on the project board.
For example, a new AI-assisted case-summary process may affect service colleagues preparing cases, managers reviewing quality, subject experts answering queries, data and information-governance teams, and customers who experience a different response time. Each group sees a different part of the change. That is useful knowledge, not an administrative exercise.
Look at impact and influence separately
Two simple lenses are usually enough to begin. First, how much will the change affect this group’s day-to-day work? Second, how much influence do they have over adoption, decisions, resources or the story others hear about the change?
High impact does not automatically mean high formal influence. A busy frontline team may have little place in governance meetings but know immediately whether a process works. Conversely, a senior leader may be lightly affected by the new process but have a decisive role in releasing time, resolving a policy question or modelling the behaviour expected from managers.
Mapping both dimensions helps you avoid a common mistake: communicating most with the people who are easiest to reach rather than the people whose involvement will make the greatest difference.
Identify what each group needs from the project
The next question is more useful than simply asking whether a stakeholder is “supportive” or “resistant”. What do they need to understand, decide, do or provide? A manager may need a clear guide for answering team questions. A subject expert may need time protected for design input. A frontline colleague may need a chance to test a draft process before it is finalised.
Be specific about the practical impact too. If training, testing or a pilot will draw people away from normal work, record that early. It gives the project manager and sponsor a chance to plan capacity, sequence activity and make an honest decision about priorities.
Make the map a working document
Stakeholder mapping is not something to complete at the start and file away. Groups can move as the project develops. Someone who was only being kept informed may become a key champion during a pilot. A team that appeared unaffected may be drawn in by a change to a hand-off or a control.
Build short review points into the plan. At a stage boundary, before a pilot and before go-live, ask whether the map still reflects reality. Have new concerns emerged? Has anyone been missed? Are the same managers being asked to carry too many messages or activities at once?
Turn insight into a conversation plan
A map only helps if it changes what the project does. For priority groups, record the owner of the relationship, the next conversation, the decision or information needed, and the likely timing. Keep it light. A simple list of purposeful conversations is often more valuable than a large communications calendar full of generic updates.
This is where project management and change management meet. Project management gives the work ownership, milestones, risks and decisions. Change management helps the team understand impact, readiness and the quality of involvement. Together, they make communications part of delivery rather than an activity that begins once decisions have already been made.
Use the map within PRINCE2 controls
In a PRINCE2 project, stakeholder insight should inform more than a communications plan. It can shape the business case by testing whether expected benefits are realistic for the people affected. It can improve the quality of the project plan by identifying who is needed for design, testing, training or assurance. It can also give the project board clearer visibility of risks, issues and dependencies that need a decision or escalation.
The map should have an owner and be reviewed alongside the relevant management stage. When impact changes, record it, decide what action is needed and update the appropriate plan or risk record. This is a proportionate way to apply the PRINCE2 principles of continued business justification, defined roles and responsibilities, management by stages and manage by exception. It keeps engagement connected to governance rather than treating it as a separate stream of activity.
Listen for useful disagreement
Stakeholder conversations should not be designed to obtain instant agreement. People close to the work may identify an exception, workload issue or dependency that a project plan has missed. That can feel inconvenient, but it is often exactly the information a sponsor needs before committing further time or money.
Ask open questions: What will be harder on a busy day? What needs to be true for this to work? What would make the first week more manageable? Then show what happens with the answers. Trust is stronger when people can see that the project has listened, even where every request cannot be accepted.
A sensible first step
Take one planned change and list the groups whose work, decisions or service will be affected. Give each a short assessment of impact and influence. Then identify the three conversations the project needs to have before it moves into its next phase. That is enough to turn a vague commitment to engagement into a useful delivery action.
If you are planning a change and would value practical support with stakeholder mapping, communications and project governance, I would be happy to discuss an approach that fits the scale of the work.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
