The three stakeholder tasks almost nobody studies properly

Inside the People domain there are three tasks that run one after another and that, read quickly, look like the same thing said three times. Engage stakeholders, align stakeholder expectations and manage stakeholder expectations. They are not the same, and the exam charges you for the difference.

Where they sit, exactly

In the official PMP exam content outline of July 2026, the People domain weighs 33 per cent and holds seven tasks. The fourth, the fifth and the sixth are the stakeholder ones, consecutive and with nothing in between. That they sit together says they are family. That they are kept apart says they are not interchangeable.

A piece of context helps too. PMI’s official page for the new exam lists stakeholder engagement among what 2026 brought into project-based scenarios, alongside artificial intelligence and sustainability. This is not outline filler, it is one of the three things PMI says it put in on purpose.

Task 4, engage stakeholders

Its enablers start with identifying stakeholders and analysing them, move on to tailoring communication to what each one needs and to executing the stakeholder engagement plan, and finish with optimizing alignment among stakeholder needs, expectations and project objectives, and with building trust in order to influence them.

Look at the whole arc. It starts in a register and it ends in trust. Task 4 is the one about who and about how you deal with each of them. It is also the only one of the three that names a plan, the engagement plan, and that carries weight in the exam, because when an option talks about executing the plan it is pointing here and not at the other two.

Task 5, align stakeholder expectations

It has four enablers. Categorize stakeholders, identify stakeholder expectations, facilitate discussions to align those expectations, and organize and act on mentoring opportunities.

The third one is the heart of the task. Aligning is not informing, it is sitting people down in a conversation where expectations touch and somebody gives ground. The fourth is the one nobody sees coming, because mentoring shows up inside an expectations task rather than a team one. The outline does not explain why it put it there. Our classroom reading is that a good share of misalignment gets solved by teaching rather than negotiating, but that is our reading and it is worth knowing where the source stops.

Task 6, manage expectations, and the word that changes

Here is the find of this post, and it comes from reading the outline with a magnifying glass instead of reading a summary.

The three enablers of task 6 do not say stakeholders. They say internal and external customers. Identify their expectations, align and maintain outcomes to those expectations, and monitor their satisfaction and respond as needed.

It is the only one of the three tasks where the outline changes its noun, and it does not look like sloppy drafting. Task 6 is not asking you to manage everybody’s expectations, it is asking you to manage the expectations of whoever receives the outcome.

That is where the exam trap is. A scenario puts an influential, loud stakeholder in front of you who is nobody’s customer. Handle them with the task 6 mechanism and you will pick wrong, because what applies is task 4 or task 5.

The three tasks and their order are those of the official PMP exam content outline, July 2026 edition.

How they line up with PMBOK 6 and PMBOK 7

In PMBOK 6 all of this lives in a knowledge area of its own, with its processes for identifying stakeholders, planning their engagement, managing it and monitoring it. It is a process map and it gets studied as a map, with inputs and outputs.

In PMBOK 7 it lives in a performance domain, which describes not processes but the outcome you are after, productive relationships and minimal surprises. We walked through all eight performance domains at the time, and stakeholders being first on that list is no accident.

The exam outline follows neither of the two. It follows tasks, which is a third way of slicing the same reality. PMBOK 6 gives you the mechanism, PMBOK 7 gives you the outcome and the outline gives you what you will be asked to do. In PMBOK 8 stakeholders still have a domain of their own and they also absorbed a good share of communication, which we unpacked in the six principles and seven domains.

How to study them so they actually help

Do not memorize the names of the three tasks. Learn to recognize which one is operating in the scenario, which is what the exam measures.

Three quick questions settle almost every case. If you still do not know who that person is or what they want, you are in task 4. If you already know what each one wants and what they want clashes, you are in task 5. And if the person holding the expectation is the one who will receive the deliverable, you are in task 6.

That distinction is worth more than memorized enablers, and it is the same discipline of reading the scenario before the options that we work on in the exam mindset post.

The outline put three consecutive tasks where a hurried reader sees one repeated. What separates them is not vocabulary. It is who you owe what to, and that question does not get answered by memorizing.

Join the waitlist

At The PM Architect we write the PMBOK study guides in five languages, with real classroom cases and exercises that come with an explanation. They will be free. Leave your email on the home page and we’ll let you know the moment they’re ready.