September 7, 2026 · 7 min read
TL;DR: Across this bank, answer options that remove, replace, reassign, dismiss, or escalate a team member to HR appear 17 times and are keyed zero times. That is not a tendency, it is an absolute in 2,141 questions. What replaces it is nearly always the same move: a private conversation with the individual to find out what is actually going on.
There is a version of the PMP exam that lives in candidates' heads where the project manager is a resource allocator. Someone is not performing, so you swap them out and protect the schedule. It is what a lot of real organisations reward. It is also, measurably, never the keyed answer here.
We counted the pattern across every option in the bank. Seventeen answer choices offer some form of getting rid of the problem person: take them off the project, reassign their tasks to others, ask the functional managers to replace them, escalate to HR for disciplinary action, remove the people slowing the project from the team. None of the seventeen is correct.
Because removal is a remedy chosen before anyone has established the cause, and the exam consistently keys the diagnosis instead.
Take the clearest case. A team member is repeatedly late to meetings, talks over others, and turns in work past deadline. Morale is dropping, and other members have started calling out their performance in meetings and asked the project manager to step in. The situation is about as provoked as it gets. The four options are: address it privately with the individual, raise the behaviour at the next team meeting, document it and escalate to HR for disciplinary action, or reassign the person's tasks to others.
The keyed answer is the private one-on-one. The other three are all things a stressed project manager actually does, and all three skip the same step. Nobody has asked why. The lateness could be a second project nobody told you about, a capability gap the person is embarrassed about, or a genuine attitude problem, and the correct response differs in each case. You cannot pick the response before you know which one you have.
The same shape recurs with the roles reversed. An experienced team member tells the project manager privately that a new hire "doesn't seem to have the skills for this role" and suggests reassigning their tasks. The project manager has not yet seen the new hire's work. Two of the distractors act on that report immediately: reassign the tasks as suggested, or release the new hire and request a replacement through HR. The keyed answer observes the new hire's actual work and checks it against the role's expectations first. What the project manager has is one colleague's secondhand impression, which may be wrong, may be incomplete, or may itself be a symptom of friction between the two of them.
Common trap: "The team asked me to deal with this person, so dealing with them is what the exam wants." It wants you to deal with the situation, which is not the same thing. In the bank scenario above, the team explicitly asks the project manager to step in, and reassigning the problem member's tasks is still a distractor. Peer pressure to act does not change what the correct first act is. This bank puts the socially satisfying option in front of you on purpose, and explains why it fails rather than just marking it wrong.
The replacement is not a single technique, it is a ladder. Diagnose first, then respond in proportion, and keep the response with the individual rather than broadcasting it.
| Situation in the stem | Keyed response | Common distractor beside it |
|---|---|---|
| One person's behaviour is disrupting the team | Private one-on-one to establish the cause | Raise it at the next team meeting; escalate to HR |
| An engineer's output falls short of project standards | One-on-one to discuss the issues and a development plan | Formal performance improvement plan through HR; team-wide meeting about standards |
| Output has fallen and the cause traces to one person's unfamiliar tech stack | Pair them with someone experienced, or reassign those specific tasks | Team-building session; more retrospectives |
| Some members declining, others strong, cause unknown | Investigate the causes and gather systematic feedback | Discuss the weak members' performance openly in a team meeting; competitive bonus for the top 20% |
| Juniors stuck on a hard problem and reluctant to speak up | Pair-programming plus individual coaching chats | Move the hard tasks to the seniors and give juniors easier work |
Two things in that table are worth pulling out.
First, the escalation options are wrong in both directions. Escalating up to HR is a distractor, and so is escalating sideways into a public forum. A team-wide meeting about standards after one engineer's work fell short, or a group email stressing the importance of standards without naming anyone, both take an individual matter and make it everyone's. Performance concerns about one person go to that person, in private.
Second, reassignment is not banned outright, it is banned as a substitute for diagnosis. There is a bank scenario where reassigning the tasks is keyed: output dropped, the investigation already traced it to one member handed a technology stack they have never used, and the rest of the team is unaffected and on pace. The keyed answer pairs that member with someone experienced in the stack or moves those specific tasks. The cause is known and the action fits it. Compare that with reassigning a developer's tasks to the rest of the team without adjusting the sprint scope, which is a distractor, because it just relocates the work and hopes.
The underlying doctrine is not subtle once you see it. Under the 2026 ECO, leading the project team and supporting team performance are the project manager's job. A project manager who removes a struggling member has not led them. In one bank question about a multinational team struggling to hit its deliverables, asking the functional managers to replace the team members sits alongside blanket HR-run training, and the keyed answer is to support the team so they can solve their own problems.
Can removing a team member ever be the right PMP exam answer? Not in this bank. Across 2,141 questions, options that remove, replace, reassign, dismiss, or escalate a team member to HR appear 17 times as answer choices and are keyed zero times. The exam treats the project manager as the person responsible for developing the team, not for triaging it.
What should I pick instead when a team member is underperforming? A private one-on-one with that individual to establish the cause. That is the keyed answer in multiple bank scenarios. Once the cause is known, the response follows it: pairing for a skill gap, coaching for confidence, a development plan for a standards gap.
Why is escalating to HR a distractor rather than due process? Because it converts a management conversation into a disciplinary one before anyone has established what is wrong. In the bank scenario where a colleague reports that a new hire seems to lack the skills, the project manager has not yet observed the work. Releasing them through HR acts on a secondhand impression.
Is reassigning tasks different from removing the person? The exam scores them the same way when the reassignment is a substitute for diagnosis. Reassigning a struggling member's tasks to someone stronger appears repeatedly as a distractor. It becomes acceptable only once the cause is known and the reassignment is the targeted fix, such as pairing someone with an expert to close a specific technology gap.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, and every wrong answer is explained, not just marked wrong, so you learn why the swap-them-out option was written into the question at all. Start the free 20-question sample. No card, no signup required to try it.
Related reading: Leading the Project Team covers the broader set of leadership answers this pattern sits inside, and The Functional Manager: The Person the Exam Keeps Offering as the Wrong Answer covers the sideways-escalation version of the same mistake. The People domain study guide maps these to the 2026 ECO tasks.
Source: PMI, PMP Examination Content Outline.
Can removing a team member ever be the right PMP exam answer?
Not in this bank. Across 2,141 questions, options that remove, replace, reassign, dismiss, or escalate a team member to HR appear 17 times as answer choices and are keyed zero times. The exam treats the project manager as the person responsible for developing the team, not for triaging it.
What should I pick instead when a team member is underperforming?
A private one-on-one with that individual to establish the cause. That is the keyed answer in multiple bank scenarios. Once the cause is known, the response follows it: pairing for a skill gap, coaching for confidence, a development plan for a standards gap.
Why is escalating to HR a distractor rather than due process?
Because it converts a management conversation into a disciplinary one before anyone has established what is wrong. In the bank scenario where a colleague reports that a new hire seems to lack the skills, the project manager has not yet observed the work. Releasing them through HR acts on a secondhand impression.
Is reassigning tasks different from removing the person?
The exam scores them the same way when the reassignment is a substitute for diagnosis. Reassigning a struggling member's tasks to someone stronger appears repeatedly as a distractor. It becomes acceptable only once the cause is known and the reassignment is the targeted fix, such as pairing someone with an expert to close a specific technology gap.