September 8, 2026 · 7 min read
TL;DR: Compromise appears in fourteen options in this bank and is keyed twice. Both keyed cases are recognition questions, where the stem describes a compromise and asks which technique was used. Every time the stem asks what the project manager should do, compromise is a distractor, and one explanation states the reason in a single line: collaborating is win-win, smoothing is lose-win, compromising is lose-lose, forcing is win-lose.
Compromise has better public relations than any other conflict mode. It sounds mature, it sounds fair, and it is what most working project managers actually do most weeks. On this exam it is a trap dressed as a virtue, and the bank sets it fourteen times.
Because of what it leaves behind.
One record puts it plainly. A functional manager argues constantly and is slowing progress, and the sponsor asks for a win-win approach. The four options are the four modes: smooth and accommodate stressing the areas of agreement, collaborate and problem solve with the manager, compromise and meet the manager halfway, force and impose your own viewpoint.
Keyed is collaborate, and the explanation is one sentence: only collaborating and problem solving can produce a win-win; smoothing is lose-win, compromising is lose-lose, and forcing is win-lose.
That is worth memorising as written, because it explains why a technique that works fine on Tuesday afternoon is graded as a failure here. In a compromise both parties give something up, so neither gets what they came for. The disagreement has not been resolved, it has been priced.
| Mode | Outcome | What it does to the underlying issue |
|---|---|---|
| Collaborating / problem solving | Win-win | Resolves it |
| Compromising | Lose-lose | Prices it, leaves it live |
| Smoothing / accommodating | Lose-win | Defers it |
| Forcing / directing | Win-lose | Suppresses it |
| Withdrawing / avoiding | No outcome | Leaves it entirely |
When the question is what happened, not what should happen.
Two subcontractors on a stadium project are deadlocked over which of them absorbs the cost of a redesign, and handover is a week away. The project manager brings them together and they agree to split the cost so work can restart in the morning, leaving the underlying question of fault to be settled afterwards. Which conflict-resolution technique did the project manager use?
Keyed is compromising, against smoothing, forcing and collaborating.
Read the explanation and you can see the exam having it both ways honestly. Compromise searches for a solution that gives every party some degree of satisfaction, each side concedes something, which clears the immediate obstacle but typically produces a temporary rather than a durable resolution. It then rules out collaborating with the clause that matters: collaborating works the problem through to a solution both parties genuinely own, which is exactly the outcome these two deferred.
So the same record that keys compromise also tells you it deferred the real resolution. Naming a technique correctly is not the same as endorsing it.
Common trap: treating fairness as the criterion. In the heritage railway record, two stakeholder groups want materially different things from the same phase, and the explanation notes both positions are reasonable within their own remit. Split the difference by blending elements of both specifications into a single compromise design is offered and rejected. Keyed is bringing both groups together to establish what each requirement is actually protecting, historical authenticity on one side and operational safety on the other, and finding or escalating a resolution before the scope statement is finalised. A blended signal box is even-handed and may satisfy neither remit, which is the specific failure mode compromise carries into technical scope. The bank offers the fair-sounding option by name and its explanation says what the fairness costs, rather than only marking it wrong.
No, and the testing-time record shows why the near-miss matters.
A sharp argument erupts between a lead engineer and a test manager. The engineer says testing eats too much of the schedule; the test manager says the engineer rushes the code and creates quality problems. Facilitate a discussion between the two to reach a compromise on the testing time is offered. Keyed is hold separate one-on-one meetings with each of them to understand the underlying concerns before attempting a resolution.
The explanation names the flaw twice over. First, both people have stated positions rather than interests, and testing takes too long and the code arrives half-finished are almost certainly the same underlying tension about when quality is built in. Second, it says the joint discussion is the right second step but the wrong first one, and points at what the distractor is aimed at: a compromise on testing time.
Splitting testing time down the middle resolves a number. It does not touch the question of when quality gets built in, which is the thing both of them are actually arguing about.
Once, and it is instructive rather than contradictory.
A sponsor who controls funding and scope has heard the team's concern, considered it, and directed that the project proceed exactly as it stands. Keyed there is accommodate the sponsor to preserve harmony and goodwill, with compromise, forcing and problem-solving all rejected.
That is not the ranking failing. It is the ranking applied after collaboration has already happened. The explanation says so directly: the project manager took the concern to the sponsor and set out the case, which is the collaborative move, and it has been made. What remains is a decision about how to respond to a legitimate ruling by the person entitled to make it.
Compromise is rejected there for the usual reason and one extra. There is nothing to split, because the authority to decide scope sits entirely on one side of the table.
Why is compromise wrong on the PMP exam when it works in real life? Because the exam grades on durability, not on speed. The bank states the ranking outright in one explanation: collaborating produces win-win, smoothing is lose-win, compromising is lose-lose, and forcing is win-lose. A compromise clears the immediate obstacle while leaving the underlying disagreement unresolved, so the same conflict returns.
When is compromising the keyed answer? When the stem describes a compromise and asks you to name the technique. The bank keys compromising for two subcontractors who agree to split the cost of a redesign so work can restart, leaving fault to be settled afterwards. The keyed answer identifies what was done; it does not endorse it as the best available move.
What is keyed instead when the stem asks what to do? Collaborating, or the step that makes collaboration possible. The bank keys collaborate and problem solve with the manager when a sponsor asks for a win-win approach, and it keys separate one-on-one meetings before a joint discussion when two people have stated positions rather than interests.
Is splitting the difference ever acceptable in a scope disagreement? Not in this bank. When a heritage trust and an operating partner want materially different things from the same phase, blending both specifications into a single compromise design is offered and rejected. The keyed answer establishes what each requirement is actually protecting, because a blended design may protect neither.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained, not just marked wrong. Start the free 20-question sample and see how often the reasonable-sounding middle is the option the explanation dismantles. No card, no signup required to try it.
Why is compromise wrong on the PMP exam when it works in real life?
Because the exam grades on durability, not on speed. The bank states the ranking outright in one explanation: collaborating produces win-win, smoothing is lose-win, compromising is lose-lose, and forcing is win-lose. A compromise clears the immediate obstacle while leaving the underlying disagreement unresolved, so the same conflict returns.
When is compromising the keyed answer?
When the stem describes a compromise and asks you to name the technique. The bank keys compromising for two subcontractors who agree to split the cost of a redesign so work can restart, leaving fault to be settled afterwards. The keyed answer identifies what was done; it does not endorse it as the best available move.
What is keyed instead when the stem asks what to do?
Collaborating, or the step that makes collaboration possible. The bank keys collaborate and problem solve with the manager when a sponsor asks for a win-win approach, and it keys separate one-on-one meetings before a joint discussion when two people have stated positions rather than interests.
Is splitting the difference ever acceptable in a scope disagreement?
Not in this bank. When a heritage trust and an operating partner want materially different things from the same phase, blending both specifications into a single compromise design is offered and rejected. The keyed answer establishes what each requirement is actually protecting, because a blended design may protect neither.