Most frameworks focus on problems, decisions, and futures. Stakeholder mapping focuses on people. Specifically: who are the people and groups that have influence over whether a decision succeeds or fails, and what do they actually want?

The structure is simple: for any decision or initiative, you identify everyone who has a stake in the outcome: anyone who can help it succeed, block it, accelerate it, or undermine it. Then you map them based on two dimensions: how much power they have over the outcome, and how aligned they are with what you’re trying to do.

Why this matters. Analysis is completely useless if the wrong person blocks it. You can build a perfect scenario plan. You can identify the exact right acquisition target. You can compress the most elegant SCR brief. An then the CFO kills it and because nobody mapped the fact that they’re threatened by AI investment. Or the head of engineering quietly sabotages integration because he wasn’t consulted. Or the board chair has a relationship with competing vendor that nobody knew about. The best strategic thinking in the world fails when it ignores the human terrain. Stakeholder mapping is how you read that terrain before you step on a landmine. Executives might be stuck, and it’s often not because she doesn’t know the right strategic move. But because she can’t get it past the people around her. The stakeholder mapping can help her see who’s in the way, who’s on her side, who needs to be moved, and how.

Who developed it:

• Stakeholder analysis has roots in strategic management theory from the 1980s. R. Edward Freeman’s book Strategic Management: A Stakeholder Approach (1984) formalized the idea that organizations must manage relationships with multiple groups who affect or are affected by their decisions, not just shareholders but employees, customers, regulators, communities, suppliers.
• The power-interest grid (the specific 2x2 mapping tool) was developed by Aubrey Mendelow in 1991. It became standard practice in project management, change management, political strategy, and consulting. Every major consulting firm uses some version of it.

The power-alignment matrix. The classic version uses two axes:

• Power: How much ability does this stakeholder have to affect the outcome? Can they approve it, fund it, block it, slow it down, speed it up? High power means they can make or break the initiative. Low power means they’re affected by it but can’t change it.
• Alignment: How supportive are they of what you’re trying to do? High alignment means they want the same outcome you want. Low alignment means they’re opposed, skeptical, or have competing priorities.
• Four quadrants:
  
  • High power, high alignment: Champions. Those are your strongest allies. They want what you want and they have the power to make it happen. Strategy: keep them engaged, give them ammunition to advocate for you, don’t take them for granted.
  • High power, low alignment: Blockers. The most dangerous quadrant. They have the power to kill your initiative and they don’t support it. Strategy: understand why they’re opposed. Is it a value disagreement? A resource competition? A personal threat? A lack of information? Each cause requires a different approach. This quadrant is where most strategic initiatives die.
  • Low power, high alignment: Supporters. They want you to succeed but can’t directly make it happen. Strategy: find ways to amplify their influence. Can they provide data, testimonials, internal advocacy? Can they be elevated to positions of more influence?
  • Low power, low alignment: Observers. They’re not aligned and they can’t do much about it anyway. Strategy: monitor but don’t invest significant energy. Unless their power changes, which it can.‍

Key disciplines:

• Map the real power, not the org chart power. The person with the most formal authority isn’t always the person with the most actual influence. Sometimes it’s the CFO’s trusted advisor. Sometimes it’s the engineer everyone respects. Sometimes it’s the executive assistant who controls the calendar and therefore controls access. Real power is about influence and not title.
• Understand the “why” behind the alignment. Someone opposing your initiative isn’t just “a blocker,” because they might have good reasons. Maybe the AI investment threatens their budget. Maybe they had a bad experience with a previous technology transformation. Maybe they genuinely believe it’s the wrong strategy and they might be right. Until you understand their why, you can’t move them.
• Stakeholder positions change over time. Someone who starts as a blocker might become a champion if their concerns are addressed. Someone who starts as a champion might become opposed if they feel excluded from the process. The map is dynamic. It needs regular updating.
• Hidden stakeholders matter. The most dangerous stakeholder is the one you didn’t know existed. The board member who has an opinion but hasn’t voiced it. The regulator who’s watching but hasn’t acted. The customer group that will react strongly but hasn’t been consulted. Always ask: who’s missing from this map?

Common pitfalls:

1. ‍Mapping only the obvious stakeholders. The CEO, the board, the direct reports. Missing the mid-level managers who will actually implement the change. Missing the external stakeholders: regulators, key customers, partners, who can derail things from outside.‍
2. Assuming alignment is permanent. Champions can become blockers if they feel betrayed, excluded, or surprised. Never surprise your champions. Keep them informed before public announcements.‍
3. Treating all blockers the same way. A blocker who’s opposed because they lack information needs education. A blocker who’s opposed because the initiative threatens their power needs a different approach entirely: maybe a role in the new structure that preserves their influence. A blocker who’s ideologically opposed may need to be worked around rather than converted. Diagnosis before strategy.‍
4. Ignoring the emotional dimension. Stakeholders aren’t rational actors making calculated decisions about organizational resources. They’re humans with egos, fears, ambitions, relationships, and histories. The CFO might block the AI investment not because the numbers don't work but because the CTO proposed it and they have a rivalry. If you only analyze the rational arguments, you’ll miss the real dynamics.

Variations: 

1. ‍Influence network mapping. Instead of a 2x2, you draw the actual relationship between stakeholders. Who influences whom? Who trusts whom? Where are the alliances and the tensions? This reveals the informal power structure that the org chart hides.‍
2. Stakeholder journey mapping. For each key stakeholder, you trace their likely emotional journey through the initiative. Where will they feel excited? Where will they feel threatened? Where will they need reassurance? This helps you anticipate resistance before it materializes.‍
3. Coalition analysis Instead of mapping individual stakeholders, you map coalitions: groups of stakeholders who tend to move together. If you win over the coalition leader, you win the group. This is how political strategists think.‍
4. RACI matrix. A simpler tool that maps who is Responsible, Accountable, Consulted, and informed for each decision. Less strategic than stakeholder mapping but useful for operational clarity.
   

How to go about it:

• Step 1: Define the initiative and the decision. Before mapping anyone, you need absolute clarity on what you’re mapping stakeholders for. “The company’s future” is too broad. “The integration of the acquired AI security startup over the next 12 months” is specific. The initiative determines who has a stake. Different initiatives produce different maps.
• Step 2: Brainstorm the stakeholder universe. Go wide. List every person, role, group, or entity that could affect or be affected by the initiative. Don’t filter yet. Don’t assess power or alignment. Just generate names. Work through it systematically using categories to make sure you don’t miss anyone.
  
  • Example:
    
    • Internal: who in leadership, middle management, engineering, sales, marketing, support, operations, HR, legal, finance will be affected by this integration? Who has budget authority? Who controls key resources? Who manages the teams that will do the actual integration work?
    • External: customers of both companies, key partners, investors or board members, regulators, industry analysts, competitors who might poach talent during the transition.
    • Adjacent: people who aren’t directly involved but whose opinion carries weight. The CEO’s trusted advisor. The broad member who was skeptical about the acquisition. The industry journalist who covers cybersecurity.
  • The goal is to be surprised by your own list. If everyone on it is obvious, you haven’t gone wide enough. The most dangerous stakeholders are the ones you almost forgot to include.
• Step 3: Assess power.
  
  • For each stakeholder ask: how much ability does this person or group have to make the integration succeed or fail?
  • High power indicators: they control budget, they control key technical resources, they have hiring or firing authority over integration team members, they have CEO’s ear, they can influence the board, they own critical customer relationships, they hold knowledge that nobody else has, they can delay timelines by withholding cooperation.
  • Low power indicators: they’re affected by the outcome but can’t change it, they have opinions but no decision authority, they’re too junior to influence the process, they’re external with no contractual leverage.
  • Be honest about informal power. The startup’s lead engineer might have no formal authority but if she leaves, she takes the AI architecture knowledge with her. That’s enormous power even without a title.
  • Questions to answer:
    
    • If this person or group quit, disappeared, or refused to cooperate tomorrow, would the integration stall or break? If yes, high power. If the work would continue without major disruption, low power.
    • Can this person or group make a decision that changes the timeline, budget, or scope of the integration without needing approval from someone else? If yes, high power. If they need permission to act, low power.
    • Does anyone else in the organization depend on this person’s knowledge, relationships, or output to do their own work on the integration? If yes, they have dependency power, people can’t move without them, which gives them leverage even without formal authority.
• Step 4: Assess alignment.
  
  • For each stakeholder, ask: does this person want the integration to succeed, and do they want it to succeed in the way we’re planning it?
  • High alignment indicators: they benefit from the integration, their role grows or is secured, their priorities are served, they were consulted and feel ownership, they believe in the strategic rationale.
  • Low alignment indicators: their budget is threatened, their team is being restructured, their authority is diminished, they weren’t consulted and feel blindsided, they disagreed with the acquisition in the first place, they have competing priorities that the integration disrupts, their personal relationships are threatened.
  • Uncertain alignment is common and important to flag. Many stakeholders won’t know how they feel until integration starts affecting them personally. These are the ones who could tip either direction depending on how the process is managed.
  • The critical discipline: assess alignment on their interest, no their words. Someone might say “I fully support this” while quietly undermining it because the integration threatens their power base. Look at what they stand to gain or lose, not what they declare publicly.
  • One more note: This exercise is based on assumptions, not data. You’re mapping with incomplete information. To make things more doable, for each stakeholder, ask three questions:
    
    • Does this X {change} make their job bigger or smaller? If bigger, lean toward aligned. If smaller, lean toward opposed.
    • Does this X {change} increase or decrease their authority? If it increases their scope but puts them under more scrutiny, the alignment is uncertain.
    • Were they involved in the decision to acquire, or was it handed to them? People who chose this path tend to be aligned. People who had it imposed tend to start skeptical.
      
  • Map them based on your best read. Mark anyone you’re genuinely uncertain about. In a real engagement, those uncertain stakeholders would be the first people you’d want to have informal conversations with to understand where they actually stand.
• Step five: Plot the map. Place each stakeholder on the power-alignment grid. For quadrants: champions (high power, high alignment), blockers (high power, low alignment), supporters (low power, high alignment), observers (low power, low alignment). Mark anyone whose position is uncertain with a flag. These are your swing stakeholders, they could move into any quadrant depending on how the integration unfolds.
• Step six. Diagnose the blockers. This is where the real work begins. For every stakeholder in the blocker quadrant, you need to understand why they’re opposed. Not just “they don’t support it” but the specific mechanism of their opposition.
  
  • Categories of opposition:
    
    • Information deficit: they don’t understand the plan well enough to support it. Solution: education, involvement, transparency.
    • Resource threat: the integration takes budget, headcount, or attention away from their priorities. Solution: demonstrate how the integration serves their goals, or negotiate resources guarantees.
    • Power threat: their authority, influence, or organizational position is diminished by the integration. Solution: design a role for them in the new structure that preserves or enhances their influence.
    • Values disagreement: they genuinely believe the strategy is wrong. Solution: engage their concerns seriously. They might be seeing a risk everyone else is missing. If their concerns are addressed and they still disagree, you may need to work around them rather than convert them.
    • Personal dynamics: they oppose it because of who proposed it, who benefits from it, or who they’d have to work with. Solution: the hardest to address because it’s emotional, not rational. Often requires the CEO to have a direct, private conversation.
    • Relationship history: they had a bad experience with a previous acquisition, a previous transformation, or a previous initiative by the same leaders. Solution: acknowledge the history explicitly and demonstrate what’s different this time.
• Step seven: Design stakeholder strategies. For each quadrant, you need a different approach:
  
  • Champions: keep informed before anyone else, give them talking points to advocate, involve them visibly so others see their support, never surprise them.
    
  • Blockers: engage directly, diagnose the specific cause of opposition, design an intervention tailored to that cause, monitor closely for escalation.
    
  • Supporters: find ways to amplify their voice, connect them to champions who can elevate their concerns, keep them motivated through visible progress.
  • Observers: monitor for changes in power or alignment, don’t invest disproportionate energy, but don’t ignore entirely.
• Step eight: Identify the critical path. Not all stakeholders matter equally. Ask: whose opposition alone could kill this initiative? That’s your critical stakeholder. They get the most attention, the most careful strategy, and the most direct engagement from the CEO personally. Also ask: is there a coalition risk, a scenario where two or three moderately powerful stakeholders align against the integration and create a blocking coalition that’s stronger than any individual? Coalitions are harder to see and harder to address because no single person looks dangerous enough to worry about.
• Step nine: Build a monitoring plan. Stakeholder positions change. Set up informal checkpoints: regular conversations, observation of behavior in meetings, feedback from trusted intermediaries. Watch for early warning signs: a champion going quiet, a blocker suddenly becoming cooperative (which might mean they’ve found a different way to undermine), a supporter becoming frustrated. The map is alive.
• Step ten: Communicate the map carefully. A stakeholder map is a sensitive document. It contains honest assessments of people’s motivations and power. It should be shared only with the CEO and perhaps one or two trusted leaders.