Mapping Your Stakeholders

Managing Your Boss was about the one relationship above you that shapes your work most directly. But your boss is almost never the only person whose expectations decide whether your work succeeds. There is usually a quiet approver, an affected team down the hall, a customer, a finance person who can veto a spend at the last minute. Manage your boss perfectly and still get blindsided by one of them, and the work stalls anyway.

This page gives you a way to find those people before they surprise you, and to decide how much of your limited attention each one deserves. Attention is the scarce resource here — you cannot keep everyone equally happy, and trying to is its own kind of failure. The goal is to spend your energy where it actually changes the outcome.

What a stakeholder actually is

A stakeholder is anyone affected by your work, or anyone able to affect whether it succeeds. That is a wider net than most people cast. When we hear “stakeholder” we tend to picture the people above us — the boss, the boss’s boss, the client who signs off. Those matter, but they are a fraction of the picture.

Widen it deliberately. Ask two plain questions about your piece of work:

• Who feels it? Whose day, workload, numbers, or reputation changes if this succeeds or fails?
• Who can move it? Who could speed it up, slow it down, approve it, block it, or quietly withhold the thing you need?

Anyone who answers yes to either is a stakeholder. In a hospital ward rolling out a new medication-check step, the stakeholders aren’t just the ward manager. They’re the nurses whose routine changes, the pharmacy that supplies the drugs, the night shift who weren’t in the room when it was decided, and the patients on the receiving end. In a cafe changing its ordering app, it’s the baristas, the supplier, the regulars who hate change, and the owner watching the till.

Miss one of these and you haven’t removed them from the situation — you’ve just made them a surprise instead of a plan.

The common trap — managing only upward

The most common stakeholder mistake is treating “stakeholders” as a synonym for “people senior to me.” You polish the update for your boss and the steering committee, and neglect the peer team whose cooperation you actually depend on. Then the work is approved on paper but grinds to a halt because someone sideways or below you was never brought along. Influence in the room isn’t the same as influence over the outcome. Map both.

Sorting them: interest versus influence

Once you have a list, you’ll notice it’s too long to treat everyone the same. You need a way to sort. The oldest and most useful tool for this is a simple grid built on two questions about each person:

• Influence — how much power do they have to affect the outcome? Can they approve, fund, block, or redirect the work?
• Interest — how much do they care about it? How closely will they follow it, and how much does the result touch them?

Plot every stakeholder against those two axes and four groups fall out:

              HIGH INFLUENCE
                    |
   Keep satisfied   |   Manage closely
   (powerful, but   |   (powerful AND
    not very        |    very interested)
    interested)     |
  ------------------+------------------  HIGH INTEREST →
   Monitor          |   Keep informed
   (low power,      |   (interested, but
    low interest —  |    limited power —
    minimal effort) |    the affected team)
                    |
              LOW INFLUENCE

Each quadrant asks for a different kind of attention:

• Manage closely (high influence, high interest): your core people. They can make or break the work and they care about it. Involve them, consult them early, keep them genuinely in the loop. This is where most of your relationship energy goes.
• Keep satisfied (high influence, low interest): powerful but not paying close attention — a senior executive, a regulator, the finance lead. Don’t drown them in detail; give them enough that they stay comfortable and don’t suddenly swoop in. The failure mode here is a quiet person who wakes up late and blocks you.
• Keep informed (high interest, lower influence): the people your work lands on — the team whose routine changes, the users, the frontline. They can’t approve or cancel it, but their cooperation determines whether it actually works in practice. Keep them told, and listen.
• Monitor (low interest, low influence): note them, spend little on them — but recheck now and then, because interest and influence both shift.

In practice — the warehouse rollout

A team lead is introducing new handheld scanners across a warehouse. Her instinct is to focus on the operations director who signed off — high influence. But he’s not very interested in the day-to-day; he just wants it done by quarter-end. He belongs in keep satisfied: a short monthly note that it’s on track is plenty. The people she actually needs in manage closely are the shift supervisors, who can quietly refuse to enforce the new process, and the keep informed group is the pickers whose hands touch the scanners all day. She’d been spending most of her attention on the one person who needed the least of it.

Finding the hidden stakeholders

The grid only works if the list feeding it is honest. The people who wreck projects are rarely the ones on the org chart — they’re the ones nobody thought to write down. Three types hide reliably:

• The quiet approver. Someone whose sign-off you need but who never speaks up in meetings. Legal, security, compliance, a budget holder. They seem passive right up until the moment they say no — and by then you’ve built on an assumption. Find them by asking: whose name has to be on this for it to go live?
• The affected team. A group downstream of your work who weren’t in the room when it was decided — the support team who’ll field the complaints, the night shift, the department that inherits the mess. They have high interest and often feel they have no voice, which is exactly how resentment and quiet non-cooperation start. Find them by asking: whose work changes because of mine, even if they never hear my name?
• The late veto. The person who can stop things at the eleventh hour — a nervous senior sponsor, a key customer, a union rep, a partner org. They may be silent through all the early work and then object at the finish line, when changing course is most expensive. Find them by asking: who could still say no at the very end, and have we heard from them yet?

The cure for all three is the same: surface them early, when their input is cheap, rather than late, when it’s a crisis. A “no” in week one is information. The same “no” in week ten is a disaster.

Case study — the 1986 Challenger launch

Before the January 1986 launch of the space shuttle Challenger, engineers at contractor Morton Thiokol raised concerns that the cold weather could compromise the O-ring seals. Their warning existed, but it did not carry through the decision chain with the weight it needed; management proceeded, and the shuttle broke apart shortly after launch, killing all seven aboard. Whatever the full engineering story, one management lesson is stark: a stakeholder with vital information is worthless if their voice doesn’t reach the decision at the moment it’s made. Identifying who holds critical concern is only half the job — you have to build a path for that concern to actually land before the point of no return.

Mapping the stake itself

Sorting people into quadrants tells you how much attention to spend. It doesn’t tell you what to say when you spend it. For that, go one level deeper on your manage closely and keep satisfied people — and map the stake itself. For each, answer three questions:

• What do they want? The outcome they’re hoping for — a launch by a date, a quiet quarter, more headcount, a win they can point to.
• What do they fear? The outcome they’re dreading — being blamed, being surprised, losing control, more work landing on their plate. Fear drives more stakeholder behavior than want does, and it’s the part people forget to ask about.
• What does a good outcome look like to them? Not to you — to them. Success in their language.

Written out, it looks like this:

Stakeholder: Priya (Head of Support)   Group: Keep informed
  Wants:  advance notice so she can staff and train before launch
  Fears:  a flood of tickets she wasn't warned about
  Good outcome (hers): a calm launch week, her team looks prepared
  → So: brief her two weeks early; give her the FAQ before customers see it

The moment you can fill that in for someone, you know how to talk to them. You lead with what they want, you get ahead of what they fear, and you frame progress in the terms that mean “good” to them. That’s the raw material for everything in the next pages — the expectations you’ll set, the updates you’ll send, the influence you’ll need. You can’t manage an expectation you never understood.

The evidence — fear and loss loom larger

Behavioral research generally finds that people weigh potential losses more heavily than equivalent gains — losing something feels roughly twice as bad as gaining the same thing feels good. For stakeholder work the practical takeaway holds up well: the fear column usually moves people more than the want column. A stakeholder who is comfortable that nothing bad will happen to them is far easier to work with than one you’ve dazzled with upside but left quietly anxious about the downside.

Choosing the engagement level

The whole point of the map is a decision: where does your attention go? Turn each quadrant into a simple commitment you’ll actually keep.

Manage closely  → involve early, consult on decisions, regular real conversation
Keep satisfied  → brief, confident, low-frequency updates; no surprises
Keep informed   → clear, timely, honest updates; a channel to raise concerns
Monitor         → light touch; recheck periodically in case they move

Two disciplines make this work. First, spend deliberately, not evenly. The failure mode is treating every stakeholder as equally urgent — usually by defaulting to whoever emails most or sits closest. That drains your attention onto low-stakes people and starves the ones who decide the outcome. Second, redraw the map when things change. Stakeholders move between quadrants: a quiet executive becomes intensely interested the week before a board review; a peer team’s cooperation matters far more once a deadline nears. The map is a living thing, not a one-time exercise. Re-glance at it whenever the work enters a new phase.

How it connects

This map is the foundation for the rest of the part. Once you know whose expectations matter and what each person wants and fears, you can set and manage those expectations rather than guess at them, and send status updates that actually inform the right people at the right depth. When you have to move someone who doesn’t report to you, the stake map is exactly what influence without authority draws on. And it tells you who to bring in — and how early — when something needs escalation.

Try this

Pick one live piece of your work and spend twenty minutes building its stakeholder map. First, list everyone using the two questions — who feels it and who can move it — and push yourself to name at least one hidden stakeholder (a quiet approver, an affected team, or a possible late veto). Then plot each on the interest-versus-influence grid, and for your two or three “manage closely” people, write their want, their fear, and what a good outcome looks like in their words. Notice where you’ve been overspending attention and where you’ve been underspending it.

Reflect

1. When you hear “stakeholder,” who comes to mind first — and who does that instinct reliably leave out?
2. On your current work, who is the hidden stakeholder most likely to surprise you late: a quiet approver, an affected team, or someone with a last-minute veto?
3. Are you spending your attention evenly, or deliberately? Which stakeholder is getting more of you than they warrant — and which is getting too little?
4. Pick one important stakeholder. What do they fear about your work? How confident are you that you actually know, versus assume?
5. What in your work has recently changed phase — and whose position on the grid should have moved as a result?

Show reflections

1. Most people name upward — boss, sponsor, client. The instinct reliably drops the sideways and downstream people: peer teams you depend on and the affected group who inherit your work. Those omissions are where the surprises come from.
2. The useful move is to name a specific person, not a category. Vague worry (“someone might object”) doesn’t protect you; a name lets you go get their input while it’s still cheap.
3. Honest answers usually reveal attention flowing to whoever is loudest or nearest, not whoever decides the outcome. The fix is to reallocate deliberately toward the “manage closely” quadrant, even when those people aren’t the ones pinging you.
4. If you can only guess at the fear, that’s the signal — you have a conversation to go have. Fear is rarely volunteered; you usually have to ask, gently and directly, what would make this go badly for them.
5. Any deadline approaching, any handoff, any review coming up is a phase change. The point is to build the habit of re-glancing at the map at these moments, because a stale map quietly stops matching reality.