CAPM Practice: Determine how to conduct stakeholder communication

Targeted, role-specific communication prevents information overload. Stakeholders receive what's relevant to them in a format appropriate to their role. Visual summaries and focused decision requests respect their time while ensuring necessary engagement.

**Why not A:** Reducing all communications to quarterly updates would create dangerous information gaps and leave stakeholders unable to make timely decisions. Effective requirements communication requires appropriate frequency based on project pace and stakeholder needs, not an arbitrary reduction that risks disengagement and misalignment.

**Why not C:** Sharing one comprehensive master document with all stakeholders simultaneously ignores the reality that different stakeholders have different information needs. A developer needs detailed technical requirements while an executive needs high-level impact summaries. A single document overwhelms some stakeholders with irrelevant detail while potentially missing what others need.

**Why not D:** Arbitrarily limiting communication to only the five most powerful stakeholders risks excluding stakeholders whose input is critical for requirements accuracy and project success. Influence is not the only criterion for stakeholder engagement — domain expertise, operational impact, and regulatory authority are equally important factors that determine who needs to be informed.