Engage Stakeholders

Introduction

This lesson covers Task 1.4 of the People domain of the July 2026 PMP Examination Content Outline (ECO), a domain that carries 33% of the scored questions. A project succeeds or fails in the perception and decisions of the people it affects: the sponsor who funds it, the users who adopt its result, the regulators who approve it, the suppliers who deliver parts of it and the people who simply live with its consequences. Engagement is the continuous work of identifying these people, understanding what they need and expect, tailoring communication to them and building the trust that makes cooperation possible. The exam typically presents a stakeholder who is resistant, silent, overlooked or newly appeared, and asks for the best next step.

After this lesson you will be able to identify stakeholders systematically, analyse them with the common models, tailor your communication, execute and adjust the stakeholder engagement plan, align needs, expectations and objectives, and build trust and influence.

Learning objectives

• Identify all stakeholders, including those who are hard to see, and keep the list current.
• Analyse stakeholders using power/interest, power/influence, impact/influence and salience models.
• Assess current versus desired engagement with an engagement assessment matrix.
• Tailor the content, channel, frequency and tone of communication to each stakeholder group.
• Execute the stakeholder engagement plan and adjust it when circumstances change.
• Align needs, expectations and project objectives, and escalate conflicts between them correctly.
• Build trust and influence ethically.

1. Identify stakeholders

A stakeholder is an individual, group or organisation that may affect, be affected by, or perceive itself to be affected by a decision, activity or outcome of the project. Identification starts at initiation but never ends: new stakeholders appear when scope, the organisation or regulations change.

Useful sources and techniques:

Categories to check: internal (sponsor, steering committee, team, functional managers, PMO), external (customers, end users, suppliers, regulators, partners, community, media) and groups that are easily missed (support and operations staff, security, legal, finance, training, unions or employee representatives, people who will lose responsibilities because of the project).

Example: the forgotten stakeholder

A hospital implements a new patient-records system. The register lists clinicians, IT, the finance office and the vendor. In month four, the night-shift nurses discover that the new login procedure takes four minutes on shared terminals, and refuse to use it. Nobody had interviewed night staff or the infection-control team that sets terminal rules. The stakeholder register is updated, a nurse representative joins the design reviews, and a faster badge-based login is added to the backlog. The lesson: identification must include people who operate the result in the real conditions, not only those who ordered it.

2. Analyse stakeholders

After the list comes analysis: how much power does each stakeholder have, how interested are they, what do they expect, and what is their attitude to the project? Several models serve different questions.

The power/interest grid gives four strategies:

• High power, high interest - manage closely. Sponsor, key customer. Regular two-way dialogue, involve in decisions.
• High power, low interest - keep satisfied. A regulator or a finance director. Give brief, relevant information at key points, and avoid surprises.
• Low power, high interest - keep informed. End users. Frequent updates, demos, feedback channels.
• Low power, low interest - monitor. Minimal effort, watch for change.

The salience model classifies a stakeholder by the combination of power, urgency and legitimacy: with all three present, the stakeholder is "definitive" and demands immediate attention; with two, the stakeholder is "dominant", "dangerous" or "dependent"; with one, "dormant", "discretionary" or "demanding".

Beyond position, record attitude and expectations. The stakeholder register typically holds: identity and role, requirements and expectations, influence, classification (internal/external, supporter/neutral/resistor), and engagement strategy. Because it contains opinions about people, it should be shared with care, according to the organisation's policy and privacy rules.

The stakeholder engagement assessment matrix

This tool compares the current level of engagement with the desired level, using the scale: unaware, resistant, neutral, supportive, leading.

(C = current, D = desired.) Every cell in which C and D differ represents a gap that needs an action: a conversation, a briefing, a demonstration, an involvement in a decision.

3. Tailor communication to stakeholder needs

Once a stakeholder is understood, adapt communication along five dimensions:

1. Content: what they need to know to decide or act. A sponsor needs outcomes, risks, money and decisions; a user needs how the change affects daily work; an engineer needs interfaces and constraints.
2. Level of detail and language: avoid jargon. Translate technical or project terms into the stakeholder's vocabulary.
3. Channel: face-to-face, video call, dashboard, newsletter, workshop, demo, short email. Choose according to the importance and complexity of the message and the person's preference.
4. Frequency and timing: weekly for the steering group, per iteration for users, at milestones for the regulator.
5. Tone and culture: direct or indirect, formal or informal, hierarchical or flat. Respect time zones, languages and accessibility needs.

Communication is two-way. Asking, listening and confirming understanding ("Let me check I understood...") matter as much as presenting.

Worked example: tailoring communication

Scenario. You manage a project to replace a retail chain's point-of-sale software in 120 stores. Stakeholders include the CFO (sponsor), 120 store managers, the IT security officer, the payment-card auditor, and the cashiers' union representative. After six weeks, the store managers say they feel ignored and that rumours suggest staff reductions. The CFO complains that the weekly 20-slide status deck is too long. The auditor has not been contacted since the kick-off.

Step 1 - Classify. CFO: high power, high interest. Store managers: moderate power, high interest, currently negative. Auditor: high power, low current interest, but an approval is required before go-live. Union representative: moderate power, moderate interest, potentially sensitive.

Step 2 - Define the gaps. Store managers: current resistant, desired supportive. Auditor: current unaware, desired supportive. CFO: current supportive but frustrated by format.

Step 3 - Adapt.

• CFO: one-page dashboard with budget, schedule, top three risks and decisions needed; 30-minute meeting every two weeks.
• Store managers: bi-weekly 30-minute online Q&A, a short newsletter, a feedback form, and a pilot-store ambassador group. State clearly what the project does and does not change, and refer questions on staffing to HR, with whom you have agreed a joint message.
• Auditor: a briefing on the architecture and the evidence plan, and a quarterly checkpoint to agree what will be tested before go-live.
• Union representative: an early briefing with the HR lead on training plans and schedule effects.

Step 4 - Check. After one month, repeat a short pulse survey of the store managers and update the assessment matrix.

Why not other choices? Sending an additional detailed report to all would increase the noise. Waiting for the auditor to ask would turn an easy approval into a late surprise. Denying the rumours without evidence would reduce trust. Tailoring addresses the specific gap for each group.

4. Execute the stakeholder engagement plan

The stakeholder engagement plan describes the desired engagement, the strategies and the actions to move each stakeholder from current to desired. It is part of the project management plan and works together with the communications plan. Executing it means:

• Doing the actions on schedule: meetings, demonstrations, workshops, one-to-one conversations.
• Monitoring signals: attendance, response time, tone of messages, escalations, survey results.
• Adjusting when engagement changes: a sponsor who changes job, a new regulation, a competitor's announcement or an incident.
• Keeping the register and the plan up to date, and recording agreements and decisions.
• Involving stakeholders in activities that suit their role, such as reviews, pilots, acceptance tests and demos, in order to turn passive supporters into active ones.

In adaptive projects engagement is built into the cadence: the product owner represents customers, sprint reviews gather feedback, and the backlog reflects stakeholder input. In predictive projects, formal reviews at phase gates and change control play the same role. In either case, the plan is not a one-time document but a living tool.

5. Align needs, expectations and objectives

Stakeholders' needs (what they must achieve), expectations (what they think will happen) and the project objectives (what has been approved) often differ. The project manager's job is to detect and close these gaps early:

1. Elicit needs and expectations in interviews, workshops and observation, and write them down.
2. Compare them with the objectives, scope, budget, time and constraints.
3. Resolve the gaps by clarifying, negotiating, prioritising or adjusting expectations. If a stakeholder wants something that is outside the approved scope, route it through change control rather than agreeing informally.
4. Confirm the agreement in writing and share it.
5. Revisit regularly, because expectations drift.

When stakeholders disagree with one another, bring them together, use objective criteria (business value, compliance, cost) and, if the disagreement remains, escalate according to the governance model. Do not resolve a conflict by favouring the most powerful person in silence; transparency matters.

Example: aligning conflicting needs

On a bank's mobile app project, marketing wants a one-tap sign-in with no extra steps, while security requires a second authentication factor for payments above 100 euros. The project manager brings both to a workshop with a customer representative and a compliance officer. They agree on risk-based authentication: one tap for balance viewing and small payments, a second factor above the threshold or on a new device. Both parties' underlying needs (fast experience, regulatory safety) are met; the compromise is documented and traced to a requirement.

6. Build trust and influence

Stakeholders cooperate when they trust the project manager. Trust is built from:

• Competence: delivering what is promised, and knowing the subject.
• Reliability: keeping commitments, communicating early when a promise will be missed.
• Openness: sharing information, bad news included, without waiting to be asked.
• Respect: listening, acknowledging concerns and treating people consistently.
• Integrity: following the PMI Code of Ethics (responsibility, respect, fairness, honesty).

Influence without formal authority relies on relationships, credibility and clear arguments tied to the other person's goals. Ethical influence means persuading with facts and shared interests, and never manipulating, hiding information or making promises you cannot keep. Useful tactics: starting with a listening conversation, finding a shared goal, showing evidence, asking for small commitments first, and recognising contributions publicly.

7. Common pitfalls and exam tips

Pitfalls

• Building the register once, at initiation, and never updating it.
• Concentrating on the sponsor and ignoring users, operations or regulators.
• Using one communication style and one report for all groups.
• Treating a resistant stakeholder as an enemy rather than finding out what they need or fear.
• Changing the scope because a powerful stakeholder asked informally.
• Sharing sensitive classifications of people in an open document.
• Communicating only by one-way email.

Exam tips

• When a new stakeholder appears, the first step is usually to analyse them (interests, influence, expectations) and update the register and plan, not to start telling them everything.
• When a stakeholder is resistant, the best answer usually starts with understanding their concerns through direct conversation.
• When the problem is a stakeholder who does not read reports, change the channel or format to fit them.
• When a question gives the current and desired engagement, look for the answer that closes the gap with a specific action.
• "Manage closely" applies to high power and high interest; do not spend the same effort on everyone.
• Requests outside scope go through change control, whoever asks.

8. Mini case study

Situation. You are the project manager of a smart-meter rollout for a regional energy provider. The project replaces 400,000 meters across 18 months. Stakeholders include the provider's executive committee (sponsor), the energy regulator, installation contractors, local municipalities, customer-service staff and customers. At month five, the regulator's representative states in a meeting that she was not aware of the data privacy design and wants a review before further rollouts. Municipalities are complaining about road work noise. A customer group posts that the meters could raise bills. Your register contains only the executive committee, contractors and the regulator's name, with no engagement plan.

Question. What should you do?

Model solution.

1. Recognise the gap. The register is incomplete and the engagement is reactive. Stop and rebuild the picture before replying to each complaint.
2. Identify and analyse. Hold a workshop with the team, customer service and the sponsor to list all groups (including call-centre staff, installers' subcontractors, the data protection officer, consumer associations, the media). Classify with power/interest: regulator and executive committee (manage closely), municipalities and consumer groups (high interest, growing power - keep informed and consult), customers (keep informed).
3. Handle the urgent issue. Meet the regulator and the data protection officer within the week, present the privacy design, record the requested changes, and agree on a review checkpoint. If the review affects the schedule or the scope, process it through change control and inform the sponsor immediately.
4. Create the engagement plan. Assessment matrix with current and desired levels; for municipalities, a notice schedule and a contact person; for customers, a clear message about billing and an FAQ prepared with customer service; for the regulator, quarterly briefings.
5. Execute and monitor. Track complaints and survey results, update the plan monthly.
6. Build trust. Communicate the changes honestly, including the delay, and show how feedback influenced the plan.

Why this is best. It deals with the immediate risk (regulator approval) while fixing the cause (incomplete identification and no plan). Answering each complaint separately, or defending the design without listening, would leave the root problem and might damage trust.

Key terms

• Stakeholder: any person, group or organisation affected by or able to affect the project.
• Stakeholder register: the record of stakeholders and their analysis.
• Power/interest grid: a model to classify stakeholders by authority and concern.
• Salience model: classification by power, urgency and legitimacy.
• Engagement assessment matrix: comparison of current and desired engagement levels.
• Stakeholder engagement plan: strategies and actions to reach the desired engagement.
• Communication channel: the means by which a message is delivered.
• Trust: confidence in the competence, reliability and integrity of a person.
• Influence: the capacity to affect decisions without formal authority.

Summary checklist

• I identify stakeholders from multiple sources and keep the register current.
• I analyse stakeholders with power/interest and other models and record attitude and expectations.
• I use the engagement assessment matrix to find the gaps between current and desired engagement.
• I tailor content, channel, frequency and tone for each group.
• I execute and adjust the engagement plan and involve stakeholders in suitable activities.
• I align needs, expectations and objectives, and send out-of-scope requests to change control.
• I build trust and influence in line with the PMI Code of Ethics.

Official sources

• PMI, PMP Examination Content Outline (July 2026): https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, the new PMP exam: https://www.pmi.org/certifications/project-management-pmp/new-exam (opens in a new tab)
• PMI, Code of Ethics and Professional Conduct: https://www.pmi.org/about/ethics/code (opens in a new tab)