Leading Project Teams

People work in the 2026 PMP outline

The People domain accounts for 33 percent of the July 2026 PMP exam. Its tasks cover developing a shared vision, managing conflict, leading the team, engaging stakeholders, aligning and managing expectations, transferring knowledge, and planning communication. Questions describe a project situation and ask what the project manager should do. The strongest answer usually addresses the cause of the problem, works with the people involved, and protects the project’s intended value.

The 2026 outline applies predictive, adaptive, and hybrid approaches across all three domains. People tasks do not belong only to agile questions. A predictive project still needs a shared vision, conflict resolution, stakeholder engagement, knowledge transfer, and clear communication. Choose the action that fits the scenario rather than matching a method label to a memorized answer.

Develop a common vision

A project vision explains the outcome the project is meant to create and why it matters. The project manager helps key stakeholders understand the same intended result, communicates it in ways that fit their needs, and keeps it current when the business context changes. A vision is useful only when team members can connect their work to it.

Suppose a sponsor describes success as launching by a fixed date, while users expect the release to include a feature that is still in discovery. The project manager should surface the difference, clarify desired outcomes, and facilitate alignment with the sponsor and users. Quietly letting each group keep its own definition invites late conflict and rework. The next step is a shared understanding that can guide scope and priority decisions.

When the team misunderstands the vision, diagnose the source before repeating the same message louder. The cause may be an unclear objective, competing incentives, a translation issue, or a change that was not communicated. Break the situation into specific expectations and check what each stakeholder heard. Then update the message or decision process.

Manage conflict with the right intervention

Conflict can arise from scarce resources, unclear roles, technical disagreement, schedule pressure, cultural differences, or unmet expectations. The project manager first identifies the source and context. A disagreement about a design trade-off calls for evidence and decision criteria. A conflict caused by disrespectful behavior also requires ground rules and a safe way to address the conduct.

The goal is a durable resolution that supports project objectives and working relationships. Facilitation and collaboration can reveal interests behind stated positions. A compromise may be practical when time is limited and both parties can accept a partial outcome. A directive decision may be necessary during an urgent safety issue or when authority and escalation rules make the decision clear. Avoid choosing a style without reading the context.

Original example: the data team wants to freeze a new interface because its current test results are stable. The operations team wants another week to test an integration defect that could delay the first customer rollout. The manager should clarify impact and decision criteria, bring the relevant people together, and agree on evidence and an owner. If the issue crosses the project manager’s authority or a risk threshold, escalate through the established governance path. Simply telling the teams to work it out does not resolve a material delivery risk.

Ground rules make conflict easier to handle. Teams can agree how to challenge an idea, how decisions are recorded, and when a concern must be escalated. If a team member violates those rules, address the behavior promptly and fairly. A conflict left unaddressed can lower trust, hide risks, and make routine coordination harder.

Lead and empower the team

Leadership is not one fixed style. The project manager considers the task, team capability, urgency, organizational environment, and decision rights. A new team facing an unfamiliar safety-critical task may need explicit coordination and coaching. An experienced team solving a technical issue may perform better when given autonomy and access to the people who can remove blockers.

Empowerment does not mean abandoning the team. The project manager establishes expectations, makes roles clear, helps the team solve problems, and represents team needs to sponsors and functional managers. The manager should remove obstacles within their authority and use governance when an obstacle needs higher-level action. The team remains responsible for its work, while the project manager supports the conditions for effective delivery.

A cross-functional team may have different incentives and professional vocabulary. Clarify decision rights, dependencies, and what “done” means for each deliverable. Ask team members to identify risks and propose options. The project manager can support varied perspectives without allowing important decisions to remain ownerless.

Engage stakeholders and align expectations

Stakeholder engagement begins with identification and analysis. Consider each stakeholder’s influence, interest, expectations, and effect on the work. Tailor communication to what the person needs to understand or decide. A senior sponsor may need a concise view of outcomes, risks, and decisions. A technical lead may need dependencies and acceptance criteria. A customer may need demonstrations and a clear feedback route.

Engagement is more than distributing status reports. The project manager listens, tests assumptions, builds trust, and acts on useful feedback. If expectations conflict, facilitate a discussion and document the agreed priority or trade-off. Do not promise an outcome that the team cannot deliver merely to end a difficult conversation.

Example: a customer asks the team to add a reporting feature after the iteration has started. In an adaptive approach, the project manager can help the product owner assess value and priority with the customer, then decide whether to replace lower-priority work in the backlog. In a predictive approach, the team uses the agreed change process to analyze impacts and obtain approval. In either case, acknowledge the request, assess it, and make the decision through the project’s authorized process.

Manage communication as a feedback loop

A communication strategy identifies who needs what information, when they need it, how they can respond, and which governance decisions require a record. Good communication is two-way. A report should show whether the project is meeting an agreed threshold, what changed, what the impact is, and what decision or support is needed.

Do not send every stakeholder the same dense status pack. Tailor detail to the audience while preserving a consistent underlying source of project information. Provide accessible formats and confirm whether the recipient understood the decision or action. When a response is essential, set a deadline and follow up through an agreed channel.

For example, a project dashboard shows the launch remains on schedule but a vendor integration has a 30 percent chance of missing a critical date. The sponsor needs the probability, impact, mitigation choices, decision deadline, and owner. A green overall status without the emerging risk conceals information needed for action. A technical team may need the dependency list and test evidence that support the estimate.

Transfer knowledge before people leave

Knowledge transfer prevents critical information from disappearing when a team member, vendor, or phase ends. Identify what knowledge is necessary, who holds it, who needs it, and how the recipient will demonstrate understanding. Documentation is one method, but a handoff can also include a walkthrough, paired work, recorded demonstration, or supported transition.

Suppose a specialist will leave after configuring a complex data pipeline. A folder of notes may not reveal why certain settings were chosen or how to diagnose a failed job. The project manager can arrange a live walkthrough, record recovery steps, identify the system owner, and have the receiving team run a test. The evidence of transfer is the new owner’s ability to operate or maintain the system, not the existence of a file.

Situational practice

A senior developer and a product owner disagree about whether to release a feature with a known usability problem. The release date is close, and the issue affects an accessibility requirement. The project manager should first clarify the requirement and impact, involve the appropriate compliance or accessibility authority, and facilitate a decision under the organization’s release governance. A majority vote or schedule pressure alone does not resolve a compliance obligation.

A remote team misses several handoffs because team members are in different time zones. Replacing the team is not the first response. The project manager should examine handoff timing and information needs, agree on a reliable communication method, define ownership and response expectations, and evaluate whether the change improves flow. Different schedules may need an asynchronous process with written decisions rather than more live meetings.

A stakeholder continues to request work outside the project objective. The manager should understand the underlying need, compare it with agreed outcomes, and explain how the request will be evaluated. If the request creates a worthwhile opportunity, use the authorized prioritization or change process. If it does not fit, communicate the reason and preserve the agreed scope.

Common answer traps

A frequent trap is escalating every disagreement before the project manager has understood it. Escalation is appropriate when authority, risk, policy, or agreed thresholds require it. Another trap is imposing a solution before hearing the team members who hold relevant information. The exam often rewards a first step that clarifies the situation and engages the people closest to it.

Candidates can also mistake communication for engagement. Sending a memo does not establish that expectations are aligned. Asking for feedback, resolving discrepancies, and confirming the decision closes the loop. Likewise, assigning a task does not guarantee knowledge transfer; the receiving person must be able to use the information.

In a scenario question, identify the immediate problem, the people with knowledge or authority, and the project outcome at risk. Then choose an action that is ethical, proportionate, and consistent with the project’s approach. Do not assume that every question has one universal “servant leader” response. Leadership should fit the conditions described.

How to study the People domain

Use the July 2026 PMP Examination Content Outline as the task list. For each task, write a short situation that could occur in a project and explain the manager’s first useful action, who should be involved, and what evidence would show the issue is resolved. This turns broad labels such as “engage stakeholders” into decisions you can practice.

Mix predictive, adaptive, and hybrid scenarios. Keep the same people problem and vary the project setting. For example, practice resolving a stakeholder expectation conflict through an approved change request in a predictive setting and through backlog prioritization in an adaptive setting. The underlying goal is alignment; the decision mechanism differs.

Use fresh questions and explain why each alternative is weaker in the scenario. A good review asks: Did the choice address the root cause? Did it respect authority and policy? Did it involve the right people? Did it protect value and relationships? The exam outline describes scenario-based application of project management concepts, so memorizing task titles is not enough.

The People domain appears alongside Process and Business Environment, and approaches occur throughout all domains. This article covers the People tasks in the 2026 outline. PMI may revise future outlines, so keep a study plan tied to the exam version you will take.