← ECO 2026 tasks

I.6 — Manage Stakeholder Expectations

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

A stakeholder task written in the language of customers

I.6 — Manage Stakeholder Expectations is the sixth task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. It has only three enablers, and the same phrase recurs in all of them:

Although the task's title says "stakeholder", every enabler deliberately uses the word "customer", and it means the customer inside the organization as well as the one outside it. What the task measures is whether the project's outcomes match what those customers expect.

The old I.6 was about building a team

This number moved to a different subject in 2026. In 2021, I.6 meant building a team, and that topic now sits inside I.3 — Lead the Project Team. In 2026, I.6 is managing stakeholder expectations. An old question tagged "I.6" is therefore most likely about team building. The same thing happened next door, where training, I.5 in 2021, also moved into I.3.

Domain I came down to eight tasks while the old numbers ran to at least I.12. When you map older material, the title is what counts and the number is not; the detailed breakdown is in what changed in the 2026 PMP exam.

Aligning happens once, managing goes on

Within the ECO's stakeholder trio, the boundary people confuse most often is the one between I.5 and this task, because both have "expectations" in their names. The difference is hidden in the verbs.

I.5 aligns expectations. At that stage they are still far from one another and from the project, and the work is to draw them together through discussion. I.6 manages them. Alignment has already been reached, and the work now is to keep outcomes in line with it and to respond when a drift appears. The ECO's wording in the second enabler, "align and maintain", carries the whole difference by itself. Aligning is something that happens at one point, whereas keeping things aligned is a condition that has to be sustained.

So when an exam scenario shows expectations and outcomes pulling apart, first work out which stage you are in. If the expectation was never discussed, the question is testing I.5; if it was discussed and has since drifted, it is testing I.6.

Who the internal and external customers are

The Guide's examples of stakeholders make 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 sits inside the organization, such as the sponsor, the project management office, the steering committee, and the team. Another part sits outside it, such as customers, end users, regulators, and communities. The ECO's phrase "internal and external customer" covers both groups.

The book also notes a situation that complicates the idea of a customer. Many projects originate from a customer's procurement process, and in those projects the performing organization serves as a vendor to a sponsor organization (PMBOK® 8, Guide p.123). On such a project the team's "customer" is another organization altogether, so the answer to the question of who the customer is changes from one project to the next.

Five levels of engagement

The most concrete tool in this task is a scale with a direct counterpart on the exam. The Guide classifies stakeholders' level of engagement in five steps (PMBOK® 8, Guide p.200):

The ladder runs in one direction, from unaware to leading. Even so, not every stakeholder needs to be brought to the top step, and the next section explains why.

The gap between where a stakeholder is and where they need to be

The book's most practical tool for this task is the stakeholder engagement assessment matrix. For each stakeholder the matrix carries two marks. C shows the current level of engagement, and D shows the level the project team has judged essential for the project's success, that is, the desired level. For each stakeholder, the gap between the two directs the level of communication needed to engage that stakeholder effectively. According to the book, closing this gap is an essential element of monitoring stakeholder engagement (PMBOK® 8, Guide p.200).

Three conclusions follow from that definition, and all three are useful on the exam. The desired level varies from one stakeholder to another, so for some it is enough to stay neutral and nobody expects everyone to lead. The amount of communication is set by the size of the gap, which makes it far from an arbitrary choice. And what gets monitored is a measurable gap, which is much firmer ground than a vague sense of satisfaction.

The enabler about monitoring and responding as needed describes exactly this loop. Measure the gap, step up communication if necessary, and measure again.

Monitoring engagement as a process

The tools of the Monitor Stakeholder Engagement process are built to run that loop (PMBOK® 8, Guide p.76). For data analysis it names alternative analysis, root cause analysis, and stakeholder analysis. For data representation it names the stakeholder engagement assessment matrix, and for decision-making multicriteria decision analysis and voting. Communication skills include feedback and presentations, and interpersonal skills include active listening, cultural awareness, leadership, networking, and political awareness.

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

Seeing change requests among the outputs tells you something important, which is that a drift in a stakeholder's expectations can go as far as a formal change request. For the details of that process, see III.3 — Manage and Control Changes.

Satisfaction is one of the places where value is measured

The third enabler uses the word "satisfaction" outright, and that choice fits the book's understanding of value. According to The Standard, value can be described and assessed with measurable metrics such as return on investment, as well as with qualitative observations such as testimonials and societal benefits. Value represents the overall worth of the project's outcomes and the net benefit delivered to stakeholders, particularly from the perspective of key stakeholders (PMBOK® 8, Standard p.40).

From this angle customer satisfaction is no secondary or "soft" indicator. It is one of the places where value gets measured. The same dimension shows up on the quality side, too. The Standard lists satisfaction among the dimensions of quality and asks whether deliverables and processes elicit valuable feedback from customers or end users, including usability and user experience (PMBOK® 8, Standard p.44).

The value side is covered in detail on II.3 — Help Ensure Value-Based Delivery, and the quality side on II.7 — Plan and Optimize Quality of Products/Deliverables.

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:

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 describes the book; it does not replace it.

iyzico ile Öde, Visa, MasterCard