Most of the attention paid to the refreshed PMP exam has gone to the domain weightings, and that is reasonable: Business Environment moved from 8% to 26%, Process from 50% to 41%, and People from 42% to 33%. But the weightings only tell you how much of the exam sits where. The task list tells you what the questions are actually about, and inside the People domain one change is easy to miss. The first task in the July 2026 outline is now Develop a common vision.
If you are studying from material written for the January 2021 outline, this task will not appear anywhere as a task. It existed, but as a single bullet buried inside a different one.
What the outline says
Under Domain I, People, the 2026 Exam Content Outline lists Task 1 as "Develop a common vision," with four enablers:
- Help ensure a shared vision with key stakeholders
- Promote the shared vision
- Keep the vision current
- Break down situations to identify the root cause of a misunderstanding of the vision
That is the whole task. It is short, but each enabler points at a different kind of scenario, and the four together describe a cycle rather than a one-time activity: establish it, communicate it, revise it, and diagnose it when it breaks.
What changed from the 2021 outline
In the January 2021 outline, People Task 1 was "Manage conflict" and Task 2 was "Lead a team." Vision appeared as the first enabler under "Lead a team" — "Set a clear vision and mission" — one bullet among seven, sitting alongside servant leadership, leadership style, and motivation.
Two things happened in the 2026 revision. The People domain was consolidated from fourteen tasks down to eight, and vision was pulled out of the leadership task and placed at the top of the domain with its own enablers. Conflict management, which used to be first, is now Task 2. "Lead the project team" is Task 3.
The consolidation matters for how you read the change. When a domain shrinks from fourteen tasks to eight, most of what moves is grouping: several old tasks fold into one broader statement. Vision went the other direction. It was promoted while everything else was being compressed, which is a reasonable signal that PMI wanted it tested on its own rather than as an aspect of leadership.
Why the shift makes sense
The outline explains its own direction. It states that the document aligns with PMI's thought leadership work on project success, which reframed success away from schedule, budget, and scope alone and toward a broader view "that encompasses stakeholder value and accomplishment of desired outcomes" — with the consensus definition being that a project delivered value worth the effort and expense.
PMI's own commentary on the exam change describes the People domain as broadened beyond internal team dynamics to include stakeholder engagement, vision alignment, and customer expectation management. Read together with the Business Environment expansion, the logic is consistent. If the exam now cares whether you can tell that a project is still worth doing, it also has to care whether everyone involved agrees on what the project is for. Those are the same question at different altitudes.
What a vision question probably looks like
You will not be asked to define "vision." Expect the usual PMP shape: a short situation, four plausible actions, and one that fits the task better than the others. The recognizable pattern is a scenario where two parties are each behaving reasonably and still pulling in different directions.
Some examples of the shape:
- The sponsor describes the project's purpose one way in a steering committee; the team has been building toward a different understanding of it, taken from the backlog.
- Two departments both support the project, and both have written down what success means, and the two definitions are not compatible.
- A team is delivering on schedule, and a key stakeholder is dissatisfied with what is being delivered.
- The business reason for the project changed mid-year, the project plan did not, and the team is still executing the original intent.
In each case the tempting answers are mechanical: update the schedule, raise a change request, escalate, add a status report. Those may be needed later. The task being tested is whether you first go back to the shared understanding of purpose and re-establish it with the people who set it.
Reading the four enablers as decision patterns
Help ensure a shared vision with key stakeholders. Note the wording — not "write the vision," but ensure it is shared, and shared with key stakeholders, not only with the team. When a scenario shows the team aligned internally but out of step with the sponsor or customer, the gap is here. The action is facilitation: get the relevant parties in the same conversation and reach one statement of purpose both recognize.
Promote the shared vision. Vision that exists only in a charter is not doing anything. This enabler covers the repeated, deliberate work of connecting current work to purpose — in iteration reviews, in status conversations, in how priorities get explained when something is cut. If a scenario says the vision was agreed months ago and nobody can restate it now, the failure is promotion, not agreement.
Keep the vision current. This is the enabler most likely to catch people trained on older material, because the instinct from predictive thinking is that the charter is stable and changes go through change control. The outline treats the vision as something that can legitimately need revising when the business context shifts. The neighboring Business Environment task on evaluating external business environment changes gives you the trigger; this enabler gives you the response.
Break down situations to identify the root cause of a misunderstanding of the vision. This is diagnostic language, and it is asking you not to treat the symptom. A stakeholder rejecting a deliverable, a team debating scope every sprint, and a recurring disagreement about priority can all be surface effects of the same unstated disagreement about purpose. The expected behavior is to analyze before acting.
How this differs from the stakeholder tasks
The People domain also contains Task 4, Engage stakeholders; Task 5, Align stakeholder expectations; and Task 6, Manage stakeholder expectations. These overlap with vision work, and the exam will rely on you separating them.
A workable distinction: the vision task is about agreement on what the project is for. The expectation tasks are about agreement on what a particular stakeholder will receive, when, and how they will hear about it. Both can appear in one scenario. The question stem usually tells you which is at issue — a disagreement about purpose, direction, or whether the project is still the right project points to Task 1; a disagreement about a deliverable, a date, or communication frequency points to Tasks 4 through 6.
Traps worth naming
- Choosing a documentation action over a conversation. Updating the charter records an alignment that has not happened yet.
- Escalating immediately. Escalation is appropriate when a decision is outside your authority, not as a substitute for facilitating a discussion you could hold.
- Treating vision as a kickoff artifact. Two of the four enablers are about the period after the vision is set.
- Reading "common vision" as a team-only concern. Three of the four enablers involve stakeholders outside the delivery team.
How to study it
This does not need much study time — it is one task of eight in a domain worth 33%. What it needs is a re-read of the outline itself, which is short and free, and a habit when you review practice questions: whenever a scenario involves two parties who both seem reasonable and still disagree, ask whether the underlying problem is purpose rather than process. That habit will also help you on the Business Environment governance and value questions, which test adjacent judgment.
If your study material predates July 2026, check whether it discusses vision at all outside a list of leadership qualities. If it does not, that is a gap worth closing before you sit the exam.