I.4 — Engage Stakeholders

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

Where this task sits

I.4 — Engage Stakeholders is the fourth task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has six enablers:

• Identify stakeholders
• Analyze stakeholders
• Analyze and tailor communication to stakeholder needs
• Execute the stakeholder engagement plan
• Optimize alignment among stakeholder needs, expectations, and project objectives
• Build trust and influence stakeholders to accomplish project objectives

What stands out is that this task only begins the subject: in 2026 stakeholder work is split across three consecutive tasks — I.4 engaging, I.5 aligning expectations, I.6 managing expectations. Three of the domain's eight tasks are about stakeholders.

🔴 Do not trust the number

Good news for this task: I.4 stayed put. An "I.4" tag in older material also points at engaging stakeholders.

But two caveats. First, this task absorbed another: "collaborate with stakeholders," a separate task in 2021 (I.9 in question banks), now sits under I.4.

Second, its neighbors did not stay put. Domain I came down to eight tasks in 2026 (older numbers ran at least as far as I.12), and the two numbers right beside it belonged to other topics:

• In 2021, I.5 was training and I.6 was building a team. Both are inside I.3 — Lead the Project Team in 2026.

So "I.4 checked out" should not extend to the whole domain. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

The Stakeholders domain carries seven processes

In PMBOK® 8 this subject maps to one of the seven performance domains — and the one holding the most processes (PMBOK® 8, Guide p.9):

Identify Stakeholders · Plan Stakeholder Engagement · Plan Communications Management · Manage Stakeholder Engagement · Manage Communications · Monitor Stakeholder Engagement · Monitor Communications

Three of the seven are about communication outright — the PMBOK-side counterpart of the ECO making communication its own task (I.8). The domain's processes run from planning through executing to monitoring; stakeholder work is not a one-time identification.

Who counts as a stakeholder

The Guide's example list shows this task's reach: 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).

The list includes family and local communities — the concept is not limited to contracted parties.

The scale is not fixed either: a project can have a small group of stakeholders or potentially millions. There may be different stakeholders in different phases, and stakeholders' influence, power, or interests may change as the project unfolds (PMBOK® 8, Guide p.67).

The Guide widens who gets included as well: effective stakeholder identification, analysis, and engagement covers stakeholders internal or external to the organization, those who are supportive, those who are neutral, and opponents, who are not supportive (PMBOK® 8, Guide p.67).

That last item decides exam answers: an opposing stakeholder does not get removed from the list — they get written into it.

Identifying and analyzing

The ECO's first two enablers correspond to PMBOK's first process.

Among the tools of Identify Stakeholders are stakeholder analysis, document analysis, and on the data representation side stakeholder mapping/representation. The process's main output is the stakeholder register; it also produces updates to the requirements management plan, the communications management plan, the risk management plan, and the stakeholder engagement plan (PMBOK® 8, Guide p.71).

Two of those plans matter: identifying stakeholders feeds directly into the communication and engagement plans. The ECO's "tailor communication to stakeholder needs" enabler comes from that link.

The mapping methods are covered in detail on the next task — see I.5 — Align Stakeholder Expectations.

Executing the engagement plan

The ECO makes "execute the stakeholder engagement plan" its own enabler. Its counterpart is the Manage Stakeholder Engagement process, and the tool list shows this task's human side (PMBOK® 8, Guide p.74):

communication skills such as feedback; interpersonal and team skills such as conflict management, cultural awareness, negotiation, and observation/conversation; plus expert judgment and meetings.

Its inputs include the change log, issue log, lessons learned register, stakeholder register, risk register, status report, and project schedule (PMBOK® 8, Guide p.74) — stakeholder engagement is fed by the rest of the project.

The Guide names the key skills to develop in this domain: negotiation and conflict management (PMBOK® 8, Guide p.67). For the conflict side, see I.2 — Manage Conflicts.

Building trust and influencing

The ECO's last enabler carries two verbs, and both find their footing in the book.

The Standard's Build an Empowered Culture principle opens directly: stakeholders determine the success of projects. Stakeholders and team members on a project are key to its success, and they should be empowered across many dimensions (PMBOK® 8, Standard p.53).

The same principle's condition is trust: the project environment should promote mutual trust among stakeholders and team members, and there should be full clarity on individual roles, responsibilities, team agreements, and guiding processes (PMBOK® 8, Standard p.53).

Translated for the exam: "influence" here is not manipulation. The order the book establishes is trust → clarity → collaboration, with influence as the result.

The Guide also notes that technical skill alone is not enough: while having relevant technical project management skills is important, possessing the interpersonal and leadership skills to work effectively with stakeholders is just as important, if not more so (PMBOK® 8, Guide p.67).

The stakeholder list is not a frozen document

The most-skipped aspect of this task, stated plainly: the activities of identification, prioritization, and engagement should be reviewed and updated routinely, or at least when the project progresses through phases (PMBOK® 8, Guide p.67).

The reason is on the same page: stakeholders' influence, power, and interests change as the project unfolds, and different phases may bring different stakeholders.

Translated for the exam: "the stakeholder register was prepared at the start" is an incomplete answer. The right one also says when it will be revisited.

Monitoring engagement and closing the gap between current and desired levels is the subject of a separate task — see I.6 — Manage Stakeholder Expectations.

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.