Introduction: Why People Matter in Projects
Welcome to the chapter on Managing Project Stakeholders! When we think of "projects," we often think of schedules, budgets, and technical tasks. But here is a secret: projects are actually about people. If the people involved aren't happy or don't understand what’s happening, even the most perfectly planned project can fail. In this chapter, we will learn how to identify who these people are and, more importantly, how to manage them so your project stays on track.
Think of it like planning a big wedding. You have the couple (the owners), the caterers (suppliers), the parents (high-influence backers), and the neighbors (who might complain about the noise). If you ignore the neighbors or forget to feed the parents, things will go wrong fast!
What is a Project Stakeholder?
A stakeholder is any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.
In the E2 curriculum, we generally group them into three categories:
1. Internal Stakeholders: People inside the business (e.g., the project team, managers, employees).
2. Connected Stakeholders: People with a direct contractual or commercial link (e.g., customers, suppliers, shareholders, lenders).
3. External Stakeholders: People outside the project who are still impacted (e.g., the government, local community, environmental groups).
Quick Review: The Project Sponsor
Don't forget the Project Sponsor! This is a crucial stakeholder. They are usually a senior manager who "owns" the project, provides the funding, and ensures the project aligns with the business strategy. They are your project's "champion."
Summary: Stakeholders aren't just the people working on the project; they are anyone who has a "stake" in its success or failure.
Analyzing Stakeholders: Mendelow’s Matrix
Don't worry if this seems a bit theoretical at first—it’s actually the most practical tool you’ll learn! Not all stakeholders are equal. You can't spend 100% of your time talking to everyone. Mendelow’s Matrix helps us prioritize by looking at two things:
1. Power: How much ability do they have to stop or change the project?
2. Level of Interest: How much do they actually care about what we are doing?
We plot these on a 2x2 grid to decide our strategy:
1. Low Power, Low Interest (Minimal Effort)
These people don't have much influence and don't really care about the project.
Strategy: Minimal Effort. Don’t ignore them completely, but don’t waste your limited resources on them. Simple mass communications (like a general newsletter) are usually enough.
2. High Power, Low Interest (Keep Satisfied)
These are powerful people who aren't very interested in the day-to-day details. However, if they get annoyed, they can pull the plug on your project!
Strategy: Keep Satisfied. Keep them happy, give them what they need, but don't bore them with tiny details.
Example: A large institutional shareholder or a high-level government regulator.
3. Low Power, High Interest (Keep Informed)
These people care deeply about the project but can't really control it. They can, however, become powerful if they join forces with others (like a protest group).
Strategy: Keep Informed. Talk to them often. Show them you are listening to their concerns. This stops them from becoming "blockers."
Example: Local residents living near a new construction site.
4. High Power, High Interest (Key Players)
These are your most important stakeholders. They care a lot and have the power to make things happen.
Strategy: Key Players / Manage Closely. You should involve them in decision-making and communicate with them constantly.
Example: The Project Sponsor or a major customer for whom the project is being built.
Memory Aid: "MSIK"
To remember the strategies moving from Low/Low to High/High, think: Minimal, Satisfied, Informed, Key players. "Many Students Interpret Knowledge."
Key Takeaway: Use Mendelow’s Matrix to focus your energy where it matters most. Spend the most time on Key Players and the least on Minimal Effort groups.
Managing Stakeholder Expectations and Conflict
Managing stakeholders isn't just about sending emails; it’s about managing expectations. Different stakeholders often want different things, which leads to conflict.
Common Sources of Conflict:
• Resources: Two managers both wanting the same expert for their project.
• Priorities: The Finance Director wants to save money; the Marketing Director wants the best-looking product.
• Schedules: The client wants it "now," but the team says it will take "six months."
Steps to Manage Stakeholders Effectively:
1. Identify: Figure out who they are.
2. Analyze: Use Mendelow’s Matrix to see how much power/interest they have.
3. Plan: Decide how you will talk to them (meetings, reports, emails).
4. Engage: Execute your communication plan and listen to their feedback.
Did you know?
Stakeholders can move between quadrants! A "Low Power" group of employees can become "High Power" if they form a union or go on strike. You must review your stakeholder map regularly throughout the project lifecycle.
Quick Review: Conflict is natural in projects. The goal isn't to make everyone perfectly happy (which is impossible) but to manage their expectations so the project can reach its goals.
Common Pitfalls (Mistakes to Avoid)
When answering exam questions on this topic, watch out for these common errors:
• Thinking "Power" is the same as "Seniority": Sometimes a junior person has high power if they have a specialized skill the project cannot survive without.
• Forgetting External Stakeholders: Don't just look inside the company. Think about regulators, the media, and the community.
• Static Analysis: Thinking a stakeholder stays in the same box forever. Their interest or power levels change as the project moves from start to finish.
Summary Table
Final Encouragement: Managing stakeholders might feel like "soft skills," but it is one of the most tested areas in E2. Master Mendelow’s Matrix, and you'll be well on your way to success!