Project Management Leadership with AI · Stakeholder and team leadership · lesson 15 of 21 · 14 min

Stakeholder engagement

Stakeholders decide whether projects succeed

A stakeholder is anyone who affects or is affected by the project: sponsors, users, customers, suppliers, regulators, unions, communities and internal functions such as IT security, legal and finance. Projects often fail not because of technical problems but because important stakeholders were ignored, surprised or unconvinced.

Step 1: identify

Brainstorm broadly, then refine. Ask: who funds it, who uses it, who approves it, who could block it, who loses something, who must change behaviour, who supplies inputs?

Step 2: analyse

The power–interest grid is a common starting point:

| | Low interest | High interest | |---|---|---| | High power | Keep satisfied | Manage closely | | Low power | Monitor | Keep informed |

Go deeper for key stakeholders:

Stakeholder: Head of Compliance
Power: High (can block go-live)   Interest: Medium (focused on regulatory risk)
Current attitude: Neutral / cautious     Desired: Supportive
What they care about: Audit trail, data residency, regulator expectations
Concerns: New vendor processes customer data abroad
Engagement: Early design review; monthly briefing; involve in vendor due diligence
Owner: PM + product owner

Step 3: plan engagement

Compare current and desired engagement levels (e.g., unaware, resistant, neutral, supportive, leading) and plan actions to close the gaps. Tailor messages: executives want outcomes and risks; users want to know what changes for them and how they will be supported; regulators want evidence of compliance.

Step 4: engage and monitor

Meet key stakeholders early, before decisions are fixed.
Listen first; understand interests behind positions.
Show how their input changed the plan.
Track sentiment and adjust.

Managing resistance

Resistance is information. People resist because they fear loss (status, control, job security, competence), do not understand the reason, or were not consulted. Responses:

Explain the why, with evidence.
Involve resisters in solution design.
Address concerns concretely (training, transition support).
Find respected champions within the affected group.
Escalate only when genuine blocking behaviour persists.

Influence without authority

PMs often lead people who do not report to them. Useful levers:

Reciprocity: help others with their goals.
Credibility: keep commitments, be well-prepared, admit mistakes.
Shared goals: connect the project to what they already care about.
Coalitions: gain support from respected peers.
Data: make the case with evidence, not opinion.

Worked example

Illustrative. A fictional hospital group in Lahore introduced electronic health records. Doctors, a high-power group, were resistant: they feared slower consultations. The PM invited senior doctors to co-design screens, ran pilot clinics with extra support, and shared consultation-time data from pilots openly. When data showed a temporary slowdown in the first weeks followed by recovery, doctors themselves proposed a phased rollout with protected learning time. Resistance became ownership.

Cultural and regional sensitivity

Stakeholder engagement styles vary. In some cultures and organisations, decisions are made through senior consensus before formal meetings; in others, open debate in meetings is expected. Hierarchy, relationship-building, language and religious observances (e.g., meeting times during Ramadan) matter. Ask local colleagues how decisions are really made.

Common mistakes

Identifying stakeholders once and never revisiting.
Treating communication (broadcasting) as engagement (dialogue).
Ignoring low-power stakeholders who later become powerful (e.g., via social media or regulators).
Engaging only supporters.

Quick self-check

Which stakeholder could stop your project next month, and when did you last talk with them directly? If the answer is "not recently", schedule that conversation this week.

Tracking engagement over time

Stakeholder positions change as projects progress. Review your stakeholder map at least monthly, and after major events such as a leadership change, reorganisation or public announcement. Track a simple indicator for key stakeholders (current vs desired engagement) and note the last meaningful interaction. A stakeholder who was supportive at initiation may become resistant when the change becomes real for their team.

Engaging with senior executives

Senior executives have limited time. Prepare short, decision-focused briefings; lead with the headline; bring options rather than problems; and follow up in writing with what was agreed. Respect their communication preferences, which vary across organisations and cultures.

Quick check before key meetings

Before any important stakeholder meeting, write down three things: what you want them to know, what you want them to feel, and what you want them to do afterwards. This simple preparation keeps conversations focused and makes follow-up easier.

Hands-on: a stakeholder register with engagement tracking (Excel)

Columns: A Stakeholder/group | B Power (1–5) | C Interest (1–5) | D Current (1–5) | E Desired (1–5)
F Quadrant      =IFS(AND(B2>=3,C2>=3),"Manage closely",B2>=3,"Keep satisfied",C2>=3,"Keep informed",TRUE,"Monitor")
G Gap           =E2-D2
H Priority      =G2*B2                 (sort descending: largest gap × power first)
I Cares about | J Concerns | K Next action | L Owner | M Due
N..S Monthly attitude scores; T Trend sparkline; U Drift flag =IF(S2<Q2,"DRIFTING: talk this week","")
Attitude scale: 1 resistant, 2 cautious, 3 neutral, 4 supportive, 5 leading

Template: pre-meeting check

Meeting: ____  Key attendees: ____
For each: current stance | what they need from this meeting | likely concern | what I want them to think, feel, do
My one ask: ____

Prompt template: anticipating concerns (approved AI tool)

For the change described below, list the likely concerns of each stakeholder group (finance, line managers,
front-line staff, IT security, customers) and one engagement action that would address each concern.
Mark these as hypotheses to test in conversation, not facts. Keep it to 5 bullets per group.

Validate every hypothesis by talking to real stakeholders.

How to measure success

Key stakeholders' attitude gap closing over time.
Adoption and usage measures after go-live meeting targets.
Concerns raised early (in design) rather than late (at go-live).

Video lecture: Stakeholder engagement

Lecture coming soon · 10 chapters · about 9 minutes. Read the full transcript below.

Stakeholders decide whether projects succeed
Why it matters
The concept: identify and analyse
Plan, engage and monitor
Worked example one: a quick stakeholder map
Worked example two: electronic health records in Lahore
Watch me do it: a stakeholder register with engagement tracking
Resistance and influence without authority
Common mistakes
Recap and try this now

Lecture transcript

Stakeholders decide whether projects succeed

A hospital group in Lahore, fictional but very realistic, introduced electronic health records. Technically, the system was sound. But the doctors, the most powerful group in any hospital, were resistant. They feared the new screens would slow down consultations, and they had the influence to stop the rollout. What turned resistance into ownership wasn't a better system. It was better engagement. In this lecture you'll learn a four-step approach to stakeholder engagement: identify, analyse, plan and engage, then monitor. You'll learn how to analyse power and interest, how to understand what people actually care about, how to handle resistance, and how to influence without formal authority. By the end, you'll be able to build a stakeholder map and plan specific actions for the people whose support you need most.

Why it matters

Why does this matter? Because projects fail more often because of people than because of technology. Stakeholders control the resources you need, the approvals you depend on and, ultimately, whether the thing you deliver is adopted. A technically perfect system that users avoid delivers no benefits. And engagement isn't a launch event or a one-off communication plan. People's positions change as the project progresses, new stakeholders appear, and concerns that were quiet in planning become loud at go-live. The PMBOK Guide's eighth edition makes stakeholders one of its seven performance domains for good reason: it's where many projects are won or lost.

The concept: identify and analyse

Step one: identify everyone who is affected by the project or can affect it: sponsors, users, managers, regulators, suppliers, unions, customers, and people who'll lose something because of the change. Step two: analyse. A power-interest grid is a good start. High power and high interest: manage closely. High power, lower interest: keep satisfied. Lower power, high interest: keep informed. Lower power, lower interest: monitor. Then go deeper for the key stakeholders. What's their current attitude, and what attitude do we need? What do they care about? What are their concerns? For example, a head of compliance might be cautious now and needs to be supportive by go-live. She cares about the audit trail, data residency and regulator expectations, and her concern is a new vendor processing customer data abroad. Now you know what engagement should address.

Plan, engage and monitor

Step three: plan engagement for each key stakeholder. Not a generic newsletter, but specific actions. For the head of compliance: an early design review, a monthly briefing, and involvement in the vendor's due diligence. Each action has an owner and a date. Here's the key idea: involve, don't just inform. People support what they help create. Step four: engage and monitor. Track each key stakeholder's attitude over time, even informally, on a simple scale from resistant to leading. When someone shifts, positively or negatively, adjust. A sponsor who goes quiet, a manager who stops attending reviews, or a user group whose complaints increase are all signals worth acting on before they become problems.

Worked example one: a quick stakeholder map

Let's map a simple project: a new expense system for a firm of three hundred people. The finance director: high power, high interest, because she owns the policy and the budget. Manage closely: invite her to co-own the policy rules the system will enforce. Line managers: medium power, lower interest. They approve expenses but mostly want it not to take their time. Keep satisfied: show them a two-minute approval demo on a phone. Employees: low individual power, high interest, because it affects how quickly they get reimbursed. Keep informed: practical tips on photographing receipts, and a clear date for the switch. IT security: significant power over go-live. Early review of the vendor's controls. Four stakeholder groups, four targeted actions, and a much smoother rollout than a single all-staff email.

Worked example two: electronic health records in Lahore

Now the realistic example from the lesson. At the fictional Lahore hospital group, doctors feared that electronic health records would slow down their consultations. That fear was reasonable. So the project manager didn't try to persuade them it was wrong. She invited senior doctors to co-design the screens they'd use. She ran pilot clinics with extra support staff on hand. And she shared consultation-time data from the pilots openly, including the bad news. The data showed a temporary slowdown in the first weeks, followed by recovery. Seeing that, the doctors themselves proposed a phased rollout with protected learning time. Resistance became ownership. Notice the pattern: take the concern seriously, involve people in solving it, and be honest with data, even when it doesn't flatter the project.

Watch me do it: a stakeholder register with engagement tracking

Let me show you the register I keep. One row per key stakeholder or group. Power and interest from one to five. Current attitude and desired attitude, on a simple five-point scale: resistant, cautious, neutral, supportive, leading. A gap column, desired minus current, and I sort by it, because the biggest gaps with the highest power are where engagement effort should go. Then the next action, its owner and date. Finally, a small row of monthly attitude scores with a sparkline. It's subjective, of course, but it makes drift visible. Here, the operations director has slipped from supportive to neutral over two months. That's my cue for a one-to-one conversation this week, to find out what's changed before it turns into opposition.

Resistance and influence without authority

Treat resistance as information, not opposition. People usually resist because they fear losing something, such as status, control or skills, because they're uncertain what the change means for them, or because it adds to an already heavy workload. So listen first, involve people in shaping the solution, show evidence rather than assurances, and make the new way easier. Project managers rarely have formal authority over stakeholders, so influence matters. Build credibility by doing what you say. Understand what others need and help them get it, which creates reciprocity. Frame the project in terms of their goals, not yours. And build allies, respected people who can speak for the change. In some regional cultures, including across the Gulf and South Asia, relationships and respect for seniority shape how and when to raise concerns, so adapt your approach thoughtfully.

Common mistakes

The common mistakes. Mapping stakeholders once at the start and filing the analysis. Broadcasting messages rather than engaging in two-way conversation. Ignoring quiet or low-power groups, such as the service desk, who later become the people fielding every complaint at go-live. Treating concerns as obstacles to be overcome rather than information to be used. And relying on the sponsor's authority to force adoption, which gets compliance at best, never commitment. A quick check before any important meeting: who in the room has concerns, what do they need from this meeting, and what do I want them to think, feel and do afterwards?

Recap and try this now

Let's recap. Stakeholders decide whether projects succeed, through resources, approvals and adoption. Identify everyone affected or able to affect the project, analyse power and interest, and go deeper for key stakeholders: current and desired attitude, what they care about and what worries them. Plan specific engagement actions, involve rather than just inform, and monitor attitudes over time so you notice drift. Treat resistance as information, and influence through credibility, shared goals and allies. Your try-this-now: build a stakeholder map for a current initiative, identify two stakeholders whose engagement must change, and plan specific actions, with owners and dates, for each.

Key takeaways

Identify stakeholders broadly and analyse power, interest, attitude and concerns.
Plan engagement to move stakeholders from current to desired levels with tailored messages.
Treat resistance as information; involve, explain, support and use champions.
Influence without authority through reciprocity, credibility, shared goals, coalitions and data.

Try it

Build a stakeholder map for a current initiative, identify two stakeholders whose engagement must change, and plan specific actions for each.