CAPM Practice: Determine how to conduct stakeholder communication

Effective BA communication is audience-aware. Business stakeholders need business language, user stories, and process models. Technical teams need precise specifications, data models, and interface definitions. Tailoring prevents miscommunication.

**Why not B:** The length or detail of a requirements document is not the defining difference between business and technical communication — the type of information and vocabulary used is what matters. A brief user story with detailed acceptance criteria may be more useful to a technical team than a long narrative document, and business stakeholders often need concise summaries rather than exhaustive detail.

**Why not C:** Using identical communication formats for both audiences is a common BA anti-pattern. Business stakeholders risk confusion when presented with data flow diagrams and API specifications, while technical teams may lack the information precision they need if given only high-level business narratives. Tailoring communication to the audience is a fundamental BA competency.

**Why not D:** Technical team members require clear, precise requirements communication to design and build solutions correctly. Withholding requirements communication and relying solely on code repositories would lead to misaligned implementations, rework, and a failure to deliver business value. BAs serve as the bridge between business needs and technical delivery.