Stakeholder Communication for Business Analysis

A business analyst sits between multiple groups — business stakeholders who hold the requirements, and delivery teams who have to build against them — which makes choosing the right communication channel for the right audience a core, tested skill. A detailed written report suits a stakeholder who needs to review specifics at their own pace; a live presentation suits a group decision or a moment that needs discussion and buy-in; a quick message suits a simple status update that doesn't need either.

Because requirements pass through the BA on their way from business language to technical specification, a breakdown in that communication doesn't just slow the BA down — it propagates into whatever the delivery team builds. A requirement the BA mis-communicated to developers becomes a wrong feature that nobody technically got "wrong" at their own step.

Study focus: expect a scenario where a BA chooses a clearly mismatched channel for the situation (e.g., a one-line message to communicate a major requirements change affecting five teams) and asks what should have been used instead.