Stakeholder Mapping

---

Origins

Stakeholder analysis as a discipline comes from project management practice and management science, formalized in the 1980s by R. Edward Freeman in Strategic Management: A Stakeholder Approach¹. The Power/Interest grid — the most common visual format — was popularized by Aubrey Mendelow and refined through decades of consulting practice.

Agile teams adopted stakeholder mapping as projects gave way to products and continuous delivery. The set of people who could influence or be affected by a piece of work expanded from "the project sponsor and the testing team" to a more complex landscape: customers, internal users, leadership, legal, security, support, sales, downstream teams. Stakeholder mapping made that landscape visible enough to engage with deliberately.

The Power/Interest Grid

The most widely-used format is a 2×2 of:

• Power: how much influence this stakeholder has over the outcome — can they block, accelerate, fund, kill?
• Interest: how much they care about the outcome — how affected they are, how engaged they want to be.

The four quadrants suggest engagement strategy:

• High power, high interest — Manage closely: deep, frequent engagement; partnership.
• High power, low interest — Keep satisfied: enough engagement to keep them on board; don't overwhelm.
• Low power, high interest — Keep informed: regular communication; they care and they can amplify.
• Low power, low interest — Monitor: minimal effort; check occasionally.

The grid is descriptive, not prescriptive. A "Monitor" stakeholder who suddenly gains power needs to be moved to a different engagement plan; the map is a working artifact, not a final document.

Other Useful Lenses

Influence / Affected

A variant grid plots influence (how much they can shape the outcome) against how affected they are (how much the outcome touches them). This produces different engagement strategies than Power/Interest: high-affected, low-influence stakeholders are easy to overlook and create real harm if ignored.

Stakeholder Onion

Concentric rings: the core team in the center, immediate stakeholders in the next ring, broader stakeholders further out, and the wider context at the edge. Useful for thinking about communication cadence — the inner rings get more frequent contact than the outer.

RACI / DACI

Per-decision mapping: who is Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), Informed (kept aware). DACI variant: Driver (moves it forward), Approver (signs off), Contributor, Informed. Useful when stakeholder confusion is decision-specific.

Running a Stakeholder Mapping Session

1. Define the scope (5 min)

What initiative, decision, or change are we mapping stakeholders for? Specific is better — "this feature" rather than "the product."

2. List all stakeholders (15 min)

Silent generation. Push past the obvious. Often the most important stakeholders are the ones nobody thought to name.

3. Place on the grid (15–20 min)

The team discusses and places each stakeholder. Disagreements about placement are productive — they surface different team members' models of who matters.

4. Identify engagement strategy (10 min)

For each high-power and high-interest stakeholder, name the specific engagement plan: cadence, channel, owner.

5. Spot the missing voices (10 min)

Which affected groups don't have someone on the map? Often the high-affected, low-influence quadrant is empty not because no one is there, but because no one is loud enough to be named.

Common Pitfalls

• Loud voices only: the map captures the stakeholders who already make themselves known. Quieter affected groups get overlooked. Force the question: who is affected but not represented?
• Static map: drawn at project kickoff, never updated. Stakeholders enter and leave; influence shifts. Revisit when major decisions approach.
• Influence as personality: confusing "who's loud in meetings" with "who has actual organizational power." The map should reflect formal and informal power realistically.
• Engagement-as-checklist: assigning a cadence to each stakeholder without thinking about what they actually need. A monthly email to a stakeholder who needs weekly partnership is worse than no plan at all.
• Treating it as confidential: a private stakeholder map can feel manipulative. Where appropriate, share the map with stakeholders themselves — "this is how we're thinking about engagement" — and let them push back on where they were placed.

Coaching Tips

Push Past the Obvious

The first list of stakeholders usually misses several. Ask "who else is affected? Who else has influence?" until the team has to think.

Hunt for the Missing Voices

An empty high-affected, low-influence quadrant is usually wrong, not empty. Surface the quiet affected groups before they become a problem.

Distinguish Loudness from Power

The stakeholder who emails most is not necessarily the most powerful. Map based on who can actually shape outcomes, not who shouts loudest.

Design Engagement Per-Person

Different stakeholders need different cadences and channels. A standardized engagement plan misses what each actually wants.

Refresh Before Big Decisions

Before a major milestone, revisit the map. New stakeholders, shifting power, changed interest — the picture has usually moved since you drew it.

Share When Appropriate

The map can feel manipulative if kept secret. Where the working relationship allows, share it with stakeholders themselves — the conversation about placement often produces better outcomes than any internal speculation would.

Summary

Stakeholder mapping is the difference between engagement happening on purpose and happening by accident. A team without a map serves the stakeholders who are loudest; the quietest affected groups go unnoticed until they show up at the end of the project with a veto. A team with a map can design engagement deliberately — deep partnership with the high-power, high-interest stakeholders; honest communication with the affected; appropriate minimums with everyone else.

The practice is most useful before major decisions and before significant rollouts. It is a working artifact, not a one-time exercise; the map that worked at kickoff usually needs revising before launch. Teams that treat it that way avoid most of the political surprises that derail otherwise-successful work.

Back to Experience & Story Mapping