September 6, 2026 · 8 min read
TL;DR: Supporting organizational change sounds like a change-management-model topic and is not. Across the 49 questions in this bank's slice, ADKAR and Kotter appear twice each and neither is what is being tested. The scenarios describe the organization moving under a running project, and the keyed answers renegotiate the project's own commitments with whoever owns what moved. Escalation is offered 7 times and keyed zero.
Candidates prepare for this task by memorising a change model, and then the questions turn out to be about a bike-share operator whose availability targets were calculated on a diesel fleet it no longer has. There is no model in the answer. There is a target that two of the organization's own commitments now contradict, and someone has to fix that.
The organization changes. The project is already running. Something the project was counting on is no longer true, and none of it was caused by the project or approved through it.
The scenarios cluster into three shapes:
None of these are solved by helping people feel better about change. They are solved by finding the commitment that has quietly become impossible and renegotiating it with whoever owns it.
Training is the most-offered wrong answer in this slice. It appears 10 times across the 49 questions and is keyed twice, and it is attractive because organizational change genuinely does involve helping people adapt.
The test is simple: imagine everyone in the scenario has been perfectly trained. Is the problem gone? In the audiology scenario, extending the clinical training programme so every audiologist understands how the model reaches a proposed setting leaves the actual problem exactly where it was, because the model's recommendations move month to month and no amount of understanding creates a stable procedure. What is missing is a statement of what the clinician is answerable for, and only the line manager who owns the role can write it.
Common trap: treating resistance as the thing to be managed. Options mentioning resistance appear 5 times in this slice and are keyed zero times. When a scenario says people are resisting, the resistance is a symptom the stem is reporting, not the problem the question is asking you to solve. In one bank question where an organization moves from predictive to agile and team members are resisting, the keyed answer is to get leadership behind the change, and the distractor that presses ahead because it is a strategic company decision treats the resistance as noise, while the one that abandons the transition surrenders it. Neither addresses resistance directly, and neither is right.
The person who owns the thing that changed. This is the most reliable single rule in the slice, and the bank's option pattern is unusually clean about it.
| Option shape | Times offered | Times keyed |
|---|---|---|
| Escalate to a sponsor, senior management or a steering group | 7 | 0 |
| Offer or extend training | 10 | 2 |
| Renegotiate the specific commitment with its owner | 4 | 4 |
| Continue to the current plan and re-plan later | 7 | 1 |
Four for four on renegotiating with the owner, and zero for seven on escalation. The keyed answers in this slice reset the availability targets with operations, get the merger's lead to commit to what the consolidated record must hold and when, and rewrite the role's responsibilities with the audiology line manager. In each case the counterpart is the function that controls the thing that moved, and in each case the project manager goes there directly.
Continuing to the current plan and re-planning once the other change lands is the subtlest distractor of the four, because waiting for clarity feels prudent. It is keyed once out of seven. The reason is timing: by the time the merger date is public or the shortfall shows up as a monthly variance, the project has already spent increments building against an assumption that was never going to hold.
Do I need to know ADKAR or Kotter for the PMP exam? Not as named models, on this bank's evidence. Across 49 questions in this slice, ADKAR appears twice and Kotter twice, and neither is what the question turns on. The task is tested through scenarios where the organization changes around a live project.
Why is more training so often the wrong answer? Training closes a knowledge gap, and most of these scenarios describe a structural one: a target that no longer fits, a role whose accountability changed, a dependency on another part of the organization. Offered 10 times here, keyed twice. Ask what would still be broken after everyone was trained.
When the organization changes under my project, should I escalate? The bank says no. Escalation to a sponsor, senior management or a steering group is offered 7 times across these questions and keyed zero. Go to whoever owns what moved: the line manager, the operations function, the merger lead.
What is the difference between this task and managing change requests? Change requests change the project's baselines through an approval route you control. This task is about changes to the organization around the project, which happen whether the project agrees or not. The work is adapting the project's commitments to them.
Whole-slice patterns like four-for-four on renegotiation and zero-for-seven on escalation are the kind of thing that only shows up across a large, consistently written bank. PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked, so the training distractor teaches you why it loses. Start the free 20-question sample with no card and no signup.
Related: What is actually in the Business Environment domain now · Impediments, issues and the escalation question · Business Environment study guide
Sources: PMI, PMP Exam Content Outline · PMI, standards library
Do I need to know ADKAR or Kotter for the PMP exam?
Not as named models, on the evidence of this bank. Across the 49 questions filed under supporting organizational change, ADKAR is mentioned twice and Kotter twice, and neither is the thing being tested when it does appear. The task is tested through scenarios where the organization changes around a live project, and what is assessed is what the project manager does about the project's commitments, not whether you can recite a model's stages.
Why is more training so often the wrong answer?
Because training solves a knowledge gap, and most of these scenarios describe a structural gap instead: a target that no longer fits the new operating reality, a role whose accountability has changed, or a dependency on another part of the organization. In this bank, an option offering training or an extended training programme appears 10 times in this slice and is keyed twice. Ask what would still be broken after everyone had been trained. If the answer is everything important, training is the distractor.
When the organization changes under my project, should I escalate?
The bank says no, with unusual consistency. An option that escalates to a sponsor, senior management or a steering group appears 7 times across these 49 questions and is keyed zero times. The keyed answers go to the person who actually owns the thing that moved: the line manager who owns the role, the operations function that owns the target, the merger lead who owns the dependency.
What is the difference between this task and managing change requests?
Change requests are about changes to the project's own baselines, flowing through a defined approval route. This task is about changes to the organization the project sits inside, which the project does not control and cannot approve. A reorganization, a merger, a new operating model or a role being redefined by the deliverable itself all happen whether the project agrees or not. The work is adapting the project's commitments to them.