You can have the right plan and still lose. Most initiatives that stall don't fail on the merits, they fail because someone with quiet influence was never brought along, or because a leader poured weeks of attention into a vocal group that, when it counted, couldn't actually move anything. Stakeholder mapping is the cheap, unglamorous habit that catches both mistakes before they cost you.

The quick version

  • A stakeholder is anyone who can affect, or is affected by, what you're trying to do (Freeman, 1984). That's a wider net than the people who happen to be in the room.
  • The power/interest grid sorts them on two axes, how much they can shape the outcome, and how much they care, into four groups, each needing a different kind of attention.
  • The point isn't the picture; it's the conversation. The grid forces you to say out loud who is being under-managed and over-managed, then change where your effort goes.
  • Treat it as a lens, not a verdict. Power and interest move, the labels oversimplify, and a tidy quadrant can hide a stakeholder's legitimacy or urgency. Re-map when the situation shifts.

The idea in depth

Start with the word itself. In Strategic Management: A Stakeholder Approach (Pitman, 1984), R. Edward Freeman defined a stakeholder as "any group or individual who can affect or is affected by the achievement of the organization's objectives." It sounds obvious until you apply it honestly: your stakeholders are not just your sponsor and your boss. They include the team two doors down whose roadmap you're about to disrupt, the finance lead who never attends your meetings but signs off your budget, and the customers who feel the change without ever being consulted. The first move stakeholder mapping makes is simply widening the list, naming people you'd rather not think about because managing them is work.

Once you have the list, you need a way to prioritise it, because attention is finite and not everyone deserves the same. The most-used tool here is the power/interest grid, often called Mendelow's matrix after Aubrey Mendelow's 1991 paper on environmental scanning and the stakeholder concept. Colin Eden and Fran Ackermann developed the grid into a practical mapping technique in Making Strategy (Sage, 1998), giving the four quadrants memorable names: players (high power, high interest), subjects (high interest, low power), context setters (high power, low interest), and the crowd (low on both). A worth-knowing wrinkle on attribution: later editions of the standard strategy textbook Exploring Strategy cite Newcombe (2003) for the grid, who in turn traces it back to earlier editions of that same book, so the "Mendelow's matrix" label is more a convention than a clean lineage. The tool is real and useful; just don't over-invest in who exactly invented it.

The grid's quadrants are usually paired with four engagement postures, manage closely, keep satisfied, keep informed, and monitor (minimal effort). The practical instruction is blunt: match the intensity of your effort to where each person actually sits, not to how loud they are. The high-power, low-interest "context setter" is the one leaders most often misread, they're quiet, so you ignore them, right up to the moment their disinterest curdles into a veto. Keeping them satisfied means short, low-frequency, no-surprises updates: enough that they never feel blindsided, not so much that you waste their time and yours.

quadrantChart
    title Power / interest grid
    x-axis Low interest --> High interest
    y-axis Low power --> High power
    quadrant-1 Players: manage closely
    quadrant-2 Context setters: keep satisfied
    quadrant-3 Crowd: monitor
    quadrant-4 Subjects: keep informed
The four quadrants and the engagement posture each implies. Leaders Loop

There's a second, more demanding model worth knowing because it patches a real hole in the grid. Mitchell, Agle and Wood, writing in the Academy of Management Review (1997), argued that who counts depends on three attributes, not two: power, legitimacy (whether their claim is seen as proper and appropriate), and urgency (whether it's time-sensitive and they care intensely). Their key insight is that salience, how much a manager actually attends to a stakeholder, rises as a person accumulates more of these attributes, and that the attributes are not fixed: a stakeholder can acquire urgency overnight, or borrow power by forming a coalition. The discipline this buys you: before you dismiss a low-power group, ask whether their claim is legitimate and whether it could become urgent. A frontline team with no formal authority and a fair grievance is one viral incident away from being the most salient stakeholder you have.

And the honest limitation: these are lenses, not laws. The grid's empirical support is thin compared with how confidently it's taught, much of its authority comes from textbook repetition rather than tested prediction. It flattens people into two crude dimensions, it freezes a dynamic situation into a static snapshot, and it quietly invites you to treat "low interest, low power" as "ignore," which is exactly how you end up surprised. Position on the grid is also a judgement call, not a measurement, two honest people will place the same stakeholder in different boxes. Use the map to structure a conversation, then hold it loosely.

A worked example

Consider a mid-sized firm, figures here are illustrative, rolling out a new shared CRM across sales, service and marketing. The project lead, Dana, lists the obvious stakeholders: her exec sponsor, the two divisional sales directors, and the IT delivery team. Mapping them, she places the sponsor and the sales directors as players (high power, high interest) and resolves to manage them closely with weekly working sessions.

The map earns its keep on the people she nearly left off. The Head of Compliance has shown zero interest in the CRM, but she can halt the launch on a data-handling objection. That's a classic context setter: high power, low interest. Dana's move is a single 20-minute briefing up front and a one-paragraph update at each milestone, so compliance is never surprised into saying no. Meanwhile the frontline service reps, the people who'll live in the tool all day, have intense interest and almost no formal power: subjects. The instinct is to "keep informed" with a launch email, but Mitchell, Agle and Wood's lens flags the risk: their claim is legitimate and could turn urgent fast if the tool slows their day. Dana upgrades her approach, recruiting two reps as design partners. That converts a group who could have quietly tanked adoption into advocates, and surfaces a workflow problem early, while it's still cheap to fix. The grid didn't make the decision. It made sure the decision wasn't made blind.

flowchart TD
    A(["List everyone who can affect or is affected"]) --> B(["Place each on power x interest"])
    B --> C(["Pick the posture per quadrant"])
    C --> D(["Check: any legitimate or urgent claim hiding in low-power?"])
    D --> E(["Act, then re-map when the situation shifts"])
Stakeholder mapping as a loop, not a one-off artefact. Leaders Loop

Frequently asked questions

Is the power/interest grid the same as Mendelow's matrix?

In everyday use, yes, "Mendelow's matrix" is the common name for the power/interest grid, after Mendelow's 1991 paper. Be aware the attribution is muddier than the label suggests: Eden and Ackermann's Making Strategy (1998) gave the quadrants their well-known names, and some strategy texts cite Newcombe (2003) instead. The tool matters more than the credit.

How is "power" different from "interest"?

Power is the ability to shape the outcome, through budget, authority, a veto, scarce expertise, or informal sway. Interest is how much the person cares about it. They're independent: a regulator can have enormous power and near-zero day-to-day interest, while an affected team can care intensely yet hold no levers. Mapping them separately is the whole point; it stops you conflating "loud" with "decisive."

How often should I re-map?

Whenever the situation moves, a reorganisation, a budget shift, a new sponsor, a public incident. Mitchell, Agle and Wood (1997) stress that power, legitimacy and urgency are dynamic, so a stakeholder map made once and filed away ages badly. For anything live and contested, a quick re-check at each major milestone is enough.

Isn't this just politics dressed up as a diagram?

It's politics made explicit, which is healthier than pretending it isn't there. Mapping doesn't tell you to manipulate anyone; it tells you to spend your limited attention where it changes outcomes, and to bring along people you'd otherwise overlook. The ethical line is in how you engage, honestly and openly, not in whether you think about influence at all.

What's the single most common mistake?

Treating the bottom-left "monitor" quadrant as "ignore." Low power and low interest today is not a permanent state, and a legitimate claim there can acquire urgency overnight. Watch that corner; don't write it off.

Related in the Toolkit

Mapping tells you who; the harder half is the how. Once you know your players and context setters, the work shifts to securing senior-stakeholder buy-in and to reading the informal currents around them, see reading & navigating organisational politics & power.

Where to go next