Stakeholder mapping

Stakeholder mapping makes explicit who can affect a decision, who will be affected by it, and what the team still needs to learn from them. A useful map leads to an engagement plan. A grid full of names is only a starting point.

There is no single universal stakeholder map. John Bryson’s review describes several identification and analysis techniques for different purposes, including power–interest grids and influence relationships. Treat the method below as a practical synthesis rather than a reproduction of one proprietary template. Bryson, 2004

When to use it

Map stakeholders before a change affects working practices, while defining an innovation opportunity, or when a project repeatedly encounters surprises from people outside the core team. Revisit the map when scope, leadership, delivery arrangements, or affected groups change.

Do not use the map to label people as obstacles or to decide that people with little organizational power deserve little attention. Someone can be highly affected by a decision while having almost no influence over it. Also avoid treating an internal workshop as consultation: a team’s beliefs about someone are not that person’s stated needs.

If the change is already decided, be honest about what people can still influence. Participation requires a meaningful opportunity to inform decisions, and it extends beyond a single meeting. The US EPA’s public participation guidance is useful on this boundary, although its public-sector setting differs from an internal business project. EPA introduction

Expected outcome

Aim for four connected outputs: a stakeholder register, a provisional map, a list of unknowns to verify, and a short engagement plan with owners. Mark each judgment as observed, reported by the stakeholder, or assumed. This makes the uncertainty useful instead of hiding it behind precise-looking positions.

For a first pass, allow 75 minutes with four to eight people who know different parts of the work. Include frontline and delivery perspectives as well as management. Participation in this mapping group does not automatically make it representative; check who is absent.

Prepare and gather materials

Write the decision or change at the top of the board. “New case-management system” is too broad if the immediate decision is how to pilot one intake workflow. Specify scope, affected locations, time horizon, and what remains open.

Gather a process outline, existing contact lists, earlier consultation findings, and known dependencies. Do not compile unnecessary personal information. Use role or group names where individual names do not help the work. Agree who may see the map, particularly if it contains uncertain judgments about influence or concerns.

Prepare a register with these columns: stakeholder, relationship to the change, potential effect, influence, stated needs, evidence or assumption, engagement action, owner, and review date. The accompanying visual map uses horizontal degree of impact and vertical influence. This guide deliberately includes impact so that low-power, highly affected groups remain visible.

Open the printable stakeholder worksheet.

A 75-minute mapping session

0–10 minutes: define the decision

Ask: “What can this group decide, what requires approval, and what can stakeholders still change?” Record the answer. Without this boundary, the discussion tends to drift between a broad transformation and a narrow implementation task.

Agree working definitions. Influence means the ability to shape the decision or its implementation in this context. Impact means the degree to which the change alters someone’s work, access, costs, benefits, or risks. Neither is a permanent personal characteristic.

10–25 minutes: identify stakeholders

Begin with independent writing, then collect names or groups in a round. Ask who uses the current service, delivers it, supports it, funds it, authorizes it, depends on its data, and experiences its errors. Include people outside the formal organization where relevant.

Silent generation followed by structured sharing is also used in nominal group technique to support broad participation. Here it is an adapted collection step, not a claim that the whole session is a formal consensus exercise. CDC guidance

Look for categories that hide important differences. “Employees” may include managers, temporary workers, night-shift staff, and people using assistive technology. Separate groups when their experience or engagement needs differ, while avoiding so much detail that the register becomes unmaintainable.

25–40 minutes: examine impact and influence

Place each stakeholder provisionally. Ask for the reasoning behind the position: “What can this group actually affect?” and “What changes for them on a difficult working day?”

Use rough categories rather than false numerical precision. Add an uncertainty marker where the team has little evidence. If participants disagree, keep both interpretations and create a question to investigate. A tidy map is less valuable than an honest one.

Do not automatically describe high influence as opposition or high interest as support. Someone may care deeply because they expect harm. Record support, concern, and unknown positions separately, using the person’s own account when available.

40–55 minutes: find missing voices and relationships

Trace dependencies. A local supervisor may have modest formal authority but determine whether colleagues can attend training. A supplier may control a technical dependency without having much interest in the internal change.

Ask: “Who bears the cost if this works badly?” “Who cannot easily attend our normal meetings?” and “Whose representative have we assumed speaks for everyone?” The EPA emphasizes listening, communication, and collaboration as participation skills. A diagram cannot substitute for those behaviors. EPA foundational skills

Add stakeholders discovered through these questions. Record which connections need confirmation with the people involved.

55–70 minutes: design engagement actions

For each priority relationship, specify a purpose and an action. Replace “communicate with frontline staff” with “observe an intake shift and test the draft handoff with two staff members before the pilot plan is approved.”

Choose a method that fits the question: an interview to understand an experience, a walkthrough to check a workflow, a small design session to shape an option, or a decision briefing to secure accountable approval. Clarify whether the activity informs, consults, involves, or delegates a decision; avoid implying authority that participants do not have.

Assign one owner and a date. Record how the team will show what happened to the input received. If no change can be made, explain that constraint before asking people for time.

70–75 minutes: confirm the first follow-ups

Read out the three most urgent unknowns, the actions that address them, and the next review date. Check that the map is marked provisional. Ask someone who did not lead the exercise to explain who is most affected and whose perspective remains missing.

Hypothetical example: changing appointment booking

A service team plans to pilot online appointment booking. Its first map includes customers, reception staff, IT, and the service manager. During the missing-voices step, it adds people booking on behalf of relatives, customers who cannot use the digital channel, and staff who handle cancellations.

The team initially gives reception staff low influence because they do not approve the software. A discussion of real work reveals that they manage exceptions and can identify which bookings require specialist handling. Their implementation influence is higher than the organization chart suggests.

The resulting plan includes a workflow walkthrough with reception staff, accessible testing with customers using different channels, and a technical dependency review. The team records that it has not yet heard from people who avoid the service entirely. It does not claim that the map represents their needs.

Success for this exercise is a better research and engagement plan. Whether online booking improves access remains an empirical question for the pilot.

A CLOSER LOOK

Turn a judgment into something to verify.

1. 01
   Provisional judgmentThis group may be strongly affected but have little formal influence.
2. 02
   Direct inquiryAsk what changes in its work and which assumptions are wrong.
3. 03
   Engagement commitmentAgree a route for input, an owner and a review point.

Common mistakes and adaptations

The map is made once and filed away. Review it at a decision milestone and after new evidence. Date each significant judgment so future readers know when it was plausible.

The team uses “resistant” as a category. Describe the concern: loss of discretion, extra workload, unreliable data, or disagreement with the purpose. That gives the team something to investigate.

The engagement plan consists entirely of announcements. Match the method to what remains uncertain. Sending information cannot answer a question about lived experience.

Low influence becomes low priority. Use impact and access needs as separate considerations. Invite perspectives through channels people can realistically use, including asynchronous contributions and smaller conversations.

For distributed teams, collect preliminary entries before the session and reserve meeting time for disagreements and omissions. For a large program, keep local maps and a shared dependency register rather than forcing every stakeholder into one unreadable chart. For sensitive situations, limit access to working judgments and publish a neutral account of engagement commitments.

Evidence, limitations, and next steps

Stakeholder analysis has a substantial conceptual and applied literature, but a particular two-axis map is a simplification. Bryson’s work supports choosing among techniques for the task; it does not validate this session’s timing or demonstrate that a grid alone causes project success. The 75-minute process, prompts, and example are original practice guidance.

All classifications depend on who creates them and what they know. The most consequential limitation is representation: an apparently comprehensive register may still exclude people with less access to the project team.

Use the map to guide actual conversations, then revise it. Read change management for the wider implementation context. If people have many questions worth discussing together, use Lean Coffee. Once a concrete plan exists, a premortem can explore how overlooked dependencies might cause problems.