September 7, 2026 · 6 min read
TL;DR: "Speak to them privately" appears 40 times across the bank's answer options, keyed 21 times and offered as a distractor 19. That near-even split makes it one of the least reliable reflexes on the exam. The rule that separates the two: private is right when one named person has a problem nobody has diagnosed yet. It is wrong when the issue is technical, already public, or the whole team's.
Most PMP answer shapes lean hard one way. Escalating to the sponsor is nearly always wrong. Diagnosing before acting is nearly always right. The private conversation is neither. It sits at 21 keyed against 19 distractors, which means a candidate who has learned "always take them aside" and a candidate who has learned "that is the soft option" will each be wrong about half the time.
Every keyed instance shares a shape. There is one identifiable person, something about their behaviour or output has changed, and nobody yet knows why.
A team member misses their agreed indicators for three reporting periods while everyone else meets theirs. The keyed answer is to discuss the shortfall privately with that person to understand what lies behind it. The distractors include surveying the whole team, which investigates a problem the team does not have and quietly exposes the individual to their colleagues.
Another: a member privately asks to be taken off a workstream, citing "personal preference," and the project manager has already noticed they stopped pairing with a colleague they used to work with often. Keyed answer is to speak with them privately and find out what actually changed. "Personal preference" is what they chose to say, not necessarily what is happening.
A third: one person dominates the daily scrum, others have gone quiet. Keyed answer is a private conversation about how the conduct affects the team. The explanation is specific about why private matters here, and it is not tact. It lets the person hear it without losing face, and it establishes whether the dominance is deliberate or simply unnoticed, which changes what happens next and which the project manager cannot know in advance.
So the keyed pattern is not "be kind." It is closer to "you are missing information that only this one person has."
Three situations flip it, and the bank uses all three.
| Situation in the stem | Why private fails | What the bank keys instead |
|---|---|---|
| The disagreement is technical and already public | Hides a decision the whole team must build against | Bring the tradeoffs to a full team discussion |
| The ambiguity affects everyone, one person just noticed | Fixes it for one person, leaves it in place for the rest | A working session that clarifies and records it |
| The behaviour is a group dynamic, not an individual's | Handles symptoms one at a time, changes nothing | Set ground rules and model the behaviour yourself |
The clearest of the three: two senior engineers disagree publicly about an architectural approach, other engineers are taking sides, and design work is stalled. Meeting each one privately is offered, and it is wrong. The dispute is technical and everyone will build against the outcome, so the resolution has to happen where those people can see it reasoned through.
The second is subtler. A team member tells the project manager privately that they are unsure which parts of the interface testing are theirs and which belong to the vendor. Coaching that person privately is offered. The keyed answer is a working session that clarifies the responsibilities and records them where the team can see them, because the boundary was never made explicit for anyone. One person raised it. Everyone has it.
Common trap: treating "someone came to you privately" as a signal that the answer is also private. It is not. In the vendor-testing item the private report is how the project manager learned about a gap that affects the whole team, and the bank offers private coaching as the distractor precisely because it resolves the conversation without resolving the ambiguity. Ask what the problem belongs to, not how you heard about it.
Worth knowing as a hard rule rather than a lean. Anonymous feedback systems and anonymous peer surveys appear six times across the bank's options and are keyed zero times.
When a person's conduct is affecting the team, an anonymous system denies them any chance to respond and rarely changes behaviour. When junior engineers go quiet in design reviews, collecting their input privately and raising it anonymously later is offered, and the keyed answer is instead to set ground rules that invite questions and to model constructive disagreement yourself. Anonymity manages the symptom of a room where people cannot speak. It does not make the room safe.
That zero is one of the cleaner signals in the bank, and it is the kind of thing you only see by counting rather than by remembering how questions felt. It is also why every wrong answer in this bank carries an explanation of what it was doing there.
When is a one-on-one the keyed answer on the PMP exam? When the situation involves one identified person, the cause of their behaviour or shortfall is unknown, and finding out requires asking them. Across the bank's 40 private-conversation options, that pattern accounts for almost every keyed one.
When is taking someone aside the wrong answer? When the problem is technical, already public, or shared by the whole team. A private chat about a public architectural disagreement hides a decision the team needs to see reasoned through, and the bank keys the open discussion instead.
Is an anonymous channel ever the right answer? Not in this bank. Anonymous feedback systems and anonymous peer surveys appear six times as options and are keyed zero times, because they deny the person any chance to respond.
Does "first" in the question change the answer? Often. Several items key the private conversation specifically as a first step, with the reassignment or the development plan following it. If a stem asks what to do first and one option gathers the missing information from the person who has it, that ordering usually decides the item.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong, which is how patterns like this one become visible in the first place. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Removing the Difficult Team Member: 0 Keyed, 17 Distractors and Calling HR: 1 Keyed Answer, 19 Distractors. The People domain tasks these sit under are set out on the People domain study page.
When is a one-on-one the keyed answer on the PMP exam?
When the situation involves one identified person, the cause of their behaviour or shortfall is unknown, and finding out requires asking them. Across the bank's 40 private-conversation options, that pattern accounts for almost every keyed one.
When is taking someone aside the wrong answer?
When the problem is technical, already public, or shared by the whole team. A private chat about a public architectural disagreement hides a decision the team needs to see reasoned through, and the bank keys the open discussion instead.
Is an anonymous channel ever the right answer?
Not in this bank. Anonymous feedback systems and anonymous peer surveys appear six times as options and are keyed zero times, because they deny the person any chance to respond.