Introduction
Welcome to your next lesson in the "Diagnosing Readiness and Building the Coalition" module. In our previous session, we used the ADKAR model to perform a deep-dive diagnosis on two specific groups within the AlphaTech "Project Phoenix" scenario. We identified their primary barrier points to the change, moving from theory to a targeted diagnostic application.
Today, we'll zoom out from that deep dive to create a comprehensive map of the entire organizational landscape. The learning outcome for this lesson is to conduct a stakeholder analysis mapping influence, interest, and readiness for change.
A stakeholder analysis is your strategic chessboard. It helps you systematically identify everyone who has a stake in your transformation, understand their power and perspective, and plan how to engage them effectively. This process is fundamental to building the "guiding coalition" we discussed in the context of Kotter's model and is a crucial input for crafting tailored communication and engagement strategies.
What is Stakeholder Analysis?
At its core, stakeholder analysis is a systematic process to identify, assess, and prioritize the individuals or groups who are affected by or can affect your transformation. A successful analysis doesn't just list names; it provides insight into the political and social dynamics of the change.
There are three key dimensions we need to map for each stakeholder:
- Influence (or Power): Their ability to affect decisions, allocate resources, or block progress.
- Interest: The degree to which they are impacted by the change or care about its outcome.
- Readiness (or Stance): Their current attitude toward the change—are they a supporter, neutral, or a resistor?
Let's begin by introducing the most common tool for mapping the first two dimensions: the Power-Interest Grid.
Mapping Influence and Interest: The Power-Interest Grid
The Power-Interest Grid (also known as Mendelow's Matrix) is a simple yet powerful tool for categorizing stakeholders and determining the appropriate level of engagement for each.
To get a clear overview of how this works, please watch the following video.
Stakeholder Analysis: Power Interest Grid Explained with PMP Exam Tips
This video from PM Aspirant provides a clear and concise explanation of the Power-Interest Grid. It breaks down how to categorize stakeholders based on their power and interest, and outlines the corresponding engagement strategy for each of the four quadrants.
Watch the video from the beginning until 05:15. Focus on the definition of the four quadrants (e.g., High Power/High Interest) and the recommended engagement strategy for each ('Manage Closely', 'Keep Satisfied', etc.). Note the emphasis on this being a dynamic, ongoing process.
As the video explained, you can visualize your stakeholders in four key segments:

This grid gives you a clear, actionable plan for allocating your time and effort:
- High Power, High Interest (Manage Closely/Work Together): These are your key players. You need to fully engage them and make the greatest effort to satisfy them. In your context, this would likely include the project sponsor and key business unit leaders.
- High Power, Low Interest (Keep Satisfied): These stakeholders have power but aren't engaged in the day-to-day details. Keep them satisfied with concise, relevant information, but don't overwhelm them. A CFO or Head of a non-impacted department might fall here.
- Low Power, High Interest (Keep Informed/Show Consideration): This group is passionate and can be a great source of on-the-ground intelligence and support. They lack power but want to be involved. This is often where end-users or team members directly implementing the change reside.
- Low Power, Low Interest (Monitor/Minimal Effort): Put minimal effort into this group but don't ignore them entirely. Their level of interest or power might change as the transformation progresses.
Assessing Readiness for Change
Knowing a stakeholder's power and interest tells you how to engage them, but it doesn't tell you what that engagement should look like. For that, you need to assess their readiness, or their current stance toward the change. Are they an enthusiastic ally or a deeply entrenched opponent?
The UC Berkeley Change Management Toolkit offers a useful framework that categorizes stakeholders based on their levels of agreement with the change and trust in you and the leadership team.
[PDF] Change Management Toolkit - UC Berkeley
This toolkit provides a nuanced way to look at readiness beyond a simple 'for' or 'against' dichotomy. It introduces five stakeholder types and suggests specific goals for engaging with each.
Please read pages 11-14. Start at the 'Stakeholder Analysis and Engagement Plan' heading and read through to the end of the 'Strategy for engaging each Stakeholder Type' section. Focus on understanding the definitions of Allies, Opponents, Fellow Travelers, Neutrals, and Adversaries.
This model gives you a more sophisticated lens:
- Allies (High Agreement, High Trust): Your champions. The goal is to affirm their support and empower them.
- Opponents (Low Agreement, High Trust): They trust you but disagree with the change. The goal is to build agreement by respectfully engaging with their perspective.
- Fellow Travelers (High Agreement, Low Trust): They support the change but don't trust the leadership. The goal is to build trust by being transparent and reliable.
- Adversaries (Low Agreement, Low Trust): The most challenging group. The goal is to minimize their threat, not necessarily to convert them.
- Neutrals (Unknown): Your goal is to educate them and determine where they stand.
The ADKAR diagnosis you performed in the last lesson is a perfect input for this assessment. A lack of Desire is a strong indicator that a stakeholder may be an Opponent or even an Adversary.
Application Exercise: Creating a Stakeholder Map
Now it's time to apply these concepts. We'll continue with the "Project Phoenix" scenario from the previous lesson, but let's add a few more key players to create a more complete map.
Scenario Recap:
AlphaTech is migrating its monolithic "LoanSphere" product to a microservices architecture with a new AI module.
Stakeholders:
- CEO: The executive sponsor of Project Phoenix.
- Senior Engineers: The veterans who built the original monolith.
- Sales Team: Compensated based on selling the existing product.
- Head of Product: Responsible for the overall product strategy and roadmap.
- IT Infrastructure Team: Responsible for servers, databases, and uptime. They will need to support the new microservices architecture.
- "BigBank Inc." Lead Architect: The primary technical contact at AlphaTech's largest and most important customer.
Your Task:
Your goal is to create a stakeholder analysis map. A good template can make this process much more structured.
[Free] Stakeholder Analysis Template
The AIHR article on Stakeholder Analysis provides a downloadable Excel template that is ideal for this exercise. It includes columns for many of the dimensions we've discussed.
Follow the link in the article to download the free Excel template. We will use this as the basis for your analysis.
Using the downloaded template (or a simple table of your own), complete the following for each of the six stakeholders listed above:
- Categorize them on the Power-Interest Grid (e.g., High Power/High Interest).
- Assess their likely Stance/Readiness (e.g., Ally, Opponent, Neutral).
- Briefly justify your assessment based on their role and the scenario.
- Define the primary engagement strategy (e.g., Manage Closely, Keep Informed).
(Take about 15 minutes to complete this exercise.)
Click here for a sample analysis of two stakeholders after you've completed your own.
Sample Analysis:
-
Stakeholder: Head of Product
- Power/Interest: High Power, High Interest. Their role is central to the project's success and future direction.
- Stance/Readiness: Likely an Ally. The transformation directly supports their strategic goals of improving feature velocity and creating new product tiers.
- Justification: This person is responsible for the product's long-term viability, which Project Phoenix is designed to ensure. Their objectives are aligned with the project.
- Engagement Strategy: Manage Closely. Involve them in all key strategic decisions, partner with them to define the roadmap, and leverage them as a key communicator of the vision.
-
Stakeholder: IT Infrastructure Team
- Power/Interest: High Power, Low Interest. They have high power because if they can't or won't support the new architecture, the project fails. Their interest may be low initially, as they see it as "just another system to support."
- Stance/Readiness: Likely Neutral to Opponent. They may be concerned about the increased operational complexity of microservices, the need for new skills (like Kubernetes or container orchestration), and potential impacts on stability. They have high trust in the company but may disagree with the technical approach if not consulted.
- Justification: Their primary mandate is stability and uptime. A major architectural shift represents significant risk and work for them without an immediate, obvious benefit to their core metrics.
- Engagement Strategy: Keep Satisfied. Involve them early in technical planning to address their concerns. Clearly communicate the long-term operational benefits and provide the necessary training and resources. Ensure they don't feel "blindsided" by new requirements.
Conclusion
In this lesson, you've learned how to move from a narrow diagnosis to a broad, strategic map of your organizational environment. This stakeholder analysis is not a one-time activity but a living document that you should revisit throughout the transformation.
Key Takeaways:
- Stakeholder analysis is a three-dimensional process: It requires mapping influence, interest, and readiness.
- The Power-Interest Grid dictates your engagement level: It helps you prioritize your time and resources, telling you how often and how deeply to engage different groups.
- Assessing readiness determines your engagement strategy: Understanding if someone is an Ally, Opponent, or Neutral tells you what your communication needs to achieve—reinforcing agreement, building trust, or simply educating.
- These tools create a practical action plan: The combination of these models moves you from abstract ideas to a concrete plan for managing the human dynamics of your transformation.
Preview of the Next Lesson:
Our stakeholder analysis has given us a qualitative "feel" for the organization. But to make a strong business case and track progress, we often need more quantitative data. In the next lesson, we will build on this foundation by learning how to perform an organizational readiness assessment using a structured diagnostic tool. This will allow you to aggregate your findings, present a data-backed view of readiness to leadership, and identify systemic, organization-wide barriers to change.