September 7, 2026 · 7 min read
TL;DR: Options phrased as inform, notify, tell or advise the stakeholders are keyed 10 times against 80 as distractors across this bank. The failures are rarely wrong about communicating. They are wrong about sequence: they broadcast before the project manager has anything accurate to broadcast.
Communication is somewhere between 75% and 90% of a project manager's job, depending on which textbook you read, and candidates absorb that number early. Then they carry it into the exam as a tiebreaker, and it costs them.
We counted it. Across the 2,141 questions here, 90 answer options tell, inform, notify or advise stakeholders, the sponsor, the customer or the team. Ten are keyed. The 11% hit rate is not the exam saying communication does not matter. It is the exam testing whether you know what belongs in the message.
Because a message with no analysis behind it transfers anxiety instead of information.
Take one scheduling scenario. A supplier warns that the main fan drive for a wind-tunnel facility may slip by three weeks. One option tells the stakeholders about the possible slip and asks them how the dates should be adjusted. It is a distractor. The keyed answer traces the drive's installation through the critical path and its downstream dependencies to establish whether three weeks moves the project finish at all.
Notice what the distractor actually does. It reports a possible slip whose impact nobody has measured, and then asks the stakeholders to solve a scheduling problem. Both halves are defective, and the second half is worse than the first.
A compliance scenario runs the same way. Counsel flags an export-control restriction that may apply to a product's encryption, and the official interpretation has been requested but not issued. "Inform the stakeholders about the possible legal issue and its implications" is a distractor, because the project manager cannot yet state those implications accurately. The keyed answer gets qualified legal advice first. You cannot brief people on an exposure nobody has sized.
When the fact is already settled and no further analysis will change it.
| Situation | Is the impact known? | Keyed action |
|---|---|---|
| Supplier may slip three weeks | No, depends on float | Trace the critical path first |
| Restriction may apply, ruling pending | No, legal question open | Get legal advice first |
| Sole critical-path resource out two weeks, no cover | Yes, one day slip per day out | Notify stakeholders immediately |
| Change control board has approved a change | Yes, decision made | Update documents, tell stakeholders |
| Handover reveals a defect in the inherited codebase | Yes, defect is confirmed | Tell the client, propose impact analysis |
The dividing line runs straight down the middle column. Where the impact is still a hypothesis, communicating is premature. Where the impact is arithmetic or a decision has already been taken, communicating is the work.
The sick-leave question is the clearest keyed case in the bank. The only person who can do a critical-path task is out for two weeks, there is no alternative resource, and the project slips a day for every day they are away. Fast-tracking, crashing and quietly consuming schedule reserve are all offered. All three are distractors, and the explanation is worth holding on to: a committed date has moved, and the people who agreed that date have to know before anyone chooses a remedy. Absorbing two weeks of reserve in silence hides the exact impact the stakeholders needed to see.
Common trap: the option that tells the stakeholders and asks them what to do. It reads as consultative, so it feels safer than deciding alone. This bank keys against it repeatedly, because asking stakeholders how the dates should be adjusted, how the budget should be rebalanced, or which scope to cut hands them a project management decision dressed up as respect. The bank flags those options by name in the explanation rather than just marking them wrong, which is how you learn the shape instead of the instance. Consultation is real, and it happens after you can present options, not instead of producing them.
Is telling the stakeholders ever the right first answer? Yes, when a committed date or deliverable has already moved and no analysis will change that fact. One bank question has the only critical-path resource go on two weeks of sick leave with no replacement available; notifying the stakeholders immediately is keyed, because the slip is arithmetic, not a hypothesis.
Why do so many "inform the stakeholders" options get marked wrong? Because they arrive before the project manager knows what to say. Across this bank those options are keyed 10 times against 80 as distractors, and most failures put communication ahead of the analysis that would give the message content.
What is wrong with telling stakeholders and asking them how to fix it? It outsources a project management decision under the cover of consultation. One bank question offers "tell the stakeholders about the possible slip and ask them how the dates should be adjusted" as a distractor; the keyed answer traces the dependency through the critical path first to see whether the finish date moves at all.
When a change is approved, do I tell the stakeholders? Yes, and the bank keys it. After a change control board approves a change, the keyed answer updates the project documents and tells the stakeholders. Communication follows the decision here rather than substituting for it.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained rather than just marked wrong, so a premature "inform the stakeholders" tells you which analysis it skipped. Start the free 20-question sample with no card and no signup.
Related: Status Reporting on the PMP Exam: What the Report Is For, and Who It Is For and Diagnose Before You Act: The Answer Shape the PMP Exam Rewards Most. The domain walkthrough is at /study/process.
Is telling the stakeholders ever the right first answer?
Yes, when a committed date or a committed deliverable has already moved and no analysis will change that fact. One bank question has the only critical-path resource go on two weeks of sick leave with no replacement available; notifying the stakeholders immediately is keyed, because the slip is arithmetic, not a hypothesis.
Why do so many 'inform the stakeholders' options get marked wrong?
Because they arrive before the project manager knows what to say. Across this bank those options are keyed 10 times against 80 as distractors, and most failures put communication ahead of the analysis that would give the message content.
What is wrong with telling stakeholders and asking them how to fix it?
It outsources a project management decision under the cover of consultation. One bank question offers 'tell the stakeholders about the possible slip and ask them how the dates should be adjusted' as a distractor; the keyed answer traces the dependency through the critical path first to see whether the finish date moves at all.
When a change is approved, do I tell the stakeholders?
Yes, and the bank keys it. After a change control board approves a change, the keyed answer updates the project documents and tells the stakeholders. Communication follows the decision here rather than substituting for it.