Overview
People is 33% of the PMP exam, covering the leadership and interpersonal side of running projects. It has eight tasks. Developing a common vision covers creating and sustaining a shared vision with stakeholders. Managing conflicts covers identifying conflict sources and applying resolution strategies. Leading the project team covers setting expectations, empowering the team, servant leadership and establishing roles. Engaging stakeholders covers identifying, analyzing and building trust with them. Aligning and managing stakeholder expectations cover categorizing stakeholders and keeping expectations and outcomes aligned. Knowledge transfer covers capturing and sharing critical knowledge. Communication covers defining a communication strategy, transparency and feedback.
Under the 2026 ECO, People dropped from 42% to 33% but remains heavily weighted, and the exam is scenario-based: it tests what a project manager should do in a situation, favoring servant leadership, collaboration and emotional intelligence. About 60% of questions involve agile or hybrid contexts, so leadership is tested across predictive, agile and hybrid delivery.
How it's tested
PMP questions are situational scenarios asking what a project manager should do, so the People domain tests leadership judgment rather than recall. Read the scenario for the interpersonal dynamic, and favor the proactive, collaborative, servant-leadership response that empowers the team and engages stakeholders, rather than directive or avoidant options.
-
Lead, do not command
A team situation is described, and you choose the servant-leadership response that empowers and supports over the directive one.
-
Resolve conflict constructively
A conflict is described, and you choose to understand the source and collaborate rather than avoid or impose.
-
Engage stakeholders proactively
A stakeholder situation is described, and you choose early, trust-building engagement over reactive or minimal contact.
Two team members disagree sharply over a technical approach and the tension is affecting the team. A directive answer picks one side, and an avoidant answer ignores it. The servant-leader response first understands each person's underlying concern, then facilitates a collaborative resolution the team can own, treating conflict as something to address openly at the team level, which is the people-first approach the exam consistently rewards.
Domains 8
Official domains from the PMI outline, in outline order.
1.1 Develop a common visionCreating and sustaining a shared vision with stakeholders.
- What it means
- This covers helping ensure a shared vision with key stakeholders, promoting that vision, keeping it current, and breaking down situations to find the root cause when the vision is misunderstood.
- What to understand
- A shared vision aligns the team and stakeholders on the project's purpose and desired outcomes, which motivates and guides decisions. The project manager co-creates and continually reinforces this vision, and when people drift from it, diagnoses the root cause rather than just restating it. A clear, shared vision underpins team cohesion.
- How it shows up
- A misalignment or motivation situation is described, and you must choose how to create, promote or restore the shared vision.
- Common confusion
- Treating the vision as a one-time statement rather than something continually promoted and kept current.
1.2 Manage conflictsIdentifying conflict sources and applying resolution strategies.
- What it means
- This covers identifying the sources of conflict, analyzing its context, implementing an agreed resolution strategy, communicating conflict-management principles, and establishing and enforcing common ground rules.
- What to understand
- Conflict is normal and, handled well, can be constructive. The project manager identifies the underlying source, understands the context, and guides the parties to a collaborative resolution, ideally one they agree on, rather than avoiding it or imposing a decision. Ground rules set expectations that prevent and contain conflict. Collaboration and confrontation of the problem are generally preferred.
- How it shows up
- A conflict is described, and you must choose the constructive, collaborative resolution approach.
- Common confusion
- Choosing to avoid conflict or impose a solution rather than understanding its source and collaborating on a resolution.
1.3 Lead the project teamSetting expectations, empowering the team, and servant leadership.
- What it means
- This covers establishing team-level expectations, empowering the team, solving problems, representing the voice of the team, supporting diverse experiences and perspectives, determining an appropriate leadership style, and establishing clear roles and responsibilities.
- What to understand
- The PMP favors servant leadership: the project manager empowers the team, removes obstacles, supports diversity, and adapts leadership style to the situation, rather than commanding. Clear roles and shared expectations let a self-organizing team perform. Representing the team's voice and solving problems collaboratively are central, especially in agile and hybrid contexts.
- How it shows up
- A team-leadership situation is described, and you must choose the empowering, servant-leadership response.
- Common confusion
- Choosing a directive, command-and-control style where servant leadership and empowering the team are preferred.
1.4 Engage stakeholdersIdentifying, analyzing and building trust with stakeholders.
- What it means
- This covers identifying and analyzing stakeholders, analyzing and tailoring communication to their needs, executing the stakeholder engagement plan, optimizing alignment between stakeholder needs and project objectives, and building trust and influence.
- What to understand
- Stakeholder engagement is proactive and continuous: the project manager identifies all stakeholders, analyzes their interest and influence, tailors communication to each, and builds trust so they support the project. Engaging stakeholders early and often, and aligning their needs with objectives, prevents problems that reactive engagement causes.
- How it shows up
- A stakeholder situation is described, and you must choose the proactive engagement and trust-building response.
- Common confusion
- Engaging stakeholders reactively or minimally rather than identifying, analyzing and proactively building trust with them.
1.5 Align stakeholder expectationsCategorizing stakeholders and aligning their expectations.
- What it means
- This covers categorizing stakeholders, identifying their expectations, facilitating discussions to align expectations, and organizing and acting on mentoring opportunities.
- What to understand
- Different stakeholders have different and sometimes conflicting expectations, so the project manager categorizes them, surfaces their expectations, and facilitates discussion to align them with each other and the project. Proactively aligning expectations, and mentoring where helpful, prevents later disputes over what the project should deliver.
- How it shows up
- A stakeholder expectation situation is described, and you must choose how to align or facilitate their expectations.
- Common confusion
- Letting stakeholder expectations diverge rather than facilitating alignment among them and with the project.
1.6 Manage stakeholder expectationsAligning outcomes to customer expectations and monitoring satisfaction.
- What it means
- This covers identifying internal and external customer expectations, aligning and maintaining outcomes to those expectations, and monitoring customer satisfaction and expectations, responding as needed.
- What to understand
- Beyond aligning expectations once, the project manager continually keeps project outcomes matched to what internal and external customers expect, monitors their satisfaction, and responds when expectations shift or gaps appear. Ongoing management of expectations, not just setting them, sustains stakeholder support and perceived value.
- How it shows up
- A customer satisfaction or expectation gap is described, and you must choose how to realign outcomes or respond.
- Common confusion
- Setting expectations once and not monitoring or responding to shifts in customer satisfaction.
1.7 Help ensure knowledge transferCapturing and sharing critical project knowledge.
- What it means
- This covers identifying knowledge critical to the project, gathering that knowledge, and fostering an environment where knowledge is transferred among team members and to the organization.
- What to understand
- Knowledge, both explicit and tacit, is a project asset that must be captured and shared so it is not lost when people leave and so the team and organization learn. The project manager identifies critical knowledge and creates a culture and mechanisms, such as collaboration and documentation, that encourage its transfer.
- How it shows up
- A knowledge-loss or sharing situation is described, and you must choose how to capture or transfer knowledge.
- Common confusion
- Relying only on documentation rather than fostering an environment that also transfers tacit knowledge.
1.8 Plan and manage communicationCommunication strategy, transparency and feedback.
- What it means
- This covers defining a communication strategy, promoting transparency and collaboration, establishing a feedback loop, understanding reporting requirements, creating reports aligned with stakeholder expectations, and supporting reporting and governance processes.
- What to understand
- Communication is often cited as the project manager's most important skill. A deliberate communication strategy tailors the right information to the right audience through the right channel, with transparency and a feedback loop so issues surface early. Effective, proactive communication prevents most misunderstandings and is a recurring correct answer.
- How it shows up
- A communication need or breakdown is described, and you must choose the proactive, transparent communication approach.
- Common confusion
- Communicating reactively or uniformly rather than with a tailored strategy, transparency and feedback.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Servant leadership
Leading by empowering and serving the team.
- Remember
- The preferred PMP leadership style.
- Tested as
- Team leadership questions.
- Trap
- Choosing command-and-control.
-
Shared vision
A common understanding of purpose and outcomes.
- Remember
- Continually promoted, not one-time.
- Tested as
- Vision and motivation questions.
- Trap
- Treating it as a single statement.
-
Conflict resolution
Addressing conflict constructively at its source.
- Remember
- Collaborate and confront the problem.
- Tested as
- Conflict questions.
- Trap
- Avoiding or imposing a solution.
-
Stakeholder engagement
Proactive, tailored involvement of stakeholders.
- Remember
- Engage early and build trust.
- Tested as
- Stakeholder questions.
- Trap
- Reactive or minimal engagement.
-
Emotional intelligence
Understanding and managing emotions, one's own and others'.
- Remember
- Underpins leadership and conflict handling.
- Tested as
- People questions.
- Trap
- Ignoring the interpersonal dimension.
-
Empowering the team
Giving the team authority to self-organize and decide.
- Remember
- Prefer empowerment over micromanagement.
- Tested as
- Team questions.
- Trap
- Micromanaging the team.
-
Resolve before escalating
Handling issues at the team level first.
- Remember
- Escalate only when needed.
- Tested as
- Situational questions.
- Trap
- Escalating prematurely.
-
Tailored communication
Matching message, audience and channel.
- Remember
- Communication is the PM's top skill.
- Tested as
- Communication questions.
- Trap
- One-size-fits-all communication.
-
Knowledge transfer
Capturing and sharing explicit and tacit knowledge.
- Remember
- Foster a sharing environment.
- Tested as
- Knowledge questions.
- Trap
- Relying on documentation alone.
-
Ground rules
Agreed team norms of behavior.
- Remember
- Set them early to prevent conflict.
- Tested as
- Team questions.
- Trap
- Having no agreed norms.
-
Agile and hybrid leadership
Leading self-organizing teams across delivery approaches.
- Remember
- About 60% of questions are agile or hybrid.
- Tested as
- Most People questions.
- Trap
- Assuming a purely predictive context.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Servant leadership vs. command-and-control
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Servant leadership | Empower and serve the team | Removes obstacles, enables | Choosing command-and-control |
| Command-and-control | Direct and instruct the team | Top-down authority | Preferring it on the PMP |
Conflict approaches
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Collaborate / confront | Work through the problem together | Win-win, addresses the source | Overlooking it as the best option |
| Avoid / withdraw | Ignore or postpone the conflict | Leaves the issue unresolved | Choosing it to keep peace |
| Force / direct | Impose a solution | Win-lose | Using it as a default |
Proactive vs. reactive engagement
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Proactive engagement | Identify and involve stakeholders early | Builds trust, prevents issues | Engaging only when problems arise |
| Reactive engagement | Respond after issues surface | Firefighting | Treating it as sufficient |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Escalate first
- What candidates pick
- Immediately escalate a team issue to the sponsor.
- Why it looks right
- Escalation seems decisive.
- Why it's wrong
- The project manager should first try to resolve the issue at the team level; escalation is a later resort when it cannot be resolved.
Clue to watch for The issue could be addressed within the team first.
-
Pick a side in conflict
- What candidates pick
- Decide the disagreement by choosing the better technical option.
- Why it looks right
- It resolves it quickly.
- Why it's wrong
- The people-first approach understands each party's concern and facilitates a collaborative resolution, rather than imposing a winner.
Clue to watch for Two people are in conflict and the relationship matters.
-
Command the team
- What candidates pick
- Direct the team exactly what to do to fix a problem.
- Why it looks right
- It feels efficient.
- Why it's wrong
- Servant leadership empowers the team to solve the problem with the manager's support, which the PMP prefers.
Clue to watch for The team could be empowered to solve it.
-
Minimal stakeholder contact
- What candidates pick
- Engage a difficult stakeholder only when a problem arises.
- Why it looks right
- It avoids friction.
- Why it's wrong
- Proactive, tailored engagement builds trust and prevents issues; reactive contact lets problems grow.
Clue to watch for A stakeholder's support or resistance affects the project.
-
Vision is one-time
- What candidates pick
- State the vision once at kickoff and move on.
- Why it looks right
- The vision was communicated.
- Why it's wrong
- The vision must be continually promoted and kept current, and misalignment addressed at its root.
Clue to watch for The team has drifted from the project's purpose.
-
Documentation equals knowledge transfer
- What candidates pick
- Rely solely on documents to transfer knowledge.
- Why it looks right
- Documentation is tangible.
- Why it's wrong
- Tacit knowledge needs an environment of collaboration and interaction to transfer, not just documents.
Clue to watch for Critical experience could be lost when someone leaves.
Answer framework
For any People-domain scenario, use these steps to find the answer the PMP expects.
- Read the scenario carefully for the interpersonal dynamic at play, and ask what a servant leader focused on the team and stakeholders would do in that situation.
- Favor empowering, supporting and collaborating over directing, avoiding or imposing.
- For conflict, understand each party's underlying concern and facilitate a collaborative, agreed resolution.
- Engage and align stakeholders proactively, tailoring communication and building trust before problems arise.
- Resolve issues at the team level first, communicate transparently, and escalate only when the team cannot resolve them. Where two options seem to fit, choose the one that most precisely matches the scenario and the chosen delivery approach.
Practice question
Want more like this? The PMP practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Approach this domain by internalizing the PMP mindset, since the exam tests judgment in scenarios, not definitions. The recurring correct instinct is servant leadership: empower and support the team, collaborate, communicate proactively, engage stakeholders early, and resolve issues at the team level before escalating. Whenever an option is directive, avoidant or escalates prematurely, it is usually wrong.
Study conflict management closely, learning to prefer collaboration and confronting the problem at its source over avoiding or forcing. Learn stakeholder engagement as a proactive, continuous, trust-building activity, and communication as a deliberate, tailored strategy, since communication is the project manager's most cited skill.
Because about 60% of questions involve agile or hybrid contexts, practice applying these leadership behaviors to self-organizing teams, not only predictive projects. Drilling many situational practice questions and examining why the people-first answer wins is the most effective preparation. Afterwards, move to Domain 2, Process. Because the PMP tests judgment in scenarios rather than recall, drill many situational practice questions and examine why the best-practice answer wins, applying the mindset across predictive, agile and hybrid contexts, and review missed questions by domain.
FAQ
How much of the PMP exam is the People domain?
People is 33% of the exam under the 2026 Examination Content Outline. It dropped from 42% in the previous outline but remains heavily weighted, covering the leadership and interpersonal side of projects.
What leadership style does the PMP exam favor?
Servant leadership: empowering and supporting the team, removing obstacles, and collaborating, rather than command-and-control. Scenario answers that empower the team and engage people are usually correct.
How should I handle conflict questions?
Favor understanding the underlying source of the conflict and facilitating a collaborative, agreed resolution. Collaborating and confronting the problem is generally preferred over avoiding it or imposing a solution.
When should a project manager escalate an issue?
Only after trying to resolve it at the team level first. The exam often penalizes answers that escalate immediately when the project manager could address the issue with the team.
Is the People domain tested in agile contexts?
Yes. About 60% of the exam involves agile or hybrid approaches, and leadership, conflict, stakeholder engagement and communication are all tested with self-organizing teams, not only predictive projects.
Why is communication so emphasized?
Communication is the project manager's most important and most cited skill. A deliberate, tailored, transparent communication strategy with a feedback loop prevents most project problems, so proactive communication is a recurring correct answer.
How does the People domain connect to the rest of the exam?
Leading people enables the delivery work of the Process domain and the governance and change of the Business Environment domain, so the people-first mindset threads through the whole exam.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Same subject: Domain 2: Effective People Management (9%)
- Project Management Professional (PMBOK 7) Same subject: Domain 1: People (33%)
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 1 knowledge
You have covered vision, conflict, team leadership, stakeholder engagement and communication. Test whether you can choose the servant-leadership, people-first response under exam conditions.