Who Holds the Project: A Plain Guide to Stakeholder Mapping
Most projects do not fail on the work itself. They fail on the people around the work — the manager who was never consulted, the community member who heard about the plan secondhand, the finance lead who quietly stopped approving invoices. Stakeholder mapping is simply the habit of figuring out, on purpose, who those people are and how much each one can help or hurt your project. If you have never done it formally, this is a gentle place to start.
A stakeholder is anyone affected by your project or able to affect it: sponsors, end users, regulators, neighbours, suppliers, your own team. The goal of mapping is not to make a list of everyone. It is to be deliberate about where you put your limited time, especially in a year like 2022, when budgets are tight, materials are slow, and nobody has spare hours to waste in the wrong meetings.
Start by listing, then sort by power and interest
Begin with a brain-dump. Write down every person and group connected to the project — no judgement yet, just names and roles. Then sort them along two simple questions: how much power does this person have over the project, and how interested are they in it? Those two axes give you four practical groups.
High power, high interest — manage closely. These are your sponsors and key decision-makers. Involve them early, brief them often, and never let them be surprised.
High power, low interest — keep satisfied. A senior executive or a regulator who can stop you but rarely thinks about you. Give them what they need, on time, without overwhelming them.
Low power, high interest — keep informed. Front-line staff, community members, end users. They care deeply and are your best source of ground truth. Communicate honestly and listen.
Low power, low interest — monitor. Keep a light touch, but watch for change — a low-interest group can become very interested the moment the project touches their corner.
The point of the grid is not to rank people by importance as humans. It is to right-size your effort. You owe everyone honesty; you do not owe everyone the same number of meetings.
Influence is not the same as the org chart
The trap beginners fall into is assuming influence follows job titles. It does not. The most influential person on a capital project is often someone with no formal authority at all — the long-serving operator everyone trusts, the council member others quietly defer to, the supplier rep who controls a part nobody else can source right now. In a supply-constrained market, that supplier may hold more real power over your schedule than your own director.
So map influence as a second layer. Ask: who does each person listen to? Where are the informal alliances? Who, if they nodded, would bring three others along? A quick way to test your map is to name one decision and trace who actually has to agree before it sticks. The answer is rarely just the person who signs.
Keep the map alive
A stakeholder map drawn once and filed away is worthless. People change roles, priorities shift, a return-to-office mandate moves someone from engaged to overloaded overnight. Review the map at each project stage gate and after any major change. For the few stakeholders in your top-right corner, write down what each one wants, what worries them, and how they prefer to hear from you. That small table will save you more grief than any Gantt chart.
Done well, stakeholder mapping is not bureaucracy. It is how you make sure that when the hard moments come — a delay, a cost overrun, a scope cut — the people who matter are already on side, because you brought them along from the start rather than informing them at the end.
If you want help building a stakeholder and engagement approach that holds up under real-world pressure, XNM's program & project delivery advisory can help you map the people, not just the schedule.