III.7 — Support Organizational Change

III.7 · Last updated: 24/08/2026

Where this task sits

III.7 — Support Organizational Change is the seventh task in the Business Environment domain of the 2026 ECO. The domain carries 26% of the exam.

It is one of the least enabler-heavy tasks in the entire ECO — just two:

• Assess organizational culture
• Evaluate the impact of organizational change on the project and determine required actions

Two bullets make it easy to assume the task is small. But notice: both start with a verb of assessment, and the subject of both is not the project — it is the organization. This task does not ask you to manage the project; it asks you to read the organization the project is swimming in.

🔴 Do not trust the number

This task sits right in the middle of the 2026 renumbering:

• In 2021, III.4 was support organizational change. In 2026 that topic is III.7.
• In 2026, III.4 is remove impediments and manage issues. In 2021 that topic lived in Domain I.

So an older source tagged "III.4" may be describing this page's subject, while a "III.4" tagged against the 2026 outline is something else entirely — impediments and issues. III.3 moved inside the same domain too (now change control, formerly external business environment).

There is also a wording collision: the "change" in this task's title gets confused with the "changes" in III.3. They are different things — III.3 manages change requests inside the project, III.7 supports transformation inside the organization. For the general shape of the trap, see what changed in the 2026 PMP exam.

A project is already an instrument of organizational change

This task's footing in PMBOK sits in a definition near the very front of the book.

Under the heading "Value creation through organizational change," The Standard for Project Management says: projects, in pursuit of value, drive change in organizations. From a business perspective, a project's purpose is to move an organization from one state to another to achieve a specific objective (PMBOK® 8, Standard p.7).

The model it draws has three states:

• Current state — where the organization sits before the project begins.
• Transition state — on some projects, an intermediate state where several steps are taken in a structured manner to reach the future state.
• Future state — the desired result of the change driven by the project.

Successful completion of a project results in the organization moving to the future state and achieving value for the organization, as defined by key stakeholders (PMBOK® 8, Standard p.7). The book gives it a figure as well: Impact of Projects on Organizational States (PMBOK® 8, Standard p.8).

Translated for the exam: organizational change is not a side effect of the project — it is the output.

Enabling change is the value itself

Listing business value, the book puts change directly on the list. One of the ways business value is produced is enabling the changes needed to facilitate an organizational transition to its desired future state (PMBOK® 8, Standard p.14).

The same page splits value into two columns: tangible (monetary assets, profitability, market share, infrastructure capabilities) and intangible — productivity, environmental improvements, reputation, brand recognition, public benefit, acquired knowledge, compliance, and employee well-being (PMBOK® 8, Standard p.14).

Most of what organizational change returns lands in that second column. That is why the option rejecting a change because "its benefit cannot be measured" is usually the wrong answer.

Assessing organizational culture

The ECO's first enabler says "assess culture" — so what exactly is culture?

The Standard classifies organizational culture as an enterprise environmental factor (EEF) internal to the organization, and enumerates it: vision, mission, values, beliefs, cultural norms, leadership styles, hierarchy and authority relationships, organizational styles, and ethics and codes of conduct (PMBOK® 8, Standard p.18).

Its classification as an EEF has a consequence the exam leans on: EEFs influence the project, but the project cannot change them. The ECO does not say "change the culture," it says "assess it." The right answer is never to fight the culture, but to read it and act accordingly.

Culture's most concrete effect shows up in approach selection. The book notes that adaptive approaches may fit better in an organizational culture that more easily embraces uncertainty while also emphasizing self-managed teams, flexible thinking, and innovation. The same passage raises organizational capability: organizational policies, ways of working, reporting structures, and attitudes should all be aligned to employ delivery methods successfully (PMBOK® 8, Standard p.68).

Culture changes not just the method, but the solution

The book's own example is the most instructive part of this task.

A value-focused approach aligns the project with business outcomes like maximizing usage and adoption. A deeper look might reveal a fast-paced organizational culture that values simplicity of experience over complexity of features. By reducing features and customizations, the more simplified solution might better match the culture, and thus increase overall usage and satisfaction (PMBOK® 8, Standard p.42).

This pattern recurs on the exam: a technically superior solution that does not fit the culture will not be adopted — and a solution that is not adopted produces no value.

Transition and readiness requirements

Support for organizational change is not an abstract intention; in the book it stands as a documented requirement category.

Listing requirement types, the Guide places a third alongside functional and nonfunctional: transition and readiness requirements describe temporary capabilities, such as data conversion and training requirements, needed to transition from the current, as-is state to the desired future state (PMBOK® 8, Guide p.130).

Two words there matter for the exam: temporary and training. The work that supports organizational change is not part of the permanent product, but it belongs in the requirements documentation; when it is left out, the project gets delivered and never adopted.

Change affects project performance

Finally, organizational change is not only something the project produces — it can also arrive at the project from outside. That is exactly what the ECO's second enabler asks: evaluate the impact of the change on the project.

Listing factors that may alter project performance, the Guide includes organizational change management — alongside the team environment, geographical locations of team members, communications among stakeholders, internal and external politics, and cultural issues and organizational uniqueness (PMBOK® 8, Guide p.79).

When the organization itself is transforming, the project feels it: priorities shift, stakeholders change, approval paths get redrawn. That is why this task lives in Business Environment — its subject is not the inside of the project but its surroundings.

The Guide's note on the PMO points the same way: a well-developed PMO aligns its culture with that of the organization, facilitating smoother adoption of project management methodologies (PMBOK® 8, Guide p.236).

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.