PMP Practice: Confirm communication is understood and feedback is received

The project manager should tailor communication methods, channels, frequency, and detail levels to match each stakeholder group's legitimate information needs and decision-making authority. The VP of Operations needs assurance after recent issues but likely doesn't need daily technical details. Operations managers need implementation specifics for their sites but weekly may suffice. The executive sponsor's concern about alarming the board is valid for strategic-level communications. By segmenting communications appropriately—perhaps providing the VP with weekly summaries with escalation triggers for critical issues, maintaining operational calls with site managers, and preserving monthly executive dashboards—Joaquín addresses all needs without overburdening the team or creating unnecessary alarm. The scenario establishes that issues are resolved and the project is on track, which eliminates the urgency for daily detailed reporting to executives. The 18-hour weekly reporting burden and the sponsor's explicit concern about board alarm are closing facts that make tailored communication the clearly superior approach over uniform increases in frequency or rigid adherence to the original plan.

**Why not B:** Implementing daily detailed reports to all stakeholders would dramatically increase the team's reporting burden beyond the already substantial 18 hours per week, divert resources from actual project work, and directly conflict with the executive sponsor's stated concern about creating unnecessary alarm among board members. While being responsive to senior leadership is important, the scenario establishes that the integration issues were resolved and the project remains on track, which means daily detailed reporting represents over-communication rather than appropriate transparency. Effective communication management matches the level of detail and frequency to the stakeholder's role and decision-making needs, not simply to their initial request.

**Why not C:** While following approved plans and change control procedures is generally good practice, rigidly maintaining the current plan when multiple stakeholder groups have identified gaps in their information needs represents inflexibility rather than effective stakeholder management. Communications management plans should be living documents that adapt to legitimate stakeholder needs, especially when the current approach is demonstrably causing dissatisfaction across multiple groups with different authority levels. The scenario doesn't indicate the current plan is meeting project needs—in fact, three different stakeholder groups are requesting changes, suggesting the plan requires adjustment. Additionally, communication adjustments typically don't require formal change requests unless they affect scope, schedule, budget, or contractual obligations.

**Why not D:** Attempting to achieve consensus on a single communication frequency and format across stakeholder groups with fundamentally different roles, information needs, and authority levels is unlikely to succeed and represents a misunderstanding of effective communications management. The VP of Operations needs different information at different frequencies than the executive sponsor, and operations managers have site-specific implementation concerns that aren't relevant to executives. Forcing all stakeholders into a one-size-fits-all communication approach either under-serves some groups or over-communicates to others. The scenario's closing fact that the executive sponsor explicitly wants to avoid alarming board members makes a uniform approach across all levels particularly inappropriate.