I.5 — Align Stakeholder Expectations

I.5 · Last updated: 11/10/2026

The middle step of the stakeholder trio

I.5 — Align Stakeholder Expectations is the fifth task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. It sits in the middle of the three consecutive steps into which the ECO splits stakeholder work. I.4 identifies stakeholders and brings them in, I.5 aligns their expectations, and I.6 keeps those aligned expectations in place for the rest of the project. The order is deliberate, since you cannot align the expectations of a stakeholder you have not yet identified.

The ECO lists four enablers for this task:

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

The old I.5 was about training

This number changed hands completely in 2026. In 2021, I.5 was about ensuring that team members and stakeholders were trained, and that topic now sits inside I.3 — Lead the Project Team. In 2026, I.5 means aligning stakeholder expectations. An older question tagged "I.5" is therefore much more likely to be about training than about stakeholder expectations.

The neighboring number went the same way. As Domain I shrank to eight tasks (the old numbers ran to at least I.12), team building, which was I.6 in 2021, also moved into I.3. Go by the title when you map older material; the wider picture of the numbering trap is in what changed in the 2026 PMP exam.

Alignment begins with sorting

The ECO starts the work of alignment with categorizing, and the book explains why. Stakeholder mapping/representation is the name for sorting stakeholders into categories by various methods, and the Guide states what the sorting is for: categorizing stakeholders assists the team in building relationships with the identified stakeholders (PMBOK® 8, Guide p.200).

Seen this way, categorizing stops being a filing exercise and becomes the precondition for building relationships. How much time goes to which stakeholder, and whose opinion weighs most on which decision, both follow from this first step.

The Guide also lists the axes that can be used for the sorting: internal/external, impact/influence/power/interest, upward/downward/outward/sideward, or any other model the project manager chooses (PMBOK® 8, Guide p.142). The third axis looks at the direction of influence, and the book describes each direction with examples (PMBOK® 8, Guide p.201). Upward are the sponsor, the steering committee, and senior management of the performing or customer organization. Downward are the team and specialists who contribute knowledge or skills in a temporary capacity. Outward are suppliers, government departments, the public, end users, and regulators. Sideward are the project manager's peers, meaning other project managers or middle managers. Once you notice that a single project communicates in all four directions at once, it becomes clear why one uniform reporting plan cannot be enough.

Two-axis grids

The most widely used mapping methods are two-axis grids, namely the power/interest, power/influence, and impact/influence grids. According to the Guide, each of these techniques groups stakeholders by their level of authority (power), their level of concern about the project's outcomes (interest), and their ability to affect those outcomes (PMBOK® 8, Guide p.200).

In practice each corner of a grid is paired with its own engagement strategy. Stakeholders with high power and high interest are managed closely, those with high power and low interest are kept satisfied, those with low power and high interest are kept informed, and those low on both are monitored. This four-way scheme does not appear in the text of PMBOK 8 itself. It is a common practice that settled in from earlier editions, although it sums up the purpose of the grid well.

That purpose is simply to make it possible to treat stakeholders differently, which is the whole reason for categorizing them. An answer option that says to send every stakeholder the same report at the same frequency is wrong on the exam for exactly that reason.

The salience model: power, urgency, legitimacy

A more finely tuned tool than the grids, the salience model can be asked about by name. It describes classes of stakeholders through three assessments (PMBOK® 8, Guide p.201):

• Power. The level of authority, or the ability to influence the project's outcomes.
• Urgency. The need for immediate attention, either because time is constrained or because the stakeholder has high stakes in the outcome.
• Legitimacy. Whether the stakeholder's involvement is appropriate.

The book also records an adaptation of the model in which proximity takes the place of legitimacy. Proximity means the stakeholder's direct involvement in project activities, such as physical proximity to the worksite or a direct contribution to the deliverables. The Guide adds that the model is especially useful for large, complex stakeholder communities and for groups with complex networks of relationships, and that it helps determine the relative importance of the stakeholders identified (PMBOK® 8, Guide p.201).

Reading the three dimensions together pays off directly on the exam. A demand that carries a lot of power but no legitimacy does not deserve the same response as a request that is legitimate but not urgent.

Bringing expectations to the surface

The second enabler finds its counterpart in the Plan Stakeholder Engagement process, whose tool list shows how expectations are brought into the open (PMBOK® 8, Guide p.72). On the data gathering side it names benchmarking, on the data analysis side assumption and constraint analysis and root cause analysis, and on the decision-making side prioritization/ranking. Its inputs include the assumption log, change log, issue log, project schedule, risk register, and stakeholder register.

The presence of root cause analysis on that list is telling. An expectation a stakeholder voices is often just the visible face of the actual need, and an alignment reached without finding the real concern behind a requested feature tends to fall apart at the first change. For the same logic applied to the vision, see I.1 — Develop a Common Vision.

The project manager as facilitator

The verb in the third enabler was chosen with care: facilitate discussions. Nobody expects the project manager to decide for the parties or to referee between them. The job is to build the ground on which the parties can reach agreement among themselves.

The tool list of the Manage Stakeholder Engagement process supports that role. Among communication skills it names feedback, and among interpersonal and team skills conflict management, cultural awareness, negotiation, and observation/conversation (PMBOK® 8, Guide p.74). For the techniques to use when expectations collide, and for the order of escalation, see I.2 — Manage Conflicts.

The neighboring task in the ECO describes where alignment is headed: optimizing the fit among stakeholder needs, expectations, and project objectives. In that definition what gets aligned is less the stakeholders with one another than all of them with the purpose of the project.

Why mentoring is on the list

The fourth enabler, organizing and acting on mentoring opportunities, looks at first glance as if it belongs somewhere else. The book, however, treats mentoring as one of the ordinary tools for working with people. Its examples of interpersonal skills mention coaching, mentoring, and negotiating together (PMBOK® 8, Guide p.170), and on the team development side it recommends closing gaps in knowledge and skills through training, mentoring, or coaching (PMBOK® 8, Guide p.84).

The link with aligning expectations runs like this. When a stakeholder's expectation is unrealistic, the cause is often a gap in knowledge, and mentoring is one way to align the expectation by closing that gap. Passing on knowledge makes a lasting agreement more likely than trying to win the stakeholder over in an argument. The same flow of knowledge on an organizational scale is the subject of another task; see I.7 — Help Ensure Knowledge Transfer.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ 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

All citations on this page come from the second book, the Guide. The numbers are the book's printed page numbers.

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