Decision Method
Stakeholder Analysis for Teams
Map stakeholders by power and interest to see who to manage, satisfy, inform, or monitor. The foundation of any communication plan.
Last updated: April 2026
What is Stakeholder Analysis?
Stakeholder analysis identifies every person or group affected by a decision and maps them by two dimensions: power (their ability to influence the outcome) and interest (how much they care about it). The result is a 2x2 grid that shows at a glance who deserves the most attention and what kind of communication they need.
The Power/Interest Grid (also called Mendelow's Matrix) places stakeholders in four quadrants, each with a clear engagement strategy. High-power/high-interest stakeholders need close management with frequent updates and early involvement. High-power/low-interest stakeholders must be kept satisfied without overwhelming them. Low-power/high-interest stakeholders should be kept informed because they can become advocates or blockers. Low-power/low-interest stakeholders need monitoring only. Getting this wrong wastes effort on the wrong people and leaves the people who can block your project out of the loop.
The method is standard in project management frameworks (PMI, IPMA, GPM), change management, and product development. What makes it valuable is not the grid itself but the conversation it forces: who actually has power here, who will resist, who do we need on our side early, and are we spending communication effort where it matters most?
When to Use Stakeholder Analysis
- At project kickoffs to map everyone who could influence or be affected by the project before commitments are made
- Before major decisions to understand who needs to be consulted, who just needs to be informed, and who you can safely skip
- During change management to identify sources of resistance before they become roadblocks and build targeted buy-in
- When planning communication strategies so you stop over-communicating to people who don't care and under-communicating to people who could block you
- When a project stalls and you suspect stakeholder misalignment is the root cause rather than a technical or resource issue
- Before presenting to leadership to anticipate questions, concerns, and political dynamics from different power positions
Step-by-step guide
- 1
Brainstorm stakeholders
List everyone who could be affected by or influence the decision. Go beyond the obvious team members: include leadership, end users, IT, compliance, works council, vendors, customers, and regulators. Ask your team "Who else might care about this?" and "Who could block this if they wanted to?" The stakeholders you forget are usually the ones who cause the biggest problems later, because nobody managed their expectations.
- 2
Rate power (1-5)
For each stakeholder, rate how much power they have to influence the outcome. Power comes from multiple sources: formal authority (a VP who can veto), resource control (budget holders), expertise (the only person who understands the legacy system), or political influence (someone the CEO trusts). A junior employee with the CEO's ear can have more real power than a director who is outside the decision chain.
- 3
Rate interest (1-5)
Rate how much each stakeholder cares about this specific decision. A C-level executive might have enormous power over your project but very low interest because they have 50 other priorities competing for their attention. End users might have almost no formal power but extremely high interest because the decision directly affects their daily work. Interest often changes as a project progresses, so initial ratings need regular updates.
- 4
Plan engagement per quadrant
This is where the analysis becomes actionable. For each quadrant, define the specific communication approach: Manage closely (high power, high interest): weekly 1:1s, early access to drafts, involve in key decisions, give them a voice before announcing to others. Keep satisfied (high power, low interest): quarterly summary with ROI metrics, escalate only when their input is needed, respect their time. Keep informed (low power, high interest): regular email updates, feedback channels, training plans, give them a way to be heard without slowing down decisions. Monitor (low power, low interest): include in general communications, no dedicated effort, but check quarterly whether their interest has changed.
- 5
Review at every milestone
Power dynamics shift as projects progress. A stakeholder who was low-interest in month one might become high-interest when the change reaches their department in month three. A vendor who had low power during evaluation suddenly has high power during implementation. Reassess at every major milestone, after organizational changes, and whenever someone who was quiet suddenly starts asking questions.
Pro tip: Include indirect stakeholders you might forget: regulators, works council, downstream teams, external partners, customers who will feel the impact. The stakeholders you don't map are the ones who derail the project three months in, because nobody managed their expectations.
Pro tip: Rate power and interest independently before discussing as a team. When you rate together, the first number spoken anchors everyone. Independent ratings followed by a discussion of differences produces more honest results.
Pro tip: The quadrant labels tell you what to do, not how to feel. "Monitor" does not mean "ignore." It means check in periodically, but don't invest weekly effort. Treating "Monitor" stakeholders as invisible is how projects get blindsided.
Pro tip: Use the stakeholder map as direct input for your RACI matrix. High-power/high-interest stakeholders should be Accountable or Consulted. Low-power/high-interest stakeholders are typically Informed. If someone in your RACI isn't on your stakeholder map, ask why they are in the project.
Example
A 60-person company rolling out a new CRM mapped 6 stakeholders. The Sales Director (power 4, interest 5) was initially not in planning meetings. The stakeholder map made it obvious this was a mistake: he needed weekly alignment, not post-decision notifications.
A 60-person company rolling out a new CRM mapped 6 stakeholders. The Sales Director (power 4, interest 5) was initially not in planning meetings. The stakeholder map made it obvious this was a mistake: he needed weekly alignment, not post-decision notifications.
Worked Example
A 60-person manufacturing company is replacing their legacy CRM with a modern cloud system. The project manager ran a stakeholder analysis at the kickoff to build the communication plan before any announcements were made.
| Stakeholder | Power | Interest | Quadrant | Engagement Plan |
|---|---|---|---|---|
| CEO | 5 | 2 | Keep satisfied | Quarterly executive summary with ROI metrics. Only escalate for budget changes. |
| Sales Director | 4 | 5 | Manage closely | Weekly alignment meeting. Early beta access. Input on workflow design. |
| IT Department | 3 | 4 | Keep informed | Bi-weekly technical updates. Input on integration requirements and data migration. |
| End Users (Sales Reps) | 1 | 5 | Keep informed | Training schedule announced 4 weeks before rollout. Dedicated feedback channel. |
| Works Council | 4 | 3 | Keep satisfied | Compliance briefing 6 weeks before rollout. Data privacy review documented. |
| External CRM Vendor | 2 | 3 | Monitor | Monthly status call. Escalation path defined in contract. |
The Sales Director (power 4, interest 5) was initially not included in the weekly planning meetings because the project was "owned by IT." The stakeholder map made it immediately obvious this was wrong. The Sales Director had both the power to kill the project (by refusing to mandate adoption in his team) and the interest to shape it (his team would use it daily). He was moved to weekly involvement before any design decisions were made. Three months later, when the old CRM vendor tried to offer a counter-deal through the CEO, the Sales Director was already committed to the new system and backed the project in the executive meeting.
Stakeholder Analysis vs RACI Matrix
| Dimension | Stakeholder Analysis | RACI Matrix |
|---|---|---|
| Focus | Project-level influence and communication | Task-level responsibility assignment |
| Question answered | "Who matters and how do we engage them?" | "Who does what for each task?" |
| Output | Communication plan per quadrant | Responsibility matrix per deliverable |
| When to use | Before project starts, to understand the full picture | After kickoff, to assign work |
| Updates | At milestones and when power dynamics shift | When tasks change or team composition shifts |
Do the stakeholder analysis first to understand who matters and what kind of engagement they need. Then build the RACI to assign task-level roles to the right people. The stakeholder map tells you who should be in the RACI. If you skip stakeholder analysis, your RACI will have the right tasks but the wrong people.
Common Mistakes
1 Only mapping people you already know
The most dangerous stakeholders are the ones you don't think about until they object. Ask your team: "Who could block this project if they decided to?" and "Who will be affected by this change even if they are not in our department?" The works council, a compliance officer, or an end user group you forgot to consult can halt a project faster than any technical issue.
2 Rating everyone as high-power to avoid difficult conversations
If every stakeholder is "high power, manage closely," you have no prioritization. The point of the grid is to differentiate. Some people genuinely have low power and low interest. Putting them in the right quadrant is not disrespectful. It is efficient. Your communication effort is finite. Spend it where it moves the needle.
3 Doing the analysis once and never updating it
Power dynamics shift. A vendor with low power during evaluation becomes high-power during implementation because you depend on them for data migration. A department head who was low-interest becomes high-interest when the change reaches their team. Re-run the analysis at every major milestone.
4 Treating stakeholder analysis as a document instead of a conversation
The value is not the grid. The value is the team discussion that produces the grid. When four people independently rate a stakeholder's power and get 2, 2, 4, 5, that disagreement is the most useful finding. It means someone knows something about that stakeholder's influence that others don't.
Try the free interactive tool
Use this method right now in your browser. No signup required, with PDF export.
Frequently asked questions
- RACI assigns task-level responsibilities (who does the work, who approves). Stakeholder analysis maps project-level influence (who can affect the outcome). Do the stakeholder analysis first, then build the RACI.
- A 2x2 grid (Mendelow's Matrix) with Power on the vertical axis and Interest on the horizontal. Each quadrant maps to a different engagement strategy.
- At every major milestone and whenever organizational changes happen. Power dynamics shift as projects progress.
- Ask: "Could this person block the project if they wanted to?" If yes, they have power regardless of title. Informal influence counts as much as org-chart authority.
- Even a 5-person project has stakeholders beyond the team: the budget owner, the department head, the end users, the customer. The analysis scales down easily. With fewer stakeholders, the exercise takes 15 minutes and still prevents the most common failure: forgetting someone who cares enough to block the project.
Related from the blog
Related methods
Force Field Analysis
Map driving vs. restraining forces, rate their strength, and see which side wins. Use before any change decision to understand what's pushing and what's blocking.
Scenario Analysis
Think through best case, worst case, and realistic outcomes before you commit. Reduces surprises and prepares your team for different results.