I.5 — Align Stakeholder Expectations

I.5 · Last updated: 24/08/2026

Where this task sits

I.5 — Align Stakeholder Expectations is the fifth task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has four enablers:

• Categorize stakeholders
• Identify stakeholder expectations
• Facilitate discussions to align expectations
• Organize and act on mentoring opportunities

This task sits in the middle of the stakeholder trio: I.4 identifies and engages stakeholders, I.5 aligns expectations, and I.6 sustains the aligned expectations. All three are consecutive, and the order is deliberate.

🔴 Do not trust the number

This number changed hands entirely in 2026:

• In 2021, I.5 was ensuring team members and stakeholders are trained. That topic now sits inside I.3 — Lead the Project Team.
• In 2026, I.5 is aligning stakeholder expectations.

So an older question tagged "I.5" is most likely about training, not stakeholder expectations.

Domain I came down to eight tasks in 2026 (older numbers ran at least as far as I.12), and this task's neighbor is in the same position: in 2021, I.6 was building a team, and that went to I.3 as well.

Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

Why categorization is the first enabler

The ECO begins aligning expectations with categorizing. The reason is written in the book.

Stakeholder mapping and representation is a method of categorizing stakeholders using various methods. Categorizing stakeholders assists the team in building relationships with the identified project stakeholders (PMBOK® 8, Guide p.200).

Categorization, in other words, is not a filing exercise but the precondition for building relationships. Who gets how much of your time, and whose view is decisive on which decision, comes out of it.

The Guide lists the classification axes too: internal/external, impact/influence/power/interest, upward/downward/outward/sideward, or any other classification model chosen by the project manager (PMBOK® 8, Guide p.142).

The third axis is usually skipped: upward (sponsor and senior management), downward (the team), outward (vendors, customers, regulators), sideward (peer project managers). All four directions run on the same project.

The grid methods

The most common mapping methods are two-axis grids (PMBOK® 8, Guide p.200):

Power/interest grid, power/influence grid, or impact/influence grid. Each of these techniques supports grouping stakeholders according to their level of authority (power) and their level of concern about the project's outcomes (interest).

The practical value of the grids is that the four corners call for four different engagement strategies: high power–high interest wants close working, high power–low interest wants keeping satisfied, low power–high interest wants keeping informed, low power–low interest wants monitoring.

Translated for the exam: the option saying "send all stakeholders the same reports at the same frequency" is wrong. The point of categorizing is precisely to differentiate.

The salience model

A finer tool than the grids, and one the exam can ask for by name.

The salience model describes classes of stakeholders based on assessments of three things (PMBOK® 8, Guide p.201):

• Power — level of authority or ability to influence the outcomes of the project.
• Urgency — need for immediate attention, either time-constrained or relating to the stakeholders' high stakes in the outcome.
• Legitimacy — whether their involvement is appropriate.

The book notes an adaptation as well: one version substitutes proximity for legitimacy — the stakeholders' direct involvement in project activities, such as physical proximity (PMBOK® 8, Guide p.201).

Reading the three dimensions together pays off on the exam: a high-power demand without legitimacy and a legitimate but non-urgent request call for different responses.

Identifying expectations

The counterpart of the ECO's second enabler lives in the Plan Stakeholder Engagement process, whose tool list shows how expectations get surfaced (PMBOK® 8, Guide p.72):

data gathering such as benchmarking; data analysis such as assumption and constraint analysis and root cause analysis; decision-making such as prioritization/ranking.

Its inputs include the assumption log, change log, issue log, project schedule, risk register, and stakeholder register (PMBOK® 8, Guide p.72).

Root cause analysis appearing in this process is worth noting: the expectation a stakeholder voices is often a symptom of the underlying need. The same logic applies to a misunderstood vision — see I.1 — Develop a Common Vision.

Facilitating alignment discussions

The verb in the ECO's third enabler matters: facilitate. Not decide, and not arbitrate.

The tool list of Manage Stakeholder Engagement supports that role: communication skills such as feedback; interpersonal and team skills such as conflict management, cultural awareness, negotiation, and observation/conversation (PMBOK® 8, Guide p.74).

The techniques for when expectations collide are in the book too: for the five resolution techniques and the escalation order, see I.2 — Manage Conflicts.

What alignment aims at is described in the neighboring ECO task: optimizing alignment among stakeholder needs, expectations, and project objectives. Aligning is not about bringing stakeholders closer to each other but closer to the project's purpose.

Why mentoring sits in this task

The fourth enabler looks at first as if it belongs elsewhere: organize and act on mentoring opportunities.

The book treats mentoring as a form of stakeholder and team interaction. Among interpersonal skills it names coaching, mentoring, and negotiating together (PMBOK® 8, Guide p.170). On the team development side it recommends addressing gaps in knowledge and skills through training, mentoring, or coaching (PMBOK® 8, Guide p.84).

In the context of expectation alignment the meaning is this: when a stakeholder's expectation is unrealistic, the cause is usually a knowledge gap. Mentoring is a way of aligning the expectation by closing that gap — through transferring competence rather than through argument.

The organizational form of the same knowledge flow is a task of its own — see I.7 — Help Ensure Knowledge Transfer.

About the citations

All page numbers above refer to A Guide to the Project Management Body of Knowledge, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

Every citation on this page is from the second book, the Guide. The numbers are the book's printed page numbers.

This page explains the book; it does not replace it.