I.3 — Lead the Project Team

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

Five older tasks under one roof

I.3 — Lead the Project Team is the third task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. Its reach is clearly wider than that of the other tasks in the domain, because in 2026 the ECO gathered here the team-related work that used to be scattered.

The ECO lists seven enablers for it:

• 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

Which old numbers now point here

The biggest structural change in Domain I happened in this task. In the neighboring tasks the numbers shifted, whereas here several tasks were folded into a single one. Older material spread team work across at least five separate tasks, and every one of them now points to I.3:

For anyone mapping old questions to the new ECO the consequence is plain. Most questions tagged I.2, I.3, I.5, I.6, and I.11 should be routed to the same task.

One piece stayed out of the merger. Team ground rules, a task of their own in 2021, did not come here; they went to I.2 — Manage Conflicts, where the ECO positions them as a tool for reducing conflict. For the numbering mix-up across the whole domain, see what changed in the 2026 PMP exam.

A single PMBOK process covers it

The Guide ties this work to the Lead the Team process, and the definition of that process already covers most of the seven enablers. By managing and leading the team, the process aims to improve competencies, team member interactions, and the overall team environment and so to enhance project performance. Tracking team member performance, providing feedback, resolving or escalating issues, and managing team changes are also within its scope. Its stated key benefit is that it influences team behavior, manages conflict, and resolves issues among team members (PMBOK® 8, Guide p.84).

In PMBOK the process sits inside the Resources performance domain (PMBOK® 8, Guide p.80). That may look odd at first, until you notice that the two documents group things by different logic. PMBOK sorts processes by what they manage, and the ECO sorts tasks by the competency it measures. You will meet the same split on II.4 — Plan and Manage Resources.

Managing and leading are different activities

This is the distinction the exam probes most often in this task, and the book draws a firm line between the two (PMBOK® 8, Guide p.84). Management activities concern the means of meeting project objectives, such as having effective processes, planning, coordinating, and measuring and monitoring the work. Leadership activities are aimed at people and cover influencing, motivating, listening, and enabling the team.

The book adds a condition straight away. A project manager should be sensitive to how willing and how able team members are to do their work, and should adjust management and leadership style to take both factors into account (PMBOK® 8, Guide p.84).

Consider what that means for a scenario that opens with "the team keeps missing deadlines". The same answer is not right every time. A team that is willing but lacks the skill needs training, while a team that has the skill but lacks the will needs motivation. Telling those two apart is precisely what this task measures.

Five dimensions of team development

Whatever shape the management activities take, the Guide groups the common aspects of developing a project team under five headings (PMBOK® 8, Guide p.84):

• Vision and objectives. They are communicated throughout the project, and the team refers to the intended outcomes when making decisions and solving problems. In the ECO this dimension is a task of its own, I.1 — Develop a Common Vision.
• Roles and responsibilities. The project manager makes sure team members understand and fulfill their roles. This can include identifying gaps in knowledge and skills and finding ways to close them through training, mentoring, or coaching.
• Project team operations. Facilitating communication within the team, problem-solving, and consensus building. Drawing up a team charter and a set of operating guidelines or team norms together with the team can be part of it.
• Guidance. Directed at the whole team so that everyone keeps heading in the right direction, although individual team members may also provide guidance on a particular task or deliverable.
• Growth. Recognizing where the team does well and pointing out where it can improve helps everyone grow, and the team sets its improvement goals jointly and takes steps to reach them.

The phrase about closing gaps through training in the second item also explains why training, a separate task in 2021, is now counted inside this one.

No single right leadership style

The enabler about determining an appropriate leadership style assumes that no style is best regardless of circumstances, and the book confirms it. According to The Standard, members of the project management team can adopt many different leadership styles depending on the individuals, situations, team structures, stakeholders, and organizational processes and culture. Leaders are expected to be versatile and able to switch between styles to get a better outcome (PMBOK® 8, Standard p.29).

The flexibility has a limit. Leaders should be able to adapt their style to the situation and the audience, but they should do so without losing their core values (PMBOK® 8, Standard p.46). The reason the book cares so much about this adaptation is also written down: a leader's style directly shapes team dynamics, motivation, and overall performance (PMBOK® 8, Standard p.47).

Trust and clarity come before empowerment

The book's counterpart to the enabler about empowering the team is one of PMBOK's six principles. The Build an Empowered Culture principle asks the project environment to promote mutual trust among stakeholders and team members and to provide full clarity on individual roles, responsibilities, team agreements, and guiding processes. Those two factors let people work together and produce synergistic effects from their interactions (PMBOK® 8, Standard p.53).

Reading empowerment as leaving the team to its own devices is therefore a mistake. The clarity the book insists on concerns roles, responsibilities, and agreements, which is why "establish clear roles and responsibilities" and "empower the team" sit side by side in the same ECO list. The first is a precondition of the second.

The same principle also takes in diversity, since it expects the culture to be built through stakeholders and teams with diverse skills, knowledge, and experience (PMBOK® 8, Standard p.53). That sentence is the counterpart of the enabler about supporting the team's varied experiences, skills, and perspectives.

Leadership is not confined to a job title

Here lies the most commonly misread part of the task, and the book is unusually direct about it. The Standard says effective leadership behaviors appear more often and from more people on high-performing projects than on low-performing ones (PMBOK® 8, Standard p.46). On the next page it states plainly that any project professional, stakeholder, or team member can demonstrate leadership behaviors, so leadership does not belong to one person (PMBOK® 8, Standard p.47).

Accountable leaders go a step further and commit to supporting the growth of other leaders around them and leaving a positive mark on their sphere of influence (PMBOK® 8, Standard p.47).

This part should be read together with the enabler about representing the voice of the team. The project manager's role goes beyond speaking on the team's behalf; it also includes creating the conditions in which the team can speak for itself. On the governance side the same logic appears as self-governance; see III.1 — Define and Establish Project Governance.

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:

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