People
You lead people you cannot command
A project manager carries responsibility for the outcome but rarely holds authority over the people who produce it. Team members report to other managers, sponsors and customers outrank you, and vendors answer to a contract. Closing that gap is the whole job of the People domain of the PMP, and it is a large share of your score: the 2026 exam content outline gives People 33% of the exam, second in size only to Process at 41%, and breaks it into eight tasks. Every one of those tasks is solved the same way, by leading through facilitation, trust, and influence rather than by command, so the exam almost always rewards the answer that engages people directly over the one that reaches for authority. The classic trap is the decisive-sounding shortcut, escalating to the sponsor, forcing a decision, or re-reading the charter at a divided team, when the credited move is to convene the people involved and work the problem with them.
The domain unfolds in eight jobs, from vision to communication
Read this page as a map, then follow the eight subtopics in order. Develop a Common Vision builds one shared picture of success that the key stakeholders helped shape, so later trade-offs have a north star. Manage Conflicts turns friction into a resolution that holds, collaborating toward a win-win and confronting issues early rather than letting positions harden. Lead the Project Team is the servant-leadership core, enabling and empowering the team and matching your style to its readiness, the stance the Scrum Guide captures in its self-managing team. Engage Stakeholders runs the continuous cycle of identifying, analyzing, and involving the people around the project. Align Stakeholder Expectations negotiates one shared, feasible definition of success up front, before the work is built. Manage Stakeholder Expectations then keeps delivery matched to what internal and external customers actually expect as the project changes. Help Ensure Knowledge Transfer keeps hard-won know-how, especially the tacit kind held in people's heads, from walking out the door when they move on. And Plan and Manage Communication wires it together, getting the right information to the right people and confirming it was understood. Each subtopic carries the mechanisms, the worked examples, and the traps; this page just shows how they fit.
Diagnose first, facilitate second, escalate last
Across all eight jobs the People domain rewards one sequence. First understand: find the root cause, the real source of a conflict, the reason a stakeholder has disengaged, or the gap between what a customer expected and what they perceive, before you choose a response, because acting on the visible symptom leaves the driver in place to recur. Then engage people in a way that builds ownership: facilitate a shared decision instead of announcing one, coach the team instead of solving for it, convene the affected stakeholders instead of deciding alone. Authority and escalation are not wrong, they are last, used only after a genuine, direct attempt has failed or the matter truly exceeds your remit. This instinct is the practical face of leading through individuals and interactions rather than process, and it holds whether the work is predictive, agile, or hybrid; the delivery approach changes the ceremonies, not the leadership stance.
The eight People jobs and the move each rewards
| People job | What you are really doing | The move the exam rewards | Drill into |
|---|---|---|---|
| Develop a Common Vision | Building one shared picture of success | Co-create and facilitate agreement; don't announce or re-read the charter | Develop a Common Vision |
| Manage Conflicts | Turning friction into a resolution that holds | Collaborate to a win-win; confront early, escalate last | Manage Conflicts |
| Lead the Project Team | Enabling the team to deliver | Serve and empower; match your style to the team's readiness | Lead the Project Team |
| Engage Stakeholders | Keeping the right people involved | Run the identify-analyze-engage cycle; build trust, never pressure | Engage Stakeholders |
| Align Stakeholder Expectations | Agreeing what success means, up front | Negotiate one shared, feasible set before you build | Align Stakeholder Expectations |
| Manage Stakeholder Expectations | Keeping delivery matched to what customers expect | Track the gap and set honestly; never gold-plate | Manage Stakeholder Expectations |
| Help Ensure Knowledge Transfer | Keeping know-how from walking out the door | Capture tacit knowledge through people, while context is fresh | Help Ensure Knowledge Transfer |
| Plan and Manage Communication | Getting the right information to the right people | Plan per stakeholder; confirm it was understood | Plan and Manage Communication |