Stakeholder mapping: who’s affected, who decides, who fights

A policy that helps thousands a little can still be killed by a few dozen who’d lose a lot — because they’re the ones who show up.

The idea

Before you pitch any change, list everyone it touches — not just the intended beneficiaries. The people you forget are usually the ones who mobilize against you: adjacent losers, the folks who implement it, whoever pays, whoever enforces it.

Then sort them by two things: their power to affect the decision, and their interest — how much each one personally cares. The quiet trap is concentration: a small group each bearing a big, personal cost will organize hard, while a huge group each enjoying a tiny benefit stays home. Total welfare and political reality are two different maps.

How it works

Two lenses, read in order. First the welfare lens — who gains and loses, and by how much in total. Then the mobilization lens — who will actually spend an evening at the council meeting. The gap between them is where projects die.

Welfare = group size x per-person stake   (net, aggregate)
  bus riders     ~12,000  x  +3  =  +36,000
  transit advocacy   ~150  x  +8  =   +1,200
  displaced drivers ~5,000 x  -4  =  -20,000
  shop owners        ~45   x -200 =   -9,000
  delivery ops       ~30   x -120 =   -3,600
  ----------------------------------------------
  net welfare = +37,200 - 32,600 = +4,600   good policy on paper

Mobilization = SUM(placement weight) per side
  weights:  manage closely 4  ·  keep informed 2  ·  keep satisfied 1.5  ·  monitor 0.5
  support   = riders(monitor .5) + advocacy(keep informed 2)          = 2.5
  opposition= drivers(monitor .5) + shops(manage closely 4)
              + delivery(keep informed 2)                             = 6.5

Same policy. Welfare says ship it (+4,600). Mobilization says it faces 2.6× more organized opposition than support — and almost all of it comes from the concentrated losers. That gap is the thing to manage: buy them off, phase it in, add loading zones, or lose.

When to use it

Watch out for

• Only listing the intended beneficiaries. The map is worthless if you forget implementers, funders, enforcers, and the adjacent losers — the shop two doors down, the union, the neighboring department.
• Confusing aggregate benefit with support. “This helps 12,000 people” feels decisive, but if each is helped a little, almost none of them will lift a finger for you. Diffuse benefits don’t vote.
• Underrating a small, angry group. Forty owners with a real, personal loss will out-organize thousands of mild beneficiaries every time. Count intensity, not headcount.
• Treating the map as fixed. Power and interest shift. A high-power, low-interest group (“keep satisfied”) can jump to “manage closely” the moment your project hits their radar.
• Skipping the decider. Support and opposition only matter through whoever actually chooses. Map the coalition, but aim it at the council, the exec, the buyer.

Worked example

An interviewer asks: “The city wants dedicated bus lanes on a shopping street. Who do you talk to, and in what order?” A strong answer doesn’t start with riders. It starts by naming the concentrated losers — corridor shop owners and delivery operators — because their per-person stake is high and they’re organized, so they’ll reach the council first. You’d put them in manage closely, and lead with mitigations (loading bays, a phased trial, before/after foot-traffic data). Riders and general drivers are diffuse: large in aggregate, quiet in practice — worth activating (that’s what the advocacy group is for) but not where the fight is won. Naming the concentration asymmetry out loud is the mark of someone who has actually run a change, not just costed one.