Stakeholder Mapping

Make engagement choices from evidence about influence, impact, legitimacy and current attitude—not from a static list of job titles.

In one minute

Stakeholder Mapping identifies people, groups and institutions that can affect a decision or will experience its consequences. A useful map separates:

• stake: what the actor can gain, lose, enable or constrain;
• power or influence: formal authority, resources, expertise, access or network position;
• interest: how closely the actor attends to the issue;
• impact: how strongly the change may affect the actor, including low-power groups;
• attitude: current support, neutrality, concern or opposition;
• engagement need: what must be learned, communicated, co-designed, negotiated or governed;
• evidence and review: why the assessment is credible and when it may change.

A power-interest grid is one view, not the method’s final answer. High power does not equal high legitimacy, and low formal power does not justify ignoring people who bear material risk.

Best for: programmes, policy choices, operating-model changes and cross-functional decisions whose success depends on several actors.
Avoid when: the purpose is covert manipulation, the team cannot protect sensitive observations, or a role-and-task assignment such as RACI is the actual need.

The problem it addresses

Change plans often communicate broadly but engage selectively by intuition. Formal sponsors receive attention while frontline experts, affected customers, worker representatives, regulators or partner teams appear late. The result is rework, resistance, missed constraints and weak legitimacy.

Stakeholder Mapping makes those assumptions visible. It supports a proportionate engagement plan while preserving the distinction between influence over the decision and exposure to its consequences.

When to use it

Use Stakeholder Mapping when:

• a programme crosses organisational or jurisdictional boundaries;
• adoption depends on people who do not report to the programme;
• different groups experience different benefits, burdens or risks;
• formal authority and informal influence do not align;
• the team needs an engagement strategy before a major decision;
• support, evidence or relationships are likely to change;
• representation and consultation duties must be visible.

When not to use it

Do not use it:

• as a secret score of whether named individuals are “difficult”;
• to prioritise powerful actors while excluding materially affected groups;
• as a substitute for legal consultation, consent or representation requirements;
• to publish personal attitudes or inferred traits without authority;
• when the real gap is unclear task ownership—use RACI Matrix;
• as a one-time workshop artefact that no one owns or revisits.

Use PESTLE Analysis for macro-environmental forces and Customer Journey Mapping for the customer’s end-to-end experience.

Inputs required

Prepare:

• the decision, change or programme boundary;
• expected outcomes, material risks and affected populations;
• organisational, process, customer and ecosystem evidence;
• known formal decision rights and obligations;
• interviews or observations about informal influence and attitude;
• a rule for handling sensitive or personal information;
• an engagement owner and review date.

Step-by-step process

1. Define the focal change

Write the decision, geography, time horizon and what is outside scope. A map for “digital transformation” is too vague; a map for “introduce one regional CRM workflow before Q2 renewal season” can guide action.

2. Identify actors broadly

List people, roles, groups and institutions that decide, deliver, advise, regulate, represent, depend on or are affected by the change. Use process, customer, governance and external-system views to reduce blind spots.

3. Record each stake

State what each actor needs, contributes, risks or may experience. Do not infer a motive where evidence only shows a position.

4. Assess power and influence

Separate formal authority from resource control, expertise, credibility, network access and the ability to delay or accelerate work. Record the evidence and confidence behind the assessment.

5. Assess interest and impact

Interest is attention; impact is consequence. A low-interest group can still face high impact, and an initially disengaged group may become active once consequences are understood.

6. Add legitimacy, urgency and attitude where useful

For high-consequence work, ask whether the claim is legitimate, time-sensitive and represented. Describe current attitude toward the proposal, not a permanent personality label.

7. Choose an engagement response

Decide what the programme needs from the relationship: listen, inform, consult, co-design, negotiate, assure or involve in governance. Match frequency, channel, owner and feedback loop to that purpose.

8. Test the map with representatives

Validate material assumptions with people who know the system and, where appropriate, with the stakeholders themselves. Surface missing groups and disputed assessments.

9. Protect sensitive information

Store only decision-relevant observations, distinguish facts from interpretation and limit access. Do not distribute a personalised “resistance map.”

10. Review on triggers

Update after a decision gate, incident, leadership change, regulatory signal, pilot result or material shift in support. Archive the old view so changes remain explainable.

AI automation lens

AI can extract candidate organisations and roles from approved documents, cluster interview themes, identify inconsistent names and prompt the team to consider overlooked actor types. It can maintain traceable reminders for review.

It must not:

• infer political views, vulnerability or personal attitude from unrelated data;
• rank people by “resistance” without evidence and authority;
• scrape private profiles or communications;
• decide whose rights or impacts matter;
• send engagement messages without an accountable human;
• turn a probabilistic suggestion into a fact.

Keep source, confidence and human validation beside every generated suggestion.

Visual model

Text alternative: define the focal change, identify actors and record each stake with evidence. Assess power or influence separately from interest and impact. Those views shape an owned engagement approach whose feedback updates the map.

Interactive example

Scenario

A services company will introduce a shared CRM workflow in three regions. The executive sponsor wants one launch date. Country sales leaders control local adoption; service agents will absorb additional data entry; works councils may require consultation; key customers depend on uninterrupted case handling; information security can stop the rollout. The project team has spoken only with sales leaders.

Your move

Identify a missing high-impact stakeholder, distinguish its power from impact, and propose one engagement action with evidence and a review trigger.

Worked answer

Service agents have limited formal decision authority but high operational impact and strong process knowledge. Their stake is workload, service continuity and usable case data. The programme should run representative workflow tests and publish which findings changed the design. The engagement owner is the regional process lead; evidence includes task time, error rates and agent feedback. Review the map after each regional pilot because adoption evidence may change both attitude and influence.

Works councils and security require separate treatment: their authority and obligations cannot be reduced to an interest score.

Facilitation notes

• Start with the change and consequences, not a list of senior names.
• Use role or group labels unless an individual name is necessary.
• Ask who experiences the burden but lacks the room or authority to speak.
• Separate observed evidence, team interpretation and confidence.
• Let participants challenge both missing actors and flattering assessments.
• End with an engagement owner, purpose, channel and review trigger.

Expected output

• a bounded stakeholder register;
• explicit stakes and affected outcomes;
• evidence-based views of power, influence, interest and impact;
• optional legitimacy, urgency and attitude notes;
• engagement purpose, owner, channel and cadence;
• information-handling rules;
• review dates and triggers.

Common mistakes

1. Power-interest grid as truth. It is a provisional view, not an objective measurement.
2. Power equals importance. Low-power groups may carry the greatest impact or strongest legitimate claim.
3. Job title equals influence. Expertise and networks can matter more than hierarchy.
4. Attitude as personality. Support can change with evidence, design and trust.
5. Engagement as broadcasting. Communication without listening or response does not resolve uncertainty.
6. No review. Stakeholder relationships change throughout the programme.

Quality checklist

• The focal change and boundary are explicit.
• Identification includes decision-makers, deliverers and affected groups.
• Power, interest and impact are assessed separately.
• Material claims have evidence and confidence.
• Low-power, high-impact stakeholders remain visible.
• Engagement has a purpose, owner, channel and feedback loop.
• Sensitive information is proportionate and protected.
• The map has a review date or event trigger.

Template

Use the structured Stakeholder Mapping workspace template to keep the register and engagement plan connected.

Knowledge check

Question: A customer group has little influence over a programme but will experience a high-impact service interruption if the design fails. What is the strongest response?

A. Exclude it because power is low.
B. Keep impact separate from power and design meaningful representation and feedback.
C. Mark the group as resistant.
D. Send one launch email.

Answer: B. Influence over the decision and exposure to consequences are different dimensions; both must shape engagement.

Related tools

• RACI Matrix assigns participation in defined work after the stakeholder landscape is understood.
• Vroom-Yetton-Jago Decision Model selects an appropriate level of decision participation.
• Customer Journey Mapping supplies evidence about affected customer groups.
• PESTLE Analysis reveals external institutions and pressures.
• Scenario Planning tests how stakeholder positions may change across futures.

References

1. UK Government Analysis Function. “Stakeholder mapping.” Policy-store guidance (opens in a new tab). Accessed 1 September 2026.
2. Association for Project Management. “Stakeholder engagement.” Body of knowledge resource (opens in a new tab). Accessed 1 September 2026.
3. Mitchell, R. K., Agle, B. R., & Wood, D. J. “Toward a Theory of Stakeholder Identification and Salience.” Academy of Management Review, 22(4), 1997. DOI (opens in a new tab). Foundational salience model; categories remain context-dependent managerial assessments.
4. Bryson, J. M. “What to do when Stakeholders matter.” Public Management Review, 6(1), 2004. DOI (opens in a new tab). Independent public-management treatment of stakeholder analysis techniques.