I.1 — Develop a Common Vision

I.1 · Last updated: 24/08/2026

Where this task sits

I.1 — Develop a Common Vision is the first task in the People domain of the 2026 ECO. The domain carries 33% of the exam across eight tasks.

It has 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

All four rest on one assumption: a vision is not a sentence written once and hung on a wall, but an alignment that is maintained.

🔴 Do not trust the number

Domain I is the domain that consolidated the most in 2026. In older material the numbers ran at least as far as I.12; in 2026 the domain came down to eight tasks. That means almost no I number stayed where it was.

For this task, concretely:

• In 2021, I.1 was manage conflicts. In 2026 that topic is I.2 — Manage Conflicts.
• In 2026, I.1 is developing a common vision.

So an older question tagged "I.1" is most likely about conflict management. The numbers look shifted by one, but the shift is not uniform — I.3 absorbed six separate 2021 tasks, while I.7 and I.8 took over numbers whose topics left for other domains.

Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

Why vision is the domain's first task

The ECO putting this task first lines up with how PMBOK understands project initiation.

Relating the focus areas to governance, the Guide says: successful projects begin with a clear description of the desired end state. A clearly articulated business case enables stakeholder alignment on priorities and constraints, and provides team members with a broader context that informs their work (PMBOK® 8, Guide p.10).

Three parts of that sentence cover the ECO's four enablers: a clear end state (the vision itself), stakeholder alignment (the shared vision), and context for the team (promoting the vision).

Translated for the exam: "the team knows what to do but not why" is not a communication problem — it is this task's subject.

Vision is the first dimension of team development

Listing the common aspects of project team development, the Guide starts with vision and objectives: the vision and objectives are communicated throughout the project and are essential for understanding. This communication includes referencing the intended outcomes when the project team makes decisions and solves problems (PMBOK® 8, Guide p.84).

That last clause is the most practical part of this task: the function of a vision is not to be a wall poster but to be the measure consulted at the moment of decision. The ECO's "promote the vision" enabler asks for exactly that — a promoted vision is one that has become the reasoning behind decisions.

The list's other four items (roles and responsibilities, team operations, guidance, growth) are the subject of I.3 — Lead the Project Team.

Shared vision and an empowered culture

One of The Standard's six principles overlaps directly with this task.

The Build an Empowered Culture principle calls for a culture "that fosters proactive collaboration and promotes unity in shared objectives" — through stakeholders and teams with diverse skills, knowledge, and experience (PMBOK® 8, Standard p.53).

The same passage states the condition: to develop an empowered project culture, the project environment should promote mutual trust among stakeholders and team members, and there should be full clarity on individual roles, responsibilities, team agreements, and guiding processes (PMBOK® 8, Standard p.53).

"Unity in shared objectives" and the ECO's "shared vision" are two names for the same thing. The book treats it not as a communication job but as a culture job.

Keeping the vision current

The ECO's third enabler is what most material skips: a vision can change.

Its footing is the project's dependence on the outside world. Due to changes in strategy, priorities, or the external environment, the need for a project may no longer exist — the book lists this among the ways a project ends (PMBOK® 8, Standard p.7).

The need disappearing entirely is the extreme case, but the same forces can also shift a vision. Watching for changes in the external business environment is its own task — see III.8 — Evaluate External Business Environment Changes.

Translated for the exam: the option saying "the vision was agreed at the start, the discussion is closed" is wrong. A vision needs maintenance too.

The adaptive counterpart of vision

In an agile setting the vision has a concrete counterpart, and the book spells out the chain.

The Guide describes the typical relationship among product vision, product roadmap, release planning, and iteration planning; release planning establishes a high-level plan for product scope, timelines, and a releasable product, factoring in business goals, dependencies, impediments, and resource availability (PMBOK® 8, Guide p.146).

So the vision sits at the top and decomposes downward into a roadmap, releases, and iterations. Its predictive counterpart is the scope structure — see II.2 — Develop and Manage Project Scope.

The root cause of a misunderstanding

The ECO's fourth enabler names a technique: break down situations to identify the root cause.

The book's tool here is the after-action review (AAR): a simple, structured process used to analyze what happened, why it happened, and how it can be done better (PMBOK® 8, Guide p.145).

In the context of a vision, that means: if the team has misunderstood it, the right move is not to announce the vision again but to find why it was misunderstood. The source might be an ambiguous phrase, a contradictory message from a stakeholder, or a priority that changed and was never communicated.

That is also why "lack of communication" is usually a shallow answer — what the exam looks for is the option pointing at the source rather than the symptom.

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page explains the book; it does not replace it.