I.6 — Manage Stakeholder Expectations

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

Where this task sits

I.6 — Manage Stakeholder Expectations is the sixth task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has only three enablers:

• Identify internal and external customer expectations
• Align and maintain outcomes to internal and external customer expectations
• Monitor internal and external customer satisfaction/expectations and respond as needed

The phrase repeating in all three is worth noting: internal and external customer. The ECO does not say "stakeholder" here; it says "customer" specifically — and it means both inside and outside the organization.

🔴 Do not trust the number

This number changed hands entirely in 2026:

• In 2021, I.6 was build a team. That topic now sits inside I.3 — Lead the Project Team.
• In 2026, I.6 is managing stakeholder expectations.

So an older question tagged "I.6" is most likely about team building. Its neighbor is in the same position: in 2021, I.5 was training, and that went to I.3 as well.

Domain I came down to eight tasks in 2026; older numbers ran at least as far as I.12. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

The difference between aligning and managing

The most-confused boundary in the ECO's stakeholder trio is between I.5 and this task. Both say "expectations."

The distinction is in the verbs:

• I.5 aligns — expectations are still apart from each other and from the project; the work is to bring them closer through discussion.
• I.6 manages — alignment has been achieved; the work is to keep outcomes aligned with it and to respond to drift.

The ECO's second enabler, "align and maintain," carries that difference. The first is an event; the second is an ongoing condition.

Translated for the exam: in a scenario where expectation and outcome have diverged, look first at which stage you are in. If the expectation was never discussed, it is I.5; if it was agreed and then drifted, it is I.6.

What "internal and external customer" means

The Guide's stakeholder list makes the distinction concrete: suppliers and vendors, customers, end users, regulatory bodies, local communities, family, sponsor, governing bodies, project management offices, steering committees, the project manager, the project management team, and the project team (PMBOK® 8, Guide p.68 — Figure 2-31).

Part of that list is inside the organization (sponsor, PMO, steering committee, team) and part outside (customers, end users, regulators, communities). The ECO's "internal and external customer" covers both.

The Guide also notes a special case: situations where the performing organization serves as a vendor to a sponsor organization (PMBOK® 8, Guide p.123). Who counts as "the customer" is not the same on every project.

The engagement level ladder

This task's most concrete tool, and a scale with a direct exam counterpart. The Guide classifies stakeholders' engagement level in five steps (PMBOK® 8, Guide p.200):

• Unaware — the stakeholder is unaware of the project and its potential impacts.
• Resistant — aware of the project and potential impacts but resistant to any changes that may occur as a result of the work or outcomes; unsupportive of the work or outcomes.
• Neutral — aware of the project but neither supportive nor unsupportive.
• Supportive — aware of the project and its potential impacts and supportive of the work and its outcomes.
• Leading — aware of the project and its potential impacts and actively engaged in ensuring that the project is a success.

The ladder runs one way, from unaware to leading. But the target is not "leading" for every stakeholder — that is the next section's subject.

The gap between current and desired

The book's most functional sentence on this task.

In the stakeholder engagement assessment matrix, C represents the current engagement level of each stakeholder and D indicates the level the project team has assessed as essential to ensure project success (desired). The gap between current and desired for each stakeholder will direct the level of communications necessary to effectively engage that stakeholder. Closing this gap is an essential element of monitoring stakeholder engagement (PMBOK® 8, Guide p.200).

It has three consequences, all useful on the exam:

1. The desired level varies by stakeholder — not everyone needs to be "leading"; for some, "neutral" is enough.
2. The amount of communication is not arbitrary but set by the size of the gap.
3. What monitoring tracks is not a feeling of satisfaction but a measured gap.

The ECO's "monitor and respond as needed" enabler describes exactly that loop.

The monitoring process and its tools

Among the tools of Monitor Stakeholder Engagement are, on the data representation side, the stakeholder engagement assessment matrix; on the decision-making side, multicriteria decision analysis and voting; in communication skills, feedback and presentations; and in interpersonal skills, active listening, cultural awareness, leadership, networking, and political awareness (PMBOK® 8, Guide p.76).

The process outputs are work performance information, change requests, and plan updates; the documents updated include the issue log, lessons learned register, risk register, and stakeholder register (PMBOK® 8, Guide p.76).

Change requests in that output list is worth noting: a shift in stakeholder expectations can turn into a formal change request — see III.3 — Manage and Control Changes.

Expectation management is a satisfaction measurement

The ECO's third enabler uses the word "satisfaction" outright, and that lines up with the book's understanding of value.

The Standard says value can be described and assessed using either measurable metrics or qualitative observations such as testimonials and societal benefits; value represents the overall worth of the project outcomes and the net benefits to stakeholders, particularly from the perspective of key stakeholders (PMBOK® 8, Standard p.40).

Customer satisfaction, then, is not a "soft" indicator but one of the places value is measured. The quality side carries the same dimension: satisfaction — do the deliverables and processes elicit valuable feedback from customers and end users, including usability and user experience (PMBOK® 8, Standard p.44).

For the value side in detail see II.3 — Help Ensure Value-Based Delivery, and for the quality side II.7 — Plan and Optimize Quality of Products/Deliverables.

About the citations

The page numbers above refer to the PMBOK® 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

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

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