PMP · Question #1303
A project manager has just taken over a project that is in the requirements gathering phase. A stakeholder indicates that they have not received any progress updates even though reports have been sent
The correct answer is C. Assess all of the project stakeholders and document their preferred communication method and. To resolve communication issues where stakeholders aren't receiving updates, the project manager must assess all stakeholders and document their preferred communication methods and frequency.
Question
A project manager has just taken over a project that is in the requirements gathering phase. A stakeholder indicates that they have not received any progress updates even though reports have been sent on a weekly basis. What should the project manager do to ensure all stakeholders are receiving proper information about the project?
Options
- AHold a steering committee meeting with all stakeholders to provide a comprehensive update on
- BCreate daily progress reports and send them to all stakeholders.
- CAssess all of the project stakeholders and document their preferred communication method and
- DInclude stakeholders in the weekly status meetings with the team.
How the community answered
(26 responses)- A15% (4)
- B12% (3)
- C69% (18)
- D4% (1)
Why each option
To resolve communication issues where stakeholders aren't receiving updates, the project manager must assess all stakeholders and document their preferred communication methods and frequency.
Holding a steering committee meeting is one communication method, but it does not address the fundamental need to understand and adapt to the diverse communication preferences of all stakeholders.
Creating daily progress reports for all stakeholders is likely to lead to information overload and is an inefficient, unsustainable solution that doesn't target specific communication needs.
Effective communication requires understanding stakeholder preferences. By assessing and documenting each stakeholder's preferred method (e.g., email, formal reports, meetings) and frequency, the project manager can tailor the communication strategy to ensure information is received and understood, thereby addressing the root cause of the issue.
Including stakeholders in weekly status meetings is a specific tactic that might work for some, but it's not a comprehensive approach to address the varied communication preferences of all project stakeholders.
Concept tested: Project stakeholder communication planning
Source: https://www.pmi.org/pmbok-guide-standards/foundations/pmi-lexicon#project-communications-management
Topics
Community Discussion
5C is correct. Reports are going out but not landing, which means the communication requirements analysis is out of date. You need to revisit the stakeholder register and document preferred communication methods and frequency for each person before sending anything else.
Agreed on C, and one of the seniors on my team pointed out that once you update the register you should also loop back with stakeholders to confirm the changes rather than just silently switching channels on them.
C showed up almost word for word on my exam last month and I almost picked A because it sounded proactive, but my mentor told me the PMI mindset is always to assess stakeholders and their communication preferences first before doing anything else. The part about reports already being sent weekly is the clue that the method itself is the problem, not the frequency.
A is the right move here because the underlying problem is not a lack of reporting, it is a disconnect between what is being sent and what stakeholders actually need or are looking for. A steering committee meeting gets everyone in the same room, surfaces the gap directly, and gives the PM a chance to reset expectations on how updates will flow going forward. C sounds tempting as a process step, but it is reactive paperwork that does not address the immediate trust issue this stakeholder is signaling. You fix communication breakdowns with direct engagement first, then document the plan.
Actually it is C, and the reason a senior gave me is that when a stakeholder says your reports are not useful, the first move is to review and adjust the communication plan itself, not schedule a meeting. The plan is where you define format, frequency, and content expectations, so fixing it there is what actually prevents the gap from recurring.