3.2. Stakeholder Communication

💡 First Principle: The right communication channel isn't a matter of preference — it's a match between the message's purpose (informing, persuading, negotiating) and the audience's needs (detail level, formality, urgency). Picking a channel that doesn't fit the purpose is a common wrong-answer pattern.

Why communication is a distinct BA skill. A BA sits between multiple groups — business stakeholders, the project team, sometimes external parties — who don't naturally speak the same vocabulary. Translating a business need into a requirement a development team can act on, and translating technical constraints back into terms a business stakeholder can evaluate, is core BA work, not a side skill.

⚠️ Exam Trap: "More communication" is not automatically the correct answer. A scenario describing stakeholders overwhelmed by excessive status updates is testing whether you'll recognize that the right channel and frequency matter more than sheer volume.

A worked example. A scenario describes a BA who needs to explain a technical database constraint to a non-technical executive sponsor who is asking why a requested feature will take three extra weeks. Sending the executive the technical design document is a mismatch — correct information, wrong translation. The BA's job is to reframe the constraint in terms the sponsor can act on ("the data structure we have today can't support this without a rebuild, which is the source of the three weeks") delivered through a short conversation or brief presentation, not a document dump. This translation step — same underlying fact, reframed for the audience — is what "communication is a distinct BA skill" means in practice, not just picking a channel from a list.

Internal versus external formality. A quick message to a teammate down the hall and a formal letter to an external regulatory contact aren't interchangeable in tone, even when the underlying content is similar. Internal communication can lean on shared context and faster, less formal channels; external communication typically needs more structure and documentation, since the recipient doesn't share the team's day-to-day context and the exchange may carry more formal weight.

Delivering unwelcome news honestly. A significant scope reduction or delay still needs to be communicated clearly and directly, along with the reasoning behind it and any mitigation being considered — burying it inside an otherwise positive-sounding update, or omitting it altogether, undermines the transparency stakeholder communication depends on, even when the news itself is hard to deliver.

Gathering input at scale versus depth. A survey and a series of one-on-one interviews aren't interchangeable, even when both are technically "communication." A large, geographically distributed group giving quick feedback fits a survey; a small number of key stakeholders needing to walk through nuanced concerns fits interviews. Picking the wrong one for the audience size either drowns the BA in unmanageable individual conversations or produces feedback too shallow to act on.