Overview
Stakeholder theory was formalized by R. Edward Freeman in Strategic Management: A Stakeholder Approach (1984, Pitman Publishing), where he defined a stakeholder as "any group or individual who can affect or is affected by the achievement of the organization's objectives." Freeman's work was primarily directed at corporate strategy — arguing that firms must account for stakeholders beyond just shareholders — but consulting quickly adopted the underlying framework as a diagnostic tool for mapping the political landscape of any engagement.
The Power/Interest grid — the most widely used stakeholder mapping tool — is attributed to Aubrey Mendelow, who presented the concept at the 1981 International Conference of Information Systems. It places stakeholders on a two-by-two matrix by their power over the outcome and their interest in it:
- High power, high interest: Manage closely — these are your primary audience; misread them and the engagement fails
- High power, low interest: Keep satisfied — they can block you; don't give them a reason to
- Low power, high interest: Keep informed — they'll amplify your message if it serves their interests
- Low power, low interest: Monitor — periodic check-in is sufficient
Beyond the basic grid, experienced consultants also track: stance (supportive / neutral / resistant), influence channels (formal authority, informal networks, expertise, relationships), and stakes (what does this person gain or lose if the recommendation is adopted).
When to Use It
Early in the engagement — ideally as part of initial scoping — and again when the recommendation is being formed. The map is most useful at two moments: deciding how to structure the analysis and whose input to seek; and planning how to land the recommendation politically.
In Consulting Club sessions, stakeholder mapping is useful for understanding the political dimension of the client's problem, even when the presenting question is analytical. Most real business problems have stakeholder dynamics embedded in them — who has to approve this, who will resist it, whose interests are affected.
How It Works
- Generate a full list — brainstorm everyone who touches this situation. Don't edit yet; the goal is to be exhaustive.
- Assess power — who can actually block or champion the recommendation? Consider formal authority, budget control, and informal influence. Power is not the same as seniority.
- Assess interest — how much does this person care about the outcome? High interest means engaged; low interest means they may be unaware or indifferent.
- Plot on the grid — assign each stakeholder to a quadrant.
- Add stance — mark each as supportive, neutral, or resistant. This turns the map from descriptive to strategic.
- Identify influence relationships — who influences whom? Sometimes the highest-leverage move is winning over an informal influencer, not the formal decision-maker.
- Develop an engagement strategy — what do you do differently for each quadrant? Manage closely means regular updates and direct access. Keep satisfied means proactive reassurance. Keep informed means clear, timely communication. Monitor means lightweight check-ins.
Running It in a Session
During the first 20 minutes of team work, have the Scribe build a rough stakeholder map while the Analyst begins framework analysis. These can run in parallel — the map doesn't require the full team, just someone who listened carefully to the Client brief.
The Lead Consultant should use the map to shape the recommendation — specifically: who needs to be convinced for this to actually happen, and what will move them? The best Consulting Club recommendations include a stakeholder dimension: not just "here's what you should do" but "here's who you need to bring along, and how."
At the debrief, ask whether the recommendation was politically feasible or whether it ignored obvious resistance. A technically correct recommendation that has no path to adoption is an incomplete recommendation.
Common Pitfalls
- Mapping without acting — producing a careful map and then ignoring it; the point is to change how you engage
- Static thinking — stakeholder positions shift as the engagement progresses; a resistant stakeholder may become supportive when they understand what's in it for them
- Forgetting informal power — the executive assistant who controls calendar access, the technical lead whose buy-in is required for implementation, the former executive whose opinion is still sought: these rarely appear on org charts
- Conflating who you're mapping for — sometimes you need to map stakeholders in the client's world (to shape the recommendation); sometimes you need to map stakeholders in the engagement itself (to know who to interview and who to keep informed)
- Power without path — a high-power, high-interest resistant stakeholder is your biggest risk; the map identifies them but doesn't tell you how to move them; that requires a separate strategy
References & Further Reading
- Freeman, R. Edward. Strategic Management: A Stakeholder Approach (1984, Pitman Publishing)
- Mendelow, Aubrey. "Environmental Scanning: The Impact of the Stakeholder Concept" (1981, Proceedings of the 2nd International Conference on Information Systems)
Recommended Books
- Strategic Management: A Stakeholder Approach — R. Edward Freeman
- Influence Without Authority — Cohen & Bradford
- The Trusted Advisor — Maister, Green & Galford