The PMP People Domain: What 33% of the Exam Covers

What changed in the PMP People domain in July 2026

Under PMI's 2026 Exam Content Outline (ECO, revised August 11, 2026, as checked on October 27, 2026), People accounts for 33% of the exam. PMI's page on the new exam gives the earlier weight as 42%, so the domain lost 9 percentage points when the update went live on July 9, 2026. Process lost the same amount, and Business Environment grew from 8% to 26%.

Two facts keep the drop in proportion. A third of the exam is still roughly one question in three. And the ECO says every exam includes questions on all tasks in a domain, so none of the eight People tasks can be skipped. The practical change is to move some study hours toward Business Environment, not away from people skills altogether.

The content shifted as well as the weight. PMI's July 10, 2026 blog says the earlier People domain leaned on internal team dynamics, and the updated one adds a common vision, stakeholder engagement, internal and external customer expectations, more strategic communication planning, and support for reporting and governance. Full PMP prep on Passy is not on sale yet; its page shows how many People-domain questions full prep plans at launch.

The eight PMP People tasks, the decision behind each, and an original scenario

The task names below are paraphrased. All scenarios and names are invented for practice.

Task 1: build and keep a shared vision

What it tests: getting key people to describe the same outcome, and fixing it when their descriptions drift apart.

Scenario: Halfway through a project to merge two customer-service centers, one team lead tells new hires the goal is lower cost, while another says it is shorter wait times. Strong response: find out why the vision split, revisit it with the sponsor and key stakeholders, and restate it in terms both leads can repeat. Picking one version yourself skips the root cause.

Task 2: manage conflict

What it tests: finding what a conflict is really about, settling it in a way the parties accept, and keeping the team's ground rules alive.

Scenario: Two analysts keep blaming each other for a missed data hand-off. Strong response: talk with both, discover that nobody owns the hand-off step, agree an owner, and record it in the working agreement. The PMP conflict management guide covers the approaches in detail.

Task 3: lead the project team

What it tests: giving a team clear roles and expectations, the right amount of autonomy, and a leadership style suited to where the team is.

Scenario: A new team mixes contractors and employees. Some wait for instructions while others duplicate each other's work. Strong response: work with the team on a charter and clear roles, give more guidance while the group is new, and hand over more autonomy as it matures. More on this in the PMP team leadership guide.

Task 4: engage stakeholders

What it tests: knowing who has a stake, what each of them needs from the project, and how to earn enough trust to bring them along.

Scenario: In month three a new head of compliance joins the company and has never heard of the project. Strong response: add her to the stakeholder register, learn her interests and concerns, and set up a briefing in the format she prefers before her approval is needed.

Task 5: align stakeholder expectations

What it tests: getting groups with different expectations to one agreed version, and noticing where mentoring would help.

Scenario: Finance thinks "ready for launch" means every report works. Operations thinks it means the core workflow runs. Strong response: bring both groups together, agree written launch criteria, and pair a junior analyst with the finance expert to build the reports, a mentoring opportunity as well as a fix.

Task 6: meet and monitor customer expectations

What it tests: keeping both internal and external customers' expectations in view, and acting when satisfaction slips.

Scenario: After a pilot release, the internal sales team is happy but external customers' survey scores drop because checkout feels slower. Strong response: investigate the cause with the team, share the finding, and bring a fix into the plan or backlog. One satisfied group does not cancel out the other.

Task 7: make sure knowledge is passed on

What it tests: making sure what the project knows does not leave with the people who know it.

Scenario: A rollout's pilot site learned how to train staff in half the planned time, and five more sites are due next quarter. Strong response: capture what the pilot did differently and have its trainers brief the next teams directly, rather than leaving the lesson in a closing report nobody reads.

Task 8: plan and manage communication

What it tests: deciding who needs what information, in what form, and checking that it lands, including the reports governance requires.

Scenario: The sponsor wants one page a month, the steering committee requires spend and risk figures, and the team works in a chat channel. Strong response: set out in the communication plan who gets what, in which format and how often, and ask each audience after the first cycle whether it works.

How People questions change across predictive, agile, and hybrid PMP stems

The ECO says approaches appear across all domains, so People questions come in every setting. In a predictive stem, the project manager often coordinates people assigned by functional managers and leans on formal plans. In an agile stem, the team manages its own work and the project manager acts more as a facilitator who removes obstacles. In a hybrid stem, both may apply at once. The PMP scenario-question method shows how to spot which setting you are in before choosing.

Stakeholder questions get their own treatment in the PMP stakeholder engagement guide. Once you can say which task each scenario above belongs to, test the skill on situations you have not seen. The PMP page describes how full prep is planned to let you work People-domain scenarios on their own before mixing domains.

Giving the PMP People domain the right share of study time

A simple way to plan is to split study hours roughly in line with the weights: about a third for People, two-fifths for Process and a quarter for Business Environment, then shift time toward whichever domain your practice results show is weakest. The PMP study plan builds that split for you.

For People specifically, practice on scenarios rather than definitions. Most items describe a situation with several reasonable actions, and the skill is choosing the one that addresses the cause, respects the team's agreements and stays within your authority. The 20 free PMP practice questions include People items, and for short daily recall the PMP page lists the People flashcards planned for full PMP prep.