September 7, 2026 · 8 min read
TL;DR: Options that run a workshop, facilitate a session or bring two parties together are keyed 25 times and used as distractors 27 times across 47 questions in this bank. That near-even split is unusual, and it makes the discriminator worth learning. The session keys when the people in the room hold what the decision needs. It fails when nobody has diagnosed the disagreement yet, or when the decision needs authority nobody attending has.
Most answer archetypes in this bank lean hard one way. Escalation is mostly wrong. Waiting is almost always wrong. Diagnosis is mostly right. Learn the lean and you can play the odds when a question is hard.
Getting people in a room does not work like that. Twenty-five keyed, 27 distractors, across 47 questions, 38 of them People domain. A candidate who has absorbed "collaboration is the PMI answer" will pick it into 27 wrong answers, and a candidate who has learned to distrust soft options will miss 25 right ones. This is one of the few archetypes where you have to actually read the stem.
When the misunderstanding lives between the two parties, and both of them can act on it.
Two senior specialists disagree over a technical approach and the disagreement is slowing the work. The stem tells you the project manager has authority to decide the matter and has not yet tried anything else. One option imposes a decision now, on the grounds that early delay costs more than either objection. Another asks each specialist to write up their position so the stronger argument can be judged on paper. A third separates them onto different parts of the work so the disagreement need not be settled at all.
The keyed answer brings the two specialists together to work through their reasoning and reach a solution they both accept, before considering a unilateral decision. PMBOK 8 treats the power-position move as what you reach for after collaboration has been tried and failed, not as a first resort, because it produces a win-lose outcome that neither party owns. Nothing has been attempted here yet.
The pattern repeats at organizational scale. A parks agency has a regional operations board and a central asset committee each issuing a different refurbishment sequence to the same contractor, both having proceeded for weeks believing the sequence was theirs to set. The keyed answer brings both bodies together with the sponsor to establish which decisions each of them holds. Publishing a decision-rights matrix in the plan documents a resolution that has not happened. Following whichever body has the larger budget picks a winner without asking whether it should have won.
Two situations, and both are recognisable from the stem.
The disagreement has not been diagnosed. A transit hub project has a municipal council and several rider-advocacy groups unable to agree on which passenger amenities belong in the concept. One option runs a facilitated workshop to collect input from every stakeholder group. It is wrong. The keyed answer identifies the root cause of why they cannot agree.
The disagreement is a symptom, and the remedy depends entirely on what is under it: objectives nobody made explicit, a budget nobody stated, competing political mandates, or a genuine conflict of values. Each points somewhere different. A workshop convened before you know which one you have is a room full of people restating positions.
The decision needs authority nobody in the room holds. On a wind-farm project, the design team and the environmental consultants have already run a joint session and agree on the best turbine placement. Implementing it needs a longer access road than the budget allows, and neither group can approve additional funding. One option asks the two groups to run another joint session until a cheaper option emerges.
Keyed instead: take the agreed placement and its funding gap to the sponsor, with the cost and the reasoning, for a funding decision. The technical conflict is already resolved. What remains is a funding decision, and reconvening the same two groups asks people without budget authority to solve a budget problem.
| What the stem shows | Workshop keyed? | What the exam wants instead |
|---|---|---|
| Two parties, each holding half the picture | Yes | Put them together so both halves surface |
| Norms or expectations that were never made explicit | Yes | A session where each side states how it works |
| Nobody knows why the parties disagree | No | Establish the cause first |
| The blocker is funding or authority | No | Take it to whoever can decide |
| The disagreement is already resolved | No | Act on the agreement |
| One side has a real technical problem | Sometimes | Check whether the tension is causing the defects |
The near-misses are the most instructive cases, because the workshop option is genuinely attractive in them.
A high-stakes software project has unexpected defects and team miscommunication causing delays, with a worried sponsor. One option hosts a problem-solving workshop where the team collaboratively identifies solutions to the technical issues. That is a reasonable thing to do. It is still the distractor.
The keyed answer runs team-building events focused on collaboration and open communication, because the two symptoms are not independent. Defects on this kind of project are produced at the seams, in assumptions not shared and interfaces each side understood differently, so a team that is miscommunicating will keep generating defects. Solve the technical issues in a workshop and you have cleared this batch of defects with the generator still running.
Common trap: treating "collaborative" as a synonym for "correct." Facilitation is a technique with preconditions, and this bank tests the preconditions rather than the technique. Before picking a session, ask two questions of the stem: does anyone know yet what the disagreement is actually about, and can the people being convened decide the thing that needs deciding? If either answer is no, the workshop is the trap, and one of the other three options is doing the work.
Is running a workshop usually the right answer on the PMP exam? It is close to a coin flip, which is what makes it worth studying. Options that run a workshop, facilitate a session or bring two parties together are keyed 25 times and used as distractors 27 times across 47 questions in this bank, 38 of them in the People domain.
When is bringing people together the keyed answer? When the people in the room hold the information the decision needs and have the standing to settle it. Two specialists disagreeing on a technical approach, two teams whose communication norms differ, two governing bodies each believing a sequence is theirs to set: in every case the misunderstanding lives between the parties.
When is a workshop a distractor? In two situations. First, when nobody has established what is driving the disagreement, so the session would work on a symptom. Second, when the decision requires authority nobody attending holds, such as funding approval, in which case the meeting produces agreement that changes nothing.
Does this mean facilitation is a weak technique? No. Collaboration is PMBOK 8's preferred route to a conflict outcome both parties own, and the exam keys it as a first resort over imposing a decision. The 27 distractor appearances are failures of timing and of who was invited, not failures of the technique.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 exam content outline, and every wrong answer is explained rather than just marked wrong, which is the only way an archetype this evenly split becomes learnable. Start the free 20-question sample — no card, no signup required to try it.
Is running a workshop usually the right answer on the PMP exam?
It is close to a coin flip, which is what makes it worth studying. Options that run a workshop, facilitate a session or bring two parties together are keyed 25 times and used as distractors 27 times across 47 questions in this bank, 38 of them in the People domain. Neither a bias toward it nor against it will serve you.
When is bringing people together the keyed answer?
When the people in the room hold the information the decision needs and have the standing to settle it. Two specialists disagreeing on a technical approach, two teams whose communication norms differ, two governing bodies each believing a sequence is theirs to set: in every case the misunderstanding lives between the parties, so putting them together is what resolves it.
When is a workshop a distractor?
In two situations. First, when nobody has established what is actually driving the disagreement, so the session would work on a symptom. Second, when the decision requires authority nobody attending holds, such as funding approval, in which case the meeting produces agreement that changes nothing.
Does this mean facilitation is a weak technique?
No. Collaboration is PMBOK 8's preferred route to a conflict outcome both parties own, and the exam keys it as a first resort over imposing a decision. The 27 distractor appearances are not failures of facilitation as a technique, they are failures of timing and of who was invited.