Business
Stakeholder mapping: how to build a map you can act on

Stefan Weiss
Stakeholder mapping means identifying the people and groups involved in or affected by a project, understanding their relationship to the work, and deciding how to engage them. Start with the project decision, build an evidence-backed stakeholder list, choose a useful way to assess it, then give each important engagement action an owner.
The finished map should help you answer a practical question: who do we need to involve next, about what, and why? A polished diagram without that answer is unfinished work.
This guide takes you from the first list to a reviewable engagement plan. The examples are fictional, so you can adapt the reasoning without treating the positions as universal scores.
What a stakeholder map adds to a contact list
A contact list tells you who exists and how to reach them. Stakeholder analysis examines their needs, influence, concerns and connection to the project. A stakeholder map makes selected relationships or assessments visible so a team can use them in a discussion.
The engagement plan is the next decision: what you will do with that understanding. The UK Government Analysis Function’s guidance explicitly connects mapping with planning suitable contact and reviewing those choices over time.
Keep these outputs connected, but give each a clear purpose:
Output | Main question |
|---|---|
Stakeholder list or register | Who is involved or affected, and what do we know about them? |
Stakeholder analysis | What matters to them, and how can they affect or experience the work? |
Stakeholder map | Which relationships or differences need our attention? |
Engagement plan | What happens next, who owns it and when will we check the result? |
A map also differs from an organisation chart. Formal reporting lines can matter, but they do not show every dependency, concern or source of practical knowledge.
Before you start: define the project and decision
Write a short statement of the work you are mapping. Include the intended change, the decision in view and the people likely to experience its effects.
For example:
We are replacing the client onboarding process. Before choosing the pilot approach, we need to understand who can approve it, who will operate it, who depends on its outputs and which clients may struggle with the change.
That boundary is more useful than “map everyone connected with the company”. It gives you a reason to include a person and a way to recognise an unrelated contact.
Gather the material you already have: project notes, a proposed scope, existing responsibilities, earlier feedback and appropriately retained conversations. You also need someone who can maintain the record after the workshop. Otherwise the map quickly becomes a snapshot nobody owns.
1. Build the list before deciding who is important
Start with several ways someone could be connected to the work:
They experience the change or depend on the current service.
They carry out the work, support it or deal with exceptions.
They can approve, fund, delay or stop a decision.
They hold specialist knowledge or a necessary dependency.
They represent people who may otherwise be difficult to hear.
Ask colleagues who is missing, including people outside the usual meeting group. Do not use attendance in existing recordings as your definition of the stakeholder population. Someone absent from every planning call may still carry the largest operational consequence.
For a broad project, begin with groups and then identify the individuals needed for particular decisions. Keep the distinction visible. An interview with one support adviser does not establish the view of every adviser.
The University of Birmingham’s mapping guide similarly starts with identifying relevant people and organisations, then distinguishes mapping from tracking the ongoing relationship.
2. Separate what you know from what you assume
For each entry, record the connection to the project, the current concern and the evidence behind your assessment. A short source note is often enough to make the next discussion more useful.
Compare these entries:
Weak entry | More useful entry |
|---|---|
Finance: powerful, not interested | Finance approves the pilot spending. The controller asked for an estimate before the next review; ongoing operational involvement is unconfirmed. |
Support: resistant | Two support advisers described a concern about handling incomplete client records. Ask the wider team how frequently this occurs. |
Clients: keep informed | The new intake form changes what clients must provide. We have not yet checked accessibility or language needs with representative clients. |
The second version avoids turning an interpretation into a personality label. It also shows where another conversation is needed.
If several people disagree about an assessment, retain the disagreement long enough to investigate it. Averaging opinions can produce a tidy position while concealing different evidence or different definitions of influence.
Using previous conversations carefully
If relevant discussions are saved in Weeve, Chat with recordings can help you return to that material and follow answers to their sources. Choose the recordings relevant to this project before asking about concerns, dependencies or unresolved questions.
Use the result as a starting point for review. Check who actually said something, the date and the surrounding context. An AI answer cannot establish the views of people who were never asked, and a speaker label does not establish someone's decision-making authority.
Keep the working assessment in your chosen project document or mapping tool. This is a source-review workflow, not a claim that Weeve automatically generates or validates a stakeholder map.

Genuine Weeve interface with synthetic demonstration content. The selector illustrates choosing the material to review, not a completed stakeholder map.
3. Choose a mapping method that answers your question
A power–interest grid is a useful starting point when you need to discuss influence and engagement. It places stakeholders according to their ability to affect the work and their level of involvement or concern.
Define both dimensions before placing people. For this project, does influence mean approval authority, control of a dependency, practical expertise, or several of those things? Does interest mean active attention, personal consequences, or an expressed wish to participate? An assessment is difficult to defend when the team uses different meanings.
You do not need a grid for every situation:
Method | Useful when | Watch for |
|---|---|---|
Power–interest grid | You need a first discussion of influence and suitable contact | Treating a position as a permanent fact |
Relationship map | Dependencies and connections matter more than individual scores | Drawing so many links that no decision remains clear |
Impact or affectedness assessment | You need to understand who experiences the change | Assuming formal influence reflects the size of the consequence |
Simple stakeholder table | The project is small and a diagram would add little | Leaving the engagement decision implicit |
Use more than one view if the decision requires it. You can keep a power–interest view for coordination and a separate affectedness check for inclusion. Do not squeeze every important question onto the same two axes.
4. Review low influence and high consequence separately
A person with little formal power may have a strong reason to shape the project. They might use the service every day, face an access barrier or deal with the exceptions the project team rarely sees.
Before deciding that someone needs only occasional updates, ask:
What changes for them if this project succeeds or fails?
Have we heard from them directly or only through a manager?
Can they participate in the way we currently collect input?
Which decision needs their experience before it is made?
This is a check on your process, not a new universal scoring formula. Keep the reason for involving someone visible even when their position on a power-based view looks low.
Avoid labels that imply a stakeholder is a problem to be controlled. Describe the concern or dependency you need to understand. A useful map helps a team work with people; it should not become a permanent judgement about them.
5. Turn the assessment into specific engagement actions
For each priority relationship, choose the next useful action. “Manage closely” or “keep informed” can orient a discussion, but those phrases do not tell a colleague what to do tomorrow.
Translate them into an action with an owner, purpose and review point. Examples include asking for approval criteria, testing a proposed process with the people who will operate it, or checking a dependency before setting a date.
Keep the request proportionate. A stakeholder does not need to attend every weekly meeting simply because they can approve a major decision. Equally, a broadcast email is not a substitute for input that could still change the design.

A worked example: changing a client onboarding process
Consider the fictional onboarding project introduced earlier. The team has four initial entries:
Stakeholder | Evidence or gap | Next action | Owner and review point |
|---|---|---|---|
Operations lead | Owns the current process and must confirm the pilot can be staffed | Review the pilot workload and exception route | Project lead, before agreeing a launch window |
Support advisers | Two interviews identified incomplete records as a recurring difficulty; the wider picture is unconfirmed | Review a few recent cases and test the proposed handover | Operations analyst, before finalising the process |
Finance controller | Approves the spend but has not reviewed the revised estimate | Confirm the information needed for the funding decision | Project lead, before the approval meeting |
Clients using assisted onboarding | The new form may change their experience; no direct evidence yet | Arrange suitable research before selecting the final form | Research lead, before the design decision |
The map may show the controller as influential and the clients as having less formal authority. The action table still gives the client research a clear place before a consequential decision.
After those conversations, update the assessment. You may discover that a supposedly minor dependency controls the pilot date, or that a concern disappears once the proposed exception route is explained. The point is to change the plan when the evidence changes.
6. Keep the map current and handle it with care
Agree what should trigger another review: a change of scope, a new decision-maker, a missed dependency, fresh research or movement into another project stage. Record the date of the assessment and who will maintain it.
The Birmingham guide emphasises that stakeholder relationships and circumstances change. Treat the map as a working account rather than a one-time workshop deliverable.
Be deliberate about access. A map can contain sensitive interpretations of relationships or concerns. Include only the detail needed for the project and avoid speculative personal commentary. Consider which version is suitable for a wider project group and which source material needs more restricted handling.
Before relying on the map, check that each important engagement action has an owner, missing perspectives are explicit and the next decision has the input it needs. That gives the document a practical test: it changes who you speak to, what you ask and what you do next.


