Stakeholder mapping is one of the most familiar exercises in community engagement.
We identify the groups connected to a decision, consider how they may be affected and assess their ability to influence the outcome. We place them on a matrix and use that analysis to shape the engagement approach.
The problem is not the matrix. It is what can happen after we create it.
A group’s position on the map can quietly become part of its identity.
The residents’ association is high impact, low influence.
The regulator is low impact, high influence.
The local business group is medium impact, medium influence.
Those classifications are copied into an engagement plan or stakeholder register and carried through the project, sometimes long after the circumstances that informed them have changed.
But impact and influence are not permanent characteristics of a stakeholder group.
They describe the group’s relationship with this decision, in this context, based on what we currently understand.
That relationship can change quickly.
Consider a residents’ association
Imagine a council is planning changes to a neighbourhood park.
Early in the project, the local residents’ association is likely to be significantly affected but has relatively little ability to influence the decision.
The project team might reasonably assess the group as:
High impact. Low influence.
Then a revised design proposes removing mature trees.
The association organises a public meeting. Hundreds of people sign a petition. A journalist picks up the story. The issue spreads through local networks. Councillors begin receiving emails, and an election is six months away.
The stakeholder group is the same. Its relationship with the project is not.
It may now be:
High impact. High influence.
A map created three months earlier can still look complete while describing a stakeholder landscape that no longer exists.
A stakeholder map records judgement, not fact
When we place a group on a matrix, we are making a professional assessment:
Based on what we currently know, how significantly could this decision affect the group, and how much could the group influence the decision or its implementation?
The words currently know matter.
Impact may be underestimated because the project team has not yet understood the group’s experience. Influence may change as people organise, form alliances, attract attention or gain access to decision-makers.
Different kinds of influence can also matter at different stages. A regulator may have statutory authority. A councillor may have political influence. A community organisation may have strong relationships and public credibility. A group with little formal authority may still be able to mobilise opposition or affect implementation.
A low, medium or high rating cannot capture all of that. The reasoning behind the rating is often more valuable than the rating itself.
This is also why impact should not be confused with interest.
A group may show little interest because its members do not know about the proposal, do not trust the process or face barriers to participating. That does not mean they will experience little impact.
Interest tells us how much attention a group appears to be giving the issue. Sentiment tells us how it currently feels. Neither tells us how significantly the decision may affect it.
Engagement should test the map
Stakeholder analysis is often treated as work that happens before engagement begins. In practice, engagement is one of the main ways we test whether the original analysis was right.
It may reveal an impact the project team had not considered. It may show that a broad category such as “local residents” contains groups with very different experiences. It may identify people who were absent from the original map or show that a planned method will not reach those most affected.
Stakeholders should also be able to challenge the project team’s assumptions. Wherever possible, significant assessments should be tested with the people concerned rather than remaining an internal judgement about them.
Engagement can change the landscape too.
A group may become more influential after connecting with others. A community may organise once the implications of a proposal become clearer. A stakeholder that feels repeatedly unheard may move from passive concern to active opposition.
Stakeholder analysis is therefore not simply an input to engagement. Engagement produces evidence that should change the analysis.
Map position is not an engagement strategy
A matrix helps a team make sense of complexity, but it cannot determine the engagement response on its own.
Influence, in particular, should not become a proxy for importance. If engagement effort follows whoever has the greatest ability to affect a decision, it can reinforce existing inequalities. The loudest and best-connected groups receive more attention while people facing substantial impacts remain unheard.
A group with low influence may be highly affected, poorly represented and unlikely to participate through standard methods. It may require deliberate outreach through a trusted intermediary, translated information, accessible formats, conversations in an existing community setting or engagement at a different time or location.
That need should be considered separately from the group’s position on the matrix.
A stakeholder map can help us understand the environment. It does not tell us, by itself, who needs the most effort or what credible participation will require.
Start broadly before categorising
Mapping can become a gatekeeping exercise when teams begin classifying too early.
A better starting point is to identify broadly, then make each group specific enough to guide engagement.
“Residents” is rarely a useful stakeholder group. People living beside a proposed development may experience different impacts from renters, parents using a nearby facility, young people, people with disability or residents who rely on public transport.
A group does not need to be reduced to individual contacts. It does need to be specific enough that the team can understand why it matters, how the decision may affect it and how it might credibly be reached.
Only then does placing it on a matrix become useful.
Ask what changed
When teams revisit a stakeholder register, the discussion often begins with:
Is this group still high, medium or low?
A better question is:
What has changed since our last assessment?
Has the proposal changed? Have we learned something new about its likely impact? Has a group organised, built alliances or gained access to decision-makers? Have participation patterns or sentiment shifted? Has a previously overlooked group emerged? Are our methods reaching the people we expected?
A reassessment may be needed when:
the project scope or proposed decision changes;
an option is shortlisted or announced;
engagement reveals an unexpected impact;
participation differs from what the team anticipated;
a stakeholder begins organising or attracting attention;
political or media conditions shift;
the project moves into a new decision phase.
The trigger is not simply that another month has passed. It is that the decision, the evidence or the stakeholder environment has materially changed.
Don’t overwrite the history
If a group moves from low influence to high influence, the usual response is to update its record:
Influence: High.
That keeps the current map accurate, but it removes part of the project’s history.
A more useful record might show:
March — High impact / Low influence
The proposal is at an early stage and the association has not organised around it.
June — High impact / Medium influence
The association is coordinating residents and attending council meetings.
August — High impact / High influence
The group has organised a petition, attracted media attention and established direct contact with elected representatives.
The earlier assessments were not necessarily wrong. They reflected different conditions and the evidence available at the time.
Together, they show how the stakeholder environment developed and whether the project adapted.
The stakeholder and the assessment are different things
There is the stakeholder group: who they are, why they are connected to the project and how they might be reached.
Then there is the assessment: how the decision may affect them, how they may influence it, what barriers they face and what engagement response is appropriate.
The first may remain relatively stable. The second is contextual and should be open to revision.
Separating them changes stakeholder management from maintaining a list into maintaining an evolving understanding of the project environment.
A practical way to review the map
A stakeholder review does not need to become a major workshop. At meaningful points in the project, record five things:
Change: What has changed?
Evidence: What have we seen or learned?
Assessment: Does our understanding of impact, influence, underrepresentation or barriers need to change?
Response: What will we change in the engagement approach, project governance, timing or decision process?
Review: What event or condition should prompt us to look again?
The response is the important part. Updating a dot on a matrix achieves little if the project continues exactly as before.
None of this means stakeholder matrices should be abandoned. They remain useful because they simplify a complicated environment enough for a team to discuss it.
But simplification becomes dangerous when we forget that we have simplified.
A stakeholder map should be treated as a baseline, not a finished artefact. Return to it when the project changes, when engagement produces new evidence or when the surrounding environment shifts.
And do not just move the dots. Record why they moved and what the project will do differently.
Your stakeholder map is not the stakeholder landscape. It is a snapshot of what your team understood about that landscape at a particular moment.
The practice is noticing when that picture has changed—and responding.