III.7 — Support Organizational Change

III.7 · Last updated: 11/10/2026

Reading the organization around the project

III.7 — Support Organizational Change is the seventh task in the Business Environment domain of the 2026 ECO, and the domain carries 26% of the exam. It is one of the two tasks in the whole ECO with the fewest enablers, just two:

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

A short list makes the task look small. Both enablers, though, start with a verb of assessment, and in both the thing being assessed is the organization the project works inside, with the project itself in the background. The task asks the project manager to read the organization, understand its culture, and see how the change happening around the project will reach it.

🔴 The old III.4 is today's III.7

In 2021 this task carried the number III.4. In 2026 that number went to impediments and issues, III.4 — Remove Impediments and Manage Issues. If an older source shows an organizational change question tagged "III.4", it is using the 2021 numbering. All shifts of this kind are collected in what changed in the 2026 PMP exam.

Beside the number there is a wording trap. The "change" in this task's title is often confused with the "changes" in III.3 — Manage and Control Changes, and PMBOK® 8's glossary keeps the two apart. Change control is about deciding on change requests within the project. Change management is defined as a comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from a current state to a future state with intended business benefits (PMBOK® 8, Guide p.266). Even so, the book uses the name "change management plan" for the plan that establishes the change control board (PMBOK® 8, Guide p.116). When a question uses the phrase "change management," you have to work out from the context which meaning it intends.

Every project is an organizational change

The task's footing in PMBOK sits at the very start of the book. Describing value creation through organizational change, The Standard says that projects drive change in organizations in pursuit of value. From a business perspective, a project's purpose is to move the organization from one state to another in order to reach a specific objective (PMBOK® 8, Standard p.7).

The book's model has three states. Before the project begins, the organization is in its current state. The desired result of the change the project brings about is called the future state. On some projects there is also a transition state in between, and the future state is reached in several structured steps. According to the book, a successfully completed project moves the organization to the future state and delivers value to it as key stakeholders define that value (PMBOK® 8, Standard p.7). The model is also shown in a figure (PMBOK® 8, Standard p.8, Figure 1-1).

Within this frame, organizational change is the reason the project exists, which is a much stronger role than a side effect. The book puts it even more firmly for programs, writing that programs drive significant change in organizations and should therefore be seen as more than just large projects (PMBOK® 8, Standard p.10).

Enabling change produces value too

When The Standard gives examples of how projects meet value thresholds, change appears on the list directly. One example is enabling the changes needed to facilitate the organization's transition to its desired future state (PMBOK® 8, Standard p.14). The same list includes improving efficiency, productivity, or employee well-being.

The figure on the same page divides business value into tangible and intangible elements (PMBOK® 8, Standard p.14, Figure 2-1). The tangible column holds items such as monetary assets, productivity, profitability, market share, infrastructure capabilities, and environmental improvements. The intangible column holds reputation, brand recognition, public benefit, acquired knowledge, compliance, and employee well-being, among others. A large share of the benefits that organizational change brings falls into that second column, so an answer option that dismisses a change as unnecessary because its benefit cannot be measured in money contradicts the book's definition of value.

Assessing organizational culture

The first enabler asks you to assess culture, which raises the question of what the book means by the word. The Standard classifies organizational culture as an internal enterprise environmental factor (EEF) and lists examples: vision, mission, values, beliefs, cultural norms, leadership style, hierarchy and authority relationships, organizational style, and ethics and code of conduct (PMBOK® 8, Standard p.18).

That classification has a consequence on the exam. The book defines EEFs as conditions the project team cannot directly control but that influence, constrain, or direct the project (PMBOK® 8, Standard p.18). The ECO's choice of "assess" over "change" in this enabler fits that definition. What is expected of the project manager is to read the culture and shape the project to suit it, so options that propose fighting the culture usually fall outside the task's logic.

The most visible effect of culture shows up in the choice of approach. According to the book, adaptive approaches may fit better in an organizational culture that accepts uncertainty more readily and puts self-managed teams, flexible thinking, and innovation first. The same passage mentions organizational capability, since using a delivery approach successfully requires the organization's policies, ways of working, reporting structures, and attitudes to be aligned with it (PMBOK® 8, Standard p.68). A project manager who picks an approach without assessing the culture may carry a method that looks right on paper into a setting where it cannot work.

Culture can reshape the solution itself

One of the book's examples is the most instructive part of this task. A value-driven approach aligns the project with business outcomes such as maximizing use and adoption. Looking more closely, the team may discover a fast-paced organizational culture that values a simple experience more than a wealth of features. In that case a simpler solution, reached by cutting features and customizations, fits the culture better and can raise overall usage and satisfaction (PMBOK® 8, Standard p.42).

Versions of this example come up often on the exam. A technically stronger solution that does not fit the organization's culture will not be adopted, and a solution nobody adopts cannot produce the value expected from the project.

Writing the transition into the requirements

Supporting organizational change also appears in the book as a type of documented requirement. When the Guide lists requirement types, it names transition and readiness requirements separately. They describe temporary capabilities, such as data conversion and training, needed to move from the current state to the desired future state (PMBOK® 8, Guide p.130).

Two details of that definition matter for the exam. Because these capabilities are temporary, they are not part of the lasting product, yet they still go into the requirements documentation. Training belongs to this category as well, and a delivery made before users are ready for the new system may never be adopted by the organization, even if it is technically complete.

Change can also come from outside the project

The second enabler turns the direction around. Organizational change is something the project produces, and it can also start outside the project and act on it; the enabler asks you to evaluate that effect and decide what needs to be done. When the Guide lists factors that can alter project performance, it includes organizational change management together with the team environment, the geographic locations of team members, communication among stakeholders, internal and external politics, cultural issues, and the organization's own uniqueness (PMBOK® 8, Guide p.79). While the organization transforms, the project's priorities can shift, its stakeholders can change, and its approval paths can be redrawn.

Change inside the organization is the subject of this task. Changes outside it, in the market, in technology, or in regulation, are handled in the last task of the Business Environment domain, III.8 — Evaluate External Business Environment Changes.

A note in the Guide about the PMO looks the same way. A well-developed PMO aligns its own culture with that of the organization, which makes it easier for project management methods to be adopted smoothly across the organization (PMBOK® 8, Guide p.236).

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ 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 describes the book; it does not replace it.