PMP · Question #1399
A project manager who is new to a matrix organization has just been assigned to an internal software development project that is intended to reduce conflicts in the company's internal tracking…
The correct answer is A. Set up an intranet site and allow stakeholders to access the relevant project information. For an internal software development project benefiting over 1,000 people in a matrix organization, the most effective way for the project manager to communicate progress is by setting up an intranet site where stakeholders can access relevant project information.
Question
A project manager who is new to a matrix organization has just been assigned to an internal software development project that is intended to reduce conflicts in the company's internal tracking system. With over 1,000 people in the company who will benefit from the software, the project manager wants to ensure everyone is aware of the great progress the team is making. The project manager meets with the project team to decide upon the most effective way to communicate progress. What should the project manager do?
Options
- ASet up an intranet site and allow stakeholders to access the relevant project information
- BDivide up the organization among the project team to provide direct project updates
- CAsk the project sponsor to disseminate project progress across the organization's stakeholders.
- DSend weekly emails to each stakeholder providing them with the project's progress
How the community answered
(54 responses)- A74% (40)
- B6% (3)
- C17% (9)
- D4% (2)
Why each option
For an internal software development project benefiting over 1,000 people in a matrix organization, the most effective way for the project manager to communicate progress is by setting up an intranet site where stakeholders can access relevant project information.
An intranet site serves as a centralized, accessible repository for project information, allowing over 1,000 stakeholders to self-serve updates on their own schedule. This is highly efficient for broad communication in a large organization, ensuring consistency and reducing the burden of individual communication efforts.
Dividing the organization among the project team for direct updates is highly inefficient, resource-intensive, and prone to inconsistencies for a large number of stakeholders (over 1,000).
Asking the project sponsor to disseminate progress offloads a key project management responsibility and may result in infrequent, filtered, or delayed communication, which is not ideal for ensuring everyone is aware of 'great progress.'
Sending weekly emails to each of over 1,000 stakeholders would be overwhelming, create email fatigue, and is not a sustainable or effective method for broad communication when a centralized information source is available.
Concept tested: Communication management, large-scale information distribution
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
7Correct answer is A. Per the PMBOK Guide, the Manage Communications process calls for selecting methods appropriate to the audience size and information needs. With over 1,000 stakeholders, pull-based communication via an intranet site is the efficient choice because it lets interested parties self-serve updates without flooding inboxes or burning team capacity. D is push communication at scale and becomes noise, B is a poor use of project team hours, and C hands off a responsibility that belongs to the project manager.
A is correct, because 1,000 stakeholders means PULL communication. Big crowd, let them grab info from the intranet.
Agree on A for the large audience, but worth noting that push communication still applies for critical updates that all 1,000 stakeholders must receive, so the exam might hinge on whether the question says "must receive" versus "can access."
Confirmed A on exam last week. D is tempting but 1000 emails is not effective.
Agreed on A, and in practice that volume would also blow past retention policies and get your sender domain flagged before anyone even saw the alert.
Going with B here. In a matrix org you have zero functional authority over those 1,000 plus people, so getting your team members to deliver updates directly through their own functional channels builds the relationships and buy-in you will need when crunch time hits. I have seen email blasts and intranet sites get ignored by exactly the stakeholders you need support from, whereas a face-to-face or direct conversation actually moves the needle.
Got to go with A on this one Samuel. When you are coordinating updates for a crowd of 1,000 plus people across a matrix structure, pushing info through each person's functional channel is a logistical nightmare, whereas a single shared intranet site or mailing list gives everyone one consistent source of truth. Remember my matrix megaphone mnemonic: Many Attendees need Mass communication, not Mouth-to-mouth.