Stakeholder thinking

Learning guide and study notes

Who is affected, and what do they need? Use it when a decision crosses teams or interests.

What you will learn

Distinguish formal authority from practical influence.
Adapt engagement to each group’s concerns and evidence needs.

What is it?

Stakeholder thinking identifies everyone who influences, operates, or experiences a change—mapping their distinct incentives, concerns, and evidence needs so cross-team initiatives succeed in practice rather than stalling in resistance.

Stakeholder mapping names the people who influence or experience a change and tailors engagement to their roles, power and interest.

Core question: Who is affected, and what do they need?
When to use it: Use it when a decision crosses teams or interests.

Tools and techniques

Key techniques

Power–interest–impact mappingMap decision-makers, operators, end users, and silent affected groups across influence and impact.
Audience-specific evidence ledgerList each group’s primary concern and the concrete assurance or support path they need.
Tiered consult–inform–involve planAgree upfront who shapes the design, who is consulted before launch, and who receives guided updates.

Procedure: think it through step by step

Work through these steps in order, applying the tools above. Write down the answer to each step before moving on.

List affected people
Include decision-makers, delivery staff, users, support teams and less-visible affected groups. [1] Source: UK Office for National Statistics — Stakeholder mapping (opens in a new tab)
Map interests
Assess influence, interest, concerns and the evidence each group needs. [1] Source: UK Office for National Statistics — Stakeholder mapping (opens in a new tab)
Plan engagement
Agree who to consult, inform and involve in decisions; update the map as positions change. [1] Source: UK Office for National Statistics — Stakeholder mapping (opens in a new tab)

Try it now

Map at least five groups for one proposed service change; state who you will consult before deciding and why.

Visual guide

Workflow chart: Stakeholder thinking — **Workflow**From situation through deliberate steps to output

Mind map: Stakeholder thinking — **Mind map**Four connected questions to keep in view

Detailed examples

Core scenario

Situation: A team changes access rules for an internal service.

How to apply: Ask users, security reviewers, service owners and support staff about different impacts.

Outcome: Design phased communication and a support path before changing the rule.

02 / Rolling out mandatory multi-factor authentication

Situation: Security announces a hard Friday cutover for new authentication rules, sparking pushback from field and support teams.

How to apply: Map the distinct workflows of warehouse staff on shared kiosks, on-call engineers, and helpdesk agents before enforcing cutover.

Outcome: Provide hardware tokens for shared kiosks, stage enrollment by group, and equip helpdesk staff with recovery runbooks first.

03 / Deprecating an internal API version

Situation: A platform team wants to retire v1 of an internal API, but three partner teams have competing roadmap deadlines.

How to apply: Identify each consumer’s migration effort, risk window, and incentive, then provide an automated compatibility shim and migration script.

Outcome: Align deprecation milestones with each team’s release cycle and retire v1 on schedule without escalations.

Illustrative examples showing how the lens changes decisions; not measured outcomes.

Practice and keep learning

Watch out: Low formal power does not mean low impact; the map must be revised rather than filed away.

Getting better at it

01 · Learn the foundationRecognize that people with low formal authority—such as frontline operators or end users—often experience the highest operational impact.
02 · Build daily fluencyBefore announcing a cross-team change, write down each group’s top question (“Will this wake me up at 2 a.m.?” “Will this slow my workflow?”) and answer it with evidence.
03 · Master under pressureBring high-impact sceptics into early design reviews so their edge cases strengthen the rollout plan before launch.

Combine this lens with others rather than relying on it alone. Browse all thinkings

Review and make it your own

The idea to remember

A workable decision accounts for who is affected, what they need, and who can influence the outcome.

An outline for your notes

Use a problem of your own. Write a short answer to each prompt, then return after trying the method.

People: list affected groups, including those with little formal power.
Interests: record needs, influence, concerns, and missing voices.
Engagement: specify who needs which evidence and when.

Check your understanding

Answer from memory before opening the suggested answer.

Is the sponsor the only stakeholder who matters?

Compare with a suggested answer

No. Users, operators, partners, and affected groups can determine adoption and consequences even if they cannot approve the budget.

How should a stakeholder map change over time?