CAPM Practice: Determine how to conduct stakeholder communication

Visual models (process diagrams, wireframes, data models) make abstract requirements concrete and comprehensible. They reduce ambiguity, spark productive discussion, and help stakeholders visualize the solution — often surfacing issues that text descriptions would miss.

**Why not B:** PMI does not require visual models for all project requirement deliverables. Visual models are a best practice chosen based on project needs and audience, not a mandatory standard. The decision to use visuals depends on context, complexity, and stakeholder preferences.

**Why not C:** Visual communication tools benefit all stakeholders, not just technical ones. Business stakeholders, executives, and end users often gain more from wireframes and diagrams than from dense text specifications. Visuals bridge communication gaps across diverse audience types.

**Why not D:** Visuals complement rather than replace written requirements documentation. While visuals excel at conveying concepts quickly, written documentation provides necessary detail, precision, and a formal record. Both formats serve important and complementary purposes.