September 8, 2026 · 8 min read
TL;DR: Across this bank, 67 explanations describe the losing option as one that assumes something the scenario never stated. That is the largest single defect class, ahead of skipping a step (30), bypassing a process (24) and acting unilaterally (19). The check is one question: what would have to be true for this option to be right, and did the scenario actually say it?
Most advice about wrong answers describes them as bad project management. That is not what the data shows. The typical distractor in this bank is a perfectly good action, correctly executed, for a situation the candidate has invented.
We counted how the explanations describe the failure across all 1,948 single-answer questions.
| How the explanation describes the wrong option | Count |
|---|---|
| Assumes something not established | 67 |
| Skips a required step | 30 |
| Bypasses a process or a person | 24 |
| Acts unilaterally | 19 |
| Premature | 15 |
| Acts without first establishing something | 7 |
| Treats the symptom rather than the cause | 7 |
The top row is larger than the next three combined. And notice how many of the smaller rows are really the same failure viewed from a different side: skipping a step, acting prematurely and acting without first establishing something all describe a project manager who assumed the earlier step was unnecessary.
An agile team building a hospital rostering tool has made strong progress for four iterations. In the fifth the pace drops sharply and nobody can point to a reason. One wrong option removes a team member. The explanation is direct: removing a team member assumes an underperformer nobody has identified.
Read the option in isolation and it is not absurd. Teams do slow down because of a struggling member, and addressing that is real project management. It is wrong here because the scenario says nobody can point to a reason, which is the exact fact the option needs and does not have.
The pattern repeats with different furniture:
Each of those is competent practice attached to a situation the question never described. That is why they are difficult: nothing about the option itself is objectionable.
Common trap: "This option is something a good project manager would do." That is the wrong test, and it is the test most candidates are actually applying. The right test is whether it is what a good project manager would do given only what this scenario states. In this bank the distractors are written to pass the first test and fail the second, which is why they feel reasonable right up until the explanation names the fact you supplied yourself. This bank names that fact rather than just marking the option wrong.
Inference reads what the scenario implies; assumption supplies what it omitted. The exam requires the first and punishes the second, which is why the line between them matters.
Put the rostering team through both. The pace dropped and nobody can say why, therefore the cause is currently unknown: that conclusion is contained in the words on the page, and it is inference. The pace dropped, therefore someone is underperforming: that conclusion is not on the page at all. You brought it, and it is assumption.
The practical version is a single question you can ask in about four seconds per option: what would have to be true for this to be the right move, and did the scenario say it? If the option proposes training, the scenario must contain a skills gap. If it proposes escalation, the scenario must contain a decision beyond your authority. If it proposes a change request, the scenario must contain an approved baseline being affected. When you cannot point at the sentence that supplies the fact, the option is inventing it.
Because a scenario that withholds the cause has told you what your next move is by withholding it.
The rostering-team question keys the option that works with the team to find the root cause of the slowdown. That is not a generically superior action. It is the right action for a scenario where the cause is stated to be unknown. Change the setup so the scenario names the cause, and investigating becomes the stalling answer while acting on the known cause becomes correct.
This is the deeper reason first-action questions so often key a diagnostic step. The item writer controls exactly how much you are told, and the amount you are told is itself the clue. A scenario rich in symptoms and silent on causes is asking you to establish the cause. A scenario that hands you the cause in the second sentence is asking you what to do about it, and an option proposing to investigate what you have just been told is the distractor.
Read the silences as deliberately as you read the sentences, and most of these questions answer themselves.
What is the most common reason a PMP answer is wrong? An unstated assumption. In this bank, 67 explanations describe the wrong option as one that assumes something the scenario never established, which is more than the counts for skipping a step, bypassing a process and acting unilaterally combined. The option is not bad practice in general. It is bad practice for a situation nobody has confirmed you are in.
How do I spot an assumption in an answer option? Ask what would have to be true for the option to be the right move, then check whether the scenario said it. If the option proposes training, the scenario must have described a skills gap. If it proposes replacing someone, the scenario must have described underperformance. When the required fact is missing, the option is inventing it.
Isn't some inference always necessary? Yes, and that is the line worth learning. Inference reads what the scenario implies, such as concluding that an unexplained drop in team pace has an unknown cause. Assumption supplies a fact the scenario is silent on, such as concluding that the cause is an underperformer. The first is reading; the second is writing.
Does this work on every question type? It works best on scenario questions, which are the bulk of the exam. It does not help on definitional questions asking what something is, where the test is recall rather than situational judgement.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong. Start the free 20-question sample - no card, no signup required to try it.
What is the most common reason a PMP answer is wrong?
An unstated assumption. In this bank, 67 explanations describe the wrong option as one that assumes something the scenario never established, which is more than the counts for skipping a step, bypassing a process and acting unilaterally combined. The option is not bad practice in general. It is bad practice for a situation nobody has confirmed you are in.
How do I spot an assumption in an answer option?
Ask what would have to be true for the option to be the right move, then check whether the scenario said it. If the option proposes training, the scenario must have described a skills gap. If it proposes replacing someone, the scenario must have described underperformance. When the required fact is missing, the option is inventing it.
Isn't some inference always necessary?
Yes, and that is the line worth learning. Inference reads what the scenario implies, such as concluding that an unexplained drop in team pace has an unknown cause. Assumption supplies a fact the scenario is silent on, such as concluding that the cause is an underperformer. The first is reading; the second is writing.
Does this work on every question type?
It works best on scenario questions, which are the bulk of the exam. It does not help on definitional questions asking what something is, where the test is recall rather than situational judgement.