Stakeholder Mapping Matrix
A systematic framework for identifying, analysing, and prioritising stakeholders based on their power, interest, and support levels to inform engagement strategy.
Keep in mind Positions are only as good as the evidence you give: check every Champion, Sceptic or Blocker rating against what the person actually said or did, and keep the map internal.
Version 1.1 · Updated 30 October 2026
What you'll get
The opening of a worked example. Anonymised and shortened; yours will follow your inputs.
New appraisal system: stakeholder map (fictional example)
INTERNAL: not for circulation
Context: Larchmoor Housing Association is moving 1,400 staff to a new online appraisal system. It changes how reviews are carried out and recorded.
Priority stakeholders (Manage closely):
| Stakeholder | Position | Interests and concerns | Evidence | Engagement |
|---|---|---|---|---|
| Director of People (sponsor) | Champion | Consistent appraisals across teams | Proposed the change and presented the case to the executive team in May 2026 | Weekly project meeting |
| Head of IT | Sceptic | Integration with the HR system; workload on a small IT team | Raised both points in writing at the June 2026 project board | Fortnightly technical review; early sight of specifications |
| Recognised trade union | [Confirm: evidence of their position] | Not yet known | Not yet consulted | Formal consultation, timing to agree with HR |
Key risk: IT capacity delays integration. Mitigation (proposal): involve the IT team in solution design and agree an independent technical review before go-live.
Next step
The prompt ends with questions for you. Answer them with this, in the same chat.
Here are my answers to your questions: [YOUR ANSWERS] Revise the draft using them. Remove the [Assumed] and [Confirm] marks my answers resolve, keep the rest, and update the questions and checks.
Human review checklist
Before using your stakeholder map, verify:
Go deeper
Variations
Organisational change
Use this when the map is for a restructure or change that affects staff.
This map is for an organisational change affecting [WHICH TEAMS OR GROUPS, AND WHAT CHANGES FOR THEM]. Include affected staff groups, line managers, and any recognised union or staff forum I have named; if I have named none, add [Confirm: recognised unions or staff forums]. Map groups, not individual employees whose roles may be affected, and do not describe anyone's job as safe or at risk. Do not state what consultation is required: flag that HR must confirm it, and who has to be told first.External and public affairs
Use this when the stakeholders are outside the organisation: regulators, politicians, partners, media or community groups.
These are external stakeholders: [WHICH GROUPS, SUCH AS REGULATORS, ELECTED MEMBERS, PARTNERS, MEDIA OR COMMUNITY GROUPS]. In Part 4, add a column Formal process for anyone with a formal role (a consultation, inquiry, licence or legislative stage), using only processes and dates I have given. Describe a politician's or official's view only from what they have said on the record, and say where. Add [Confirm: who signs off contact with regulators and elected members] above the Part 4 table.Full example output
Example output
Anonymised and shortened. Real outputs will vary based on your inputs.
New appraisal system: stakeholder map (fictional example)
INTERNAL: not for circulation
Context: Larchmoor Housing Association is moving 1,400 staff to a new online appraisal system. It changes how reviews are carried out and recorded.
Priority stakeholders (Manage closely):
| Stakeholder | Position | Interests and concerns | Evidence | Engagement |
|---|---|---|---|---|
| Director of People (sponsor) | Champion | Consistent appraisals across teams | Proposed the change and presented the case to the executive team in May 2026 | Weekly project meeting |
| Head of IT | Sceptic | Integration with the HR system; workload on a small IT team | Raised both points in writing at the June 2026 project board | Fortnightly technical review; early sight of specifications |
| Recognised trade union | [Confirm: evidence of their position] | Not yet known | Not yet consulted | Formal consultation, timing to agree with HR |
Key risk: IT capacity delays integration. Mitigation (proposal): involve the IT team in solution design and agree an independent technical review before go-live.
Engagement focus: answer the Head of IT’s two written concerns before the next project board. Open discussions with the union early, once HR has confirmed what consultation is required.
The template
Part 1: Stakeholder Identification
List all individuals and groups who:
- Have decision-making power over this project/initiative
- Will be affected by outcomes (positively or negatively)
- Can influence others’ opinions or decisions
- Have formal roles in approval or implementation
- Control resources you need
- Could create obstacles if opposed
| Stakeholder name/group | Role/position | Why they matter |
|---|---|---|
| [Name/title] | [Their formal role] | [Influence they have or how they’re affected] |
Part 2: Power & Interest Analysis
Power (ability to influence outcomes):
- High: Can approve/block, controls budget, has formal authority
- Medium: Influences decision-makers, controls some resources, has expertise
- Low: Limited formal authority, but may have opinion or be affected
Interest (level of concern about this project):
- High: Directly affected, strong opinions, actively engaged
- Medium: Affected but not critically, some opinions, may engage
- Low: Tangentially affected, indifferent, unlikely to engage
| Stakeholder | Power | Interest | Quadrant |
|---|---|---|---|
| [Name] | High/Med/Low | High/Med/Low | [See grid below] |
Power/Interest Grid:
High Power, │ High Power,
Low Interest │ High Interest
(KEEP SATISFIED) │ (MANAGE CLOSELY)
─────────────────────────┼─────────────────────
Low Power, │ Low Power,
Low Interest │ High Interest
(MONITOR) │ (KEEP INFORMED)
│
Low Interest ────────────► High Interest
Quadrant meanings:
- Manage Closely: Your priority stakeholders: high engagement, regular communication, involve in decisions
- Keep Satisfied: Important to keep positive but don’t need constant updates. Provide summaries, check in at key milestones
- Keep Informed: Care about this work but can’t influence it much. Regular updates, opportunities to provide input
- Monitor: Minimal engagement required. Monitor for shifts in position, but don’t invest heavy resources
Part 3: Support Level Analysis
For your Manage closely and Keep satisfied stakeholders, assess current position. Give a position only where you can point to something they said or did; otherwise mark it as needing evidence:
| Stakeholder | Current position | Their interests/concerns | Evidence |
|---|---|---|---|
| [Name] | Champion / Supporter / Neutral / Sceptic / Blocker | [What do they care about?] | [What tells you this?] |
Position definitions:
- Champion: Actively advocates for your project; uses influence to support
- Supporter: Generally positive; will approve/support when asked
- Neutral: No strong position yet; could move either direction
- Sceptic: Concerns or doubts; needs convincing
- Blocker: Opposed; will use influence to prevent/delay
Part 4: Engagement Strategy
| Stakeholder | Engagement approach | Communication frequency | Key messages/focus | Owner |
|---|---|---|---|---|
| [Name] | [1-1 meetings, working group, etc.] | [Weekly, monthly, at milestones] | [What they need to hear] | [Team member responsible] |
Engagement approaches by quadrant:
Manage Closely (high power, high interest):
- One-to-one meetings at key decision points
- Involvement in planning or advisory groups
- First to hear about developments
- Channels: Direct conversation, dedicated briefings
Keep Satisfied (high power, low interest):
- Summary updates at key milestones
- Opportunity to raise concerns, without detailed involvement
- Channels: Email updates, brief presentations
Keep Informed (low power, high interest):
- Regular progress updates
- Forums or Q&As for input
- Channels: Newsletters, group briefings, intranet
Monitor (low power, low interest):
- Passive information sharing
- Alert system if position changes
- Channels: General comms, public updates
Part 5: Risks & Mitigation
| Risk | Related stakeholder(s) | Impact if occurs | Mitigation strategy |
|---|---|---|---|
| [e.g., Key blocker convinces others to oppose] | [Name] | [e.g., Project delayed 6+ months] | [e.g., Early engagement to understand concerns, find compromise] |
When to use it
What it is
A stakeholder mapping matrix helps you systematically identify who matters to your project or initiative, understand their power and interest levels, and determine how to engage them effectively. It turns a stakeholder list into a set of priorities based on influence, interest, and current position.
It uses a Power/Interest grid, plus support level analysis to show where each stakeholder currently stands.
When to use it
Use stakeholder mapping when:
- Launching projects or initiatives that require buy-in from multiple groups
- Planning change management communications where resistance is likely
- Working through complex organisational politics or decision-making processes
- Developing advocacy or public affairs strategies
- Managing issues where different groups have conflicting interests
- Preparing for major announcements that affect different audiences differently
Don’t use stakeholder mapping for:
- Simple projects with obvious, limited stakeholders (overcomplicated approach)
- Crisis situations requiring immediate action (no time for systematic mapping)
- Situations where stakeholder positions are well-established and unchanging
Inputs needed
Before you start, gather:
- Project/initiative context: What are you mapping stakeholders for? Be specific.
- Organisational knowledge: Who holds formal power? Who has informal influence?
- Stakeholder intelligence: What do you already know about positions, interests, concerns?
- Engagement history: Have you worked with these stakeholders before? What happened?
- Decision-making process: How will decisions actually be made on this project?
Tips for success
Map early, update often:
Don’t wait until you need buy-in to understand who holds power. Map stakeholders at project inception and review monthly.
Distinguish formal and informal power:
The person with the job title isn’t always the person with influence. Map both.
Evidence your position assessments:
Base each one on something the person did or said, such as “They volunteered resources and advocated in the last Exec meeting”, rather than a hunch like “I think they’re supportive”.
Don’t make it public:
Stakeholder maps describe political reality. Describing someone as a “blocker” is useful internally; devastating if they see it. Control distribution carefully.
Plan for position shifts:
Stakeholders aren’t static. A supporter today might be a sceptic tomorrow if circumstances change. Monitor and adapt.
Common pitfalls
Mapping everyone equally:
If you have 50 stakeholders all marked “high priority,” you haven’t prioritised. Keep Manage closely to a group small enough to engage closely.
Confusing interest with importance:
Someone can be very interested but have no power to influence outcomes. Don’t over-invest engagement where there’s no decision-making authority.
Assuming positions based on roles:
“Finance people are always sceptics” is lazy thinking. Assess individuals on their behaviour and stated positions.
Ignoring informal networks:
The person who has coffee with the CEO every morning might have more influence than the director who sees them quarterly. Map the real power structure.
One-and-done mapping:
Stakeholder maps created once and never updated soon go out of date. Positions shift, people move roles, contexts change. Review regularly.
Related templates
Change Communications Plan
Comprehensive framework for planning and executing communications across major organisational change, transformation, or significant initiative rollout.
Campaign Brief
A comprehensive campaign planning document that aligns stakeholders on objectives, strategy, creative direction, and execution before work begins.
Communications Plan One-Pager
A single-page strategic overview that captures your communications objectives, audiences, approach, and measurement.
Message House
Structured narrative framework that builds a foundational house of messages with core positioning at the roof, three pillars of support, and detailed proof points in the foundation.