Stakeholder Mapping

Why it matters

Before any big decision moves — a merger, a transit corridor, a plant closure, a move of a parent into care — there is a quieter question that determines whether it goes well: who has a stake in this, and who has been left off the list? The pull is to work from the parties already in the room, the ones with the loudest claim or the formal seat. But the parties who matter most are often the ones nobody named — affected by the outcome, with no voice in it, until they surface later as resistance no one planned for. Stakeholder mapping is the discipline of laying out everyone with a stake — the obvious parties and the affected-but-voiceless alike — and placing each by how much they can affect the outcome and how much they care, so the landscape is visible before anyone acts in it.

For example: a hospital system plans a merger and the working list is the obvious four — the board, the nurses’ union, the regulators, the insurers. Map it properly and the list grows to a dozen. The physicians whose referral patterns decide whether the merged system holds together. The local government that controls zoning and the trauma designation. The patients in active treatment for whom a service relocation is not an inconvenience but a rupture in care. The bondholders whose covenants quietly constrain which facilities can ever close. None of them were in the room, yet several hold more leverage over the outcome than parties who were. Map them first and you can plan for them; skip them and they become the surprise that stalls the deal six months in.

What it reveals. The full field of parties with a stake in a decision — not just the ones with a formal seat, but the affected-but-voiceless — each placed by power and interest, with its stake, likely position, and where it aligns or collides with the others.
How it changes the read. You stop asking “what do the parties at the table want?” and start asking “who has a stake here at all, who can affect this, who merely bears it — and who decided which of them counts?”
When to foreground it. At the front of a major decision, project, transition, or policy change where multiple parties have divergent stakes and leaving one out would cause downstream trouble — especially a situation you have lived in long enough that some parties have gone invisible from familiarity.
What you’d miss without it. That the most consequential party is often the one no one named; work only from the obvious list and you optimize hard around a table whose missing chairs are exactly where the resistance, the veto, or the avoidable harm was always going to come from.
Where it misleads. It is a map, not a verdict — it describes the field, it does not adjudicate who deserves standing or tell you how to negotiate; pushed past that it can read as a plan when it is only the groundwork, and a placement made from assumption rather than the party’s own voice can be confidently wrong.

Realtime examples

See real, dated analyses where this mode laid out the full field of parties behind a decision in the news — who holds power, who merely bears the outcome, and who was left off the obvious list → Stakeholder Mapping on Main Street Independent

How to invoke it in Ora

You have a decision, project, transition, or policy change with several parties holding divergent stakes, and you want the whole field laid out — power, interest, stake, position, and who has been left off the list — before any negotiation or decision work begins.

Describe the situation concretely and ask:

“Stakeholder map for [our decision / transition] — who’s involved, who has standing, what each party’s stake is. Place them by power and interest. Who else needs to be at the table?”

The phrases stakeholder map, who’s involved and who has standing, power and interest (or Mitchell Agle Wood salience), and above all who else needs to be at the table are what route you here. Bring the decision in enough detail that the parties can be inferred — the transition itself, the parties already in mind, and the dimensions on which they differ (geography, formal role, depth of stake, time pressure) — and then let the mode surface the candidates you have not named. If the decision is time-pressured say so, because urgency changes which parties are most salient; if it is politically contested, power and standing are doing the heavy lifting.

Two boundaries worth knowing. If the parties are already mapped and the live question is how to engage them — what each one really wants beneath its stated position, how to bring them to a table — that is negotiation work, not mapping, and an interest-mapping or negotiation mode fits better. And if you suspect the very list of parties was drawn to leave someone out — that the framing itself disqualified a voice — that is boundary-critique, the critical counterpart to this neutral map. This mode produces the landscape a negotiation or a decision starts from; it does not run the negotiation or make the call.

How it works

Start with the move that gives the method its name. The management scholar R. Edward Freeman, writing in 1984, made an argument that now sounds obvious but was then a quiet revolution: an organization is not answerable only to the people who own it, but to everyone who can affect it or is affected by it — its stakeholders. The word was the point. It widened the field from the handful of parties with a formal claim to the whole web of people whose lives the decision touches, including the ones with no standing to make their touch felt. And once you accept that wider field, a practical problem appears immediately. If the relevant parties are not just the obvious few but everyone affected, the list can run long — and you cannot treat a passing supplier the same way you treat the regulator who can veto the whole thing. You need a way to lay them all out and tell them apart.

The first half of the discipline, then, is breadth: get everyone on the list. The trick that makes this more than a brainstorm is to hunt deliberately in the places parties hide. The loud and the formal name themselves; the dangerous omissions are the silent ones — the users who never file a complaint, the third parties downstream of the decision, the future interests no one represents, the sub-unit whose objection has not yet been voiced. A good map canvasses those categories on purpose, because the party that gets left off the initial list is the one that surfaces later as a blocker the analysis had no place to put. Take the hospital merger: start from the obvious four and a deliberate sweep adds the physicians, the local government, the patients in treatment, the bondholders, the non-union staff — nine more parties, several of them more consequential than the four you began with.

The second half is sorting. A flat list of a dozen parties is not yet a map; you have to place them. The classic tool is a simple two-by-two grid — the power–interest grid, associated with Aubrey Mendelow — that asks two questions of each party. Power: can they actually affect the outcome? Interest: how much do they care? Cross the two and every party lands in one of four cells, each with its own way of being handled. High power, high interest — manage closely: these are the parties whose engagement makes or breaks the thing; in the merger, the board, the regulators, the physicians. High power, low interest — keep satisfied: powerful but not paying close attention, so do not let a neglected concern wake them; the insurers, whose rate leverage is real but whose daily attention is elsewhere. Low power, high interest — keep informed: they care intensely but cannot move the outcome alone, and the right move is to keep them in the loop rather than let a surprise turn them into opposition; the patients, the non-nursing staff. Low power, low interest — monitor: a light touch is enough; the routine suppliers. The grid’s whole value is that it stops you treating every party the same — it tells you where your attention is worth spending.

There is a sharper version of the sort for the cases that need it. Mitchell, Agle, and Wood argued in 1997 that one attribute is not enough to capture why some claims command attention and others do not, and proposed three: power (can they impose their will?), legitimacy (do they have recognized standing to be considered?), and urgency (is their claim time-critical?). A party holding all three is definitive — it gets attention now, and rightly. A party with only one is faint — powerful but with no standing and no pressing claim is merely dormant, latent until something activates it. The point of the three-attribute reading, called the salience model, is that it explains change: a party with legitimacy and urgency but no power — patients facing a service closure, say — is easy to dismiss until it acquires power by coalition, at which point its salience jumps and the parties who ignored it are caught flat. Stakeholder mapping uses the grid for the quick landscape and the salience model when the field is contested enough that you need to see which claims will harden and which will fade.

What ties both halves together is the discipline they share: for each party, name the stake (what it wants and what it stands to lose), the influence (where it sits on power), and the likely position — and then look across the map for where interests align into coalitions and where they collide into conflict. Two individually weak parties who can mobilize together — patients and local government through public hearings — form a coalition that amplifies both. Two parties bound by structure — a board that needs regulatory approval, regulators who need the board’s commitments — sit in a dependency that constrains every other move. The finished map is not a ranking and not a recommendation. It is the landscape: everyone who has a stake, placed by how much they can move the outcome and how much they care, with the alliances and the fault lines drawn in — the thing you want in hand before you decide or negotiate, not the decision or the negotiation itself.

Framework & implementation

This section uses Ora’s own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.

Pipeline execution

Stakeholder Mapping is an atomic mode — a single descriptive pass, not a composite of sub-analyses — and the sole member of the stakeholder-conflict territory, occupying its multi-party-descriptive position: the operation that maps the field of parties before any downstream negotiation, decision, or change work proceeds. Its posture is deliberately descriptive, not normative — it lays out the landscape, it does not adjudicate who should have standing (that critical move belongs to boundary-critique). It runs at Gear 4, Ora’s most thorough setting: a Depth analyst and a Breadth analyst work the field in parallel and then critique each other (cross-adversarial evaluation) before a consolidator integrates the result — a division that maps onto the method’s own two halves, the breadth pass sweeping for the parties easy to miss while the depth pass presses each party’s stake, power, and position past the surface read.

The pass does four things in order. It builds the stakeholder inventory — eliciting or inferring the parties with a stake, with a deliberate scan for the ones the initial frame omits (silent users, downstream third parties, future-generation interests, organizational sub-units), and flagging which parties were named in the query versus surfaced by that breadth scan. It places each party on the power–interest grid — the four cells of manage-closely, keep-satisfied, keep-informed, and monitor — and, where the field is contested enough to warrant it, runs the Mitchell-Agle-Wood salience classification, scoring power, legitimacy, and urgency to assign each party one of the seven salience classes (dormant, discretionary, demanding, dominant, dangerous, dependent, definitive). It characterizes each party’s stake — what it wants, what it stands to lose, its fallback if the decision goes against it, and any internal split that means the “party” is not actually of one mind. Finally it maps the relationships — where interests align into coalitions and where they collide into conflict, and which parties are bound by dependency — and surfaces the absent or marginalized, the affected-but-voiceless given their own explicit listing rather than folded silently into the rest.

The mode’s reasoning tools ride in its ANALYTICAL PERSPECTIVES block — the lenses it loads as it works. The load-bearing one is the stakeholder-salience lens, which supplies the power/legitimacy/urgency grid that drives the classification. Supporting it are lenses tuned to reading interests and alliances behind the surface: interest-mapping (the wants and fears beneath each stated position), coalition-formation dynamics (how individually weak parties combine into consequential blocs), and principal-agent framing (where a named party is really a representative whose interests may diverge from those it stands for).

Output contract

The deliverable is a fixed set of sections, so the map is auditable rather than a narrative: a Stakeholder Inventory (every party with its characterization and role, each flagged as named-in-frame or surfaced-by-scan, with a note on how far the inventory expanded past the original query), Power–Interest Positioning (the four grid cells, each party placed with its reasoning), a Salience Classification where warranted (the Mitchell-Agle-Wood table scoring power / legitimacy / urgency and assigning the salience class, with contested placements named rather than smoothed over), Stake Per Party (for each: what it wants, what it could lose, its fallback option, and its internal heterogeneity where it is not of one mind), Relationships Among Parties (the coalitions, dependencies, and oppositions, each with its basis and its implication for the others’ room to move), Absent or Marginalized Parties (the affected-but-voiceless surfaced explicitly, each with the kind of absence, the reason, and the stake it would press if present), and Confidence Per Finding (how strongly each layer is supported, and which placements rest on inference that direct stakeholder input would firm up). An optional RACI assignment — responsible, accountable, consulted, informed — is produced when the analysis is heading into execution and a party’s role in carrying out the decision needs explicit definition.

Origin and evidence

The mode rests on three pillars of the stakeholder-theory tradition. R. Edward Freeman’s Strategic Management: A Stakeholder Approach (1984) is the foundational text — the work that defined a stakeholder as any group that can affect or is affected by an organization’s purpose, and so widened the field of accountability from owners to the whole web of affected parties, supplying the inventory discipline at the method’s core. The classification discipline comes from Ronald Mitchell, Bradley Agle, and Donna Wood’s “Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts” (Academy of Management Review, 1997), which introduced the three-attribute salience model — power, legitimacy, urgency — and its seven classes, giving the mode a principled way to tell consequential parties from latent ones and to see which claims will rise. The quick two-by-two placement is the power–interest grid associated with Aubrey Mendelow, whose 1981 conference paper on environmental scanning popularized plotting parties by their power and their interest into the manage-closely / keep-satisfied / keep-informed / monitor quadrants. The lineage carries forward into the strategic-planning stakeholder-analysis tradition (notably John Bryson’s public-sector work) and the broad management-and-public-administration literature on stakeholder engagement.

Applications and common uses

Mergers, acquisitions, and major reorganizations. The native use: mapping the full field of affected parties — workforce, regulators, payers, community, creditors — before a consolidation moves, so the consequential omission surfaces in the plan rather than the lawsuit.
Public infrastructure and policy. A transit corridor, a wind project, a zoning change — decisions whose affected parties span businesses, residents, commuters, agencies, and advocacy groups, where the map is the precondition for legitimate consultation.
Organizational change and transitions. A program phase-out, a restructuring, a system migration, where the parties range from the formally consulted to the silently affected, and the inventory catches both.
High-stakes personal and family decisions. A care transition for an aging parent, an estate decision — small fields where the affected parties (and their divergent stakes) are no less real for being a family rather than a corporation.
As an input to negotiation or decision work. The diagnostic front end a negotiation strategy or a decision brief starts from — establishing who is in play before the question turns to how to engage them.

Failure modes and when not to use it

Frame capture. Mapping only the parties the query named and skipping the deliberate breadth scan — which reproduces exactly the blind spot the mode exists to correct. The pass canvasses the easy-to-miss categories on purpose and reports how far the inventory expanded past the initial frame.
Treating the party as monolithic. Listing “the union” or “the board” as one interest when it is internally split — senior nurses on pensions versus mid-career nurses on promotion paths — which hides the real fault lines. The stake-per-party block records internal heterogeneity rather than flattening it.
Confident placement on thin evidence. A power-interest cell or a salience class assigned from assumption can be wrong in a way the tidy grid disguises. The confidence-per-finding section flags which placements rest on inference and which would shift with direct stakeholder input, and contested classifications are surfaced, not smoothed.

When not to reach for it. When the parties are already mapped and the live question is what each one really wants beneath its stated position in a negotiation, route to interest-mapping — that is the negotiation move, not the descriptive map. When you suspect the inventory itself was drawn to leave someone out — that whose voices the framing excludes is the real question — route to boundary-critique, the critical counterpart that audits the boundary this mode takes as given. When the question is the narrower, descriptive who benefits from a single situation as it stands, route to cui-bono. And when the field is a single obvious party or two with no divergence worth mapping, the full apparatus produces ceremony, not insight.

Cui Bono — the lighter, single-situation sibling: where stakeholder mapping lays out the whole field of parties by power and interest, cui-bono asks the narrower descriptive question of who benefits from a situation as it stands.
Boundary Critique — the critical counterpart that questions what this mode takes as given: stakeholder mapping catalogs the parties already in view, while boundary critique audits whether the framing was drawn to leave someone out — reach for it when the inventory itself feels suspect.
Interest Mapping — the negotiation follow-on: once the field is mapped, interest-mapping reads what each party actually wants beneath its stated position, the move that turns a static map into a basis for engagement.
Stakeholder Salience, with Interest Mapping and Coalition Formation — the lenses this mode loads: the power/legitimacy/urgency grid that classifies the parties, plus the tools for reading the wants beneath their positions and the alliances that form across the field.