I.3 — Lead the Project Team

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

Where this task sits

I.3 — Lead the Project Team is the third task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has seven enablers:

• Establish expectations at the team level
• Empower the team
• Solve problems
• Represent the voice of the team
• Support the team's varied experiences, skills, and perspectives
• Determine an appropriate leadership style
• Establish clear roles and responsibilities within the team

Seven enablers cover a lot of ground — and the reason is what the ECO did when it built this task.

🔴 This task is a merger

Domain I's largest structural change in 2026 lands here. Elsewhere numbers shifted; here several tasks collapsed into one.

In older material, team-related work was spread across at least five separate tasks, and all of them now point at I.3:

The practical consequence: most questions tagged I.2, I.3, I.5, I.6, and I.11 in older material now belong under a single task. Any mapping table has to route all five numbers to the same place.

One piece went the other way: team ground rules, a separate task in 2021, did not come here in 2026 but went to I.2 — Manage Conflicts; the ECO positions ground rules as the remedy for conflict.

Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

The PMBOK counterpart: the Lead the Team process

The Guide ties this work to a single process, and the definition covers most of the ECO's seven enablers.

Lead the Team is the process of applying knowledge, skills, tools, and techniques for managing and leading the team by improving competencies, team member interactions, and the overall team environment to enhance project performance. The process also involves tracking team member performance, providing feedback, resolving and escalating issues, and managing team changes to optimize project performance. Its key benefit is that it influences team behavior, manages conflict, and resolves issues among team members (PMBOK® 8, Guide p.84).

The process sits in the Resources performance domain (PMBOK® 8, Guide p.80) — PMBOK groups processes by what they manage while the ECO groups tasks by the competency measured. That distinction is also explained on II.4 — Plan and Manage Resources.

Management activities versus leadership activities

The most frequent distinction on this task, and the book separates the two cleanly (PMBOK® 8, Guide p.84):

• Management activities focus on the means of meeting project objectives: having effective processes, planning, coordinating, measuring, and monitoring work.
• Leadership activities focus on people and encompass influencing, motivating, listening, enabling, and other activities related to leading the project team.

The book then adds the condition: a project manager should be sensitive to the willingness and ability of team members to perform their work and should adjust their management and leadership styles to account for these factors (PMBOK® 8, Guide p.84).

Translated for the exam: in a "the team is falling behind" scenario the right answer is not always the same. A willing but unable team needs training; an able but unwilling team needs motivation — and telling the two apart is this task's job.

The five dimensions of team development

Regardless of how management activities are structured, the Guide gives the common aspects of project team development under five headings (PMBOK® 8, Guide p.84):

• Vision and objectives — communicated throughout the project; includes referencing the intended outcomes when the team makes decisions and solves problems. (That dimension is a task of its own: I.1 — Develop a Common Vision.)
• Roles and responsibilities — project managers should ensure team members understand and fulfill their roles. This may include identifying gaps in knowledge and skills and developing strategies to address them through training, mentoring, or coaching.
• Project team operations — facilitating team communication, problem-solving, and consensus building; may include developing a project team charter and a set of operating guidelines or team norms.
• Guidance — directed to the overall team to keep everyone headed in the right direction; individual members may also provide guidance on a particular task or deliverable.
• Growth — identifying where the team performs well and pointing out where it can improve helps everyone grow; the team should collaboratively identify improvement goals and take steps to meet them.

The phrase "address gaps through training" in the second item explains why the training work, a separate task in 2021, now lives inside this one.

Choosing a leadership style

The ECO's "determine an appropriate leadership style" enabler assumes there is no single correct style, and the book confirms it.

The Standard says there are many leadership styles that members of a project management team can adopt based on the individuals, situations, team structures, stakeholders, and organizational processes and culture. Leaders should be versatile and able to switch between different leadership styles to achieve a better outcome (PMBOK® 8, Standard p.29).

The limit is written down too: leaders should have the capability to adapt their style to the situation and the audience; styles should be adapted based on the project's needs without losing the leader's core values (PMBOK® 8, Standard p.46).

And the effect is not small: a leader's style directly shapes team dynamics, motivation, and overall performance (PMBOK® 8, Standard p.47).

What empowerment means

The counterpart of the ECO's "empower the team" enabler is one of PMBOK's six principles.

For the Build an Empowered Culture principle, 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. These factors enable individuals to work together and provide synergistic effects from their interactions (PMBOK® 8, Standard p.53).

Note what empowerment is not: it is not "leaving people alone." The two conditions the book sets are trust and clarity — and the content of that clarity is roles, responsibilities, and agreements. That the ECO lists "establish clear roles and responsibilities" alongside "empower the team" is therefore no accident: they are two halves of one thing.

The same principle covers diversity — the culture is built "through stakeholders and teams with diverse skills, knowledge, and experience" (PMBOK® 8, Standard p.53), which is the direct counterpart of the ECO's "support the team's varied experiences, skills, and perspectives."

Leadership does not stop at the project manager

The most misread aspect of this task, and one of the book's clearest sentences.

The Standard says effective leadership behaviors are found more frequently — and from more people — on high-performing projects than on lower-performing ones (PMBOK® 8, Standard p.46).

"From more people" is decisive: leadership is not a title but a behavior distributed across the team. Accountable leaders also commit to promoting the growth of other leaders around them and making a positive impact in their sphere (PMBOK® 8, Standard p.47).

Read that alongside the ECO's "represent the voice of the team" enabler: the project manager's role is as much about building the conditions in which the team can speak for itself as it is about speaking on the team's behalf.

The governance-side counterpart of the same logic is self-governance — see III.1 — Define and Establish Project Governance.

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.