Why map before you design
Centralization projects move work, authority or data from several places to one. The people who gain from that, and the people who lose something, are rarely the same. A project team that plans only around the sponsor and the technical staff will probably discover the other affected groups late, often when one of them raises an objection that could have been addressed months earlier.
Stakeholder mapping is the practice of listing the people and groups affected by or able to affect the project, then recording what you know about each: how they are affected, how much influence they have, what concerns they are likely to have, and how best to engage them. It is a planning aid, not a science, and its value is mostly in the questions it forces.
Who counts as a stakeholder
The obvious groups are the project sponsor, the team that will run the central function, and the staff whose work is being moved. A wider look usually adds:
- Local managers whose teams, budgets or decision-making authority change.
- Teams who depend on the current local arrangement, such as finance, legal or customer-facing staff.
- Staff who will receive a service from the new central group and whose requests will now flow differently.
- Technical and security teams who support or protect the systems involved.
- External parties, such as suppliers, customers or contractors, where the change touches them.
- Informal influencers, people with no formal authority who are trusted by colleagues and whose opinion shapes the mood.
- Governance bodies, such as a steering committee or an approval board, that decide whether the project proceeds.
An easy way to find missing groups is to trace a typical piece of work from request to completion and note everyone who touches it. Another is to ask several people who they think should be consulted and see whose names recur.
What to record about each group
A useful map holds only a few facts per group, kept short so it is read and updated.
- How they are affected: what changes in their work, authority, workload or status.
- Influence: how much power they have over the project’s success, through budget, formal approval, expertise or social weight.
- Interest or concern: what they care about and what they are likely to worry about.
- Current stance: supportive, neutral, doubtful or opposed, treated as a working guess and not a label.
- What they need: information, involvement, reassurance or a say in specific decisions.
- Who engages them: a named person, so the relationship has an owner.
A simple influence and impact grid
Many teams sort groups on two axes, such as influence over the project and degree of impact from it. The result is four rough zones:
| Lower influence | Higher influence | |
|---|---|---|
| Higher impact | Keep informed and supported; give a channel to be heard | Involve closely; shape decisions with them |
| Lower impact | Monitor; light communication | Keep informed; make sure they do not become opposed through neglect |
The grid is a prompt, not a rule. A group with low formal influence and high impact, such as frontline staff whose daily work is changing, can still make or break adoption through how they actually use the new arrangement. Treating them as merely “to be informed” is a frequent mistake.
An illustrative example
The groups and positions below are invented to show how a map might look; they are not drawn from any real organization.
Suppose a business with four regional offices plans a form of centralized procurement, moving purchasing approval to one central team. A first map might list:
- Regional office managers: lose control of local approvals; influence is high; likely concern is slower turnaround and loss of authority. Engagement: involve in designing service targets and exceptions.
- Regional administrative staff: their tasks change from approving to submitting; influence is lower in formal terms but impact is high. Engagement: early demonstrations, training and a named contact.
- Finance team: gains better visibility and consistent data; influence is high; concern is that the central team is adequately resourced. Engagement: regular working sessions.
- Central purchasing team: gains new work; influence is moderate; concern is capacity. Engagement: involve in planning workload.
- Suppliers: may see changed contacts and payment timing; influence is low to moderate. Engagement: advance notice from the purchasing lead.
Even this short list raises useful questions. Does the central team have enough people? What happens to urgent local purchases? How will exceptions be handled? Questions like these are better asked while the design can still change.
Gathering the information
A map built only from the project team’s assumptions will reflect their blind spots. Better sources include:
- short conversations with representatives of each group;
- input from line managers and change champions who know the teams;
- looking at how work is really done, not just how procedures describe it;
- reviewing past changes, to see who objected then and why.
Take care with the sensitive parts of the map, such as notes about individuals’ attitudes. Keep them factual and professional, share them only with those who need them, and assume they could be read by the people described. Describing a group’s concerns in respectful terms is both fairer and more useful than labelling people as obstacles.
Turning the map into an engagement plan
The map becomes useful when each group has a plan.
- For groups who gain, check that the benefits are real and not assumed, and avoid overselling them.
- For groups who lose something, acknowledge it. Where possible, look for ways to reduce the loss, such as clear service targets, a route for exceptions or a role in governance.
- For groups with a high influence and doubts, spend time understanding the reasoning. Their objections may expose real design weaknesses, and some may point towards one of the hybrid operating models in which certain decisions stay local.
- For groups whose concerns are mainly practical, make sure the details are communicated and that training is planned.
Engagement can range from a short note to a seat on a working group. Choose a level that matches the group’s influence and impact, and be honest about how much say they actually have. Offering consultation on a decision that has already been made tends to backfire.
Keeping the map alive
Stakeholder positions shift as details emerge. A group that seemed neutral may become concerned when the timetable is announced. Review the map at regular points: before major announcements, at design decisions and after go-live. Update it when someone moves role, when new groups appear, and when a concern turns out to be more or less serious than expected.
A map has limits. It simplifies people, relies on judgement, and can give a false sense of control if treated as certain. Used as a prompt for conversations with the people on it, it helps a project start from a more complete picture of the organization it is about to change.