Communicating with Stakeholders
Key Takeaways
- Under the BACCM, a stakeholder is any group or individual with a relationship to the change, the need, or the solution.
- BABOK Guide v3 identifies four underlying communication skills a business analyst relies on: verbal, non-verbal, written, and listening.
- Effective stakeholder communication tailors content depth, format, timing, and technical language to each recipient's role and decision-making needs.
- Active listening includes restating what a stakeholder said in the analyst's own words and watching for non-verbal cues that may signal unspoken disagreement.
- Poorly matched communication increases the risk of stakeholder disengagement, inaccurate requirements, and resistance to the eventual solution.
Why Stakeholder Communication Is Core to Business Analysis
Under the Business Analysis Core Concept Model (BACCM), a stakeholder is defined as a group or individual with a relationship to the change, the need, or the solution. Because nearly every business analysis task depends on stakeholders sharing information, expressing needs, and approving outcomes, communication is not a peripheral skill — it is the mechanism through which almost all other business analysis work gets done. The Business Analysis Standard frames business analysis as a discipline centered on enabling change by understanding organizational needs, and understanding is a two-way communication process: the business analyst (BA) must extract accurate information from stakeholders and, just as importantly, deliver information back to them in a form they can act on.
Communication quality directly affects stakeholder engagement. Stakeholders who receive information that is too dense, too shallow, poorly timed, or delivered through the wrong channel disengage, provide inaccurate feedback, or resist the eventual solution. Communication that matches each stakeholder's needs sustains engagement across the life of an initiative, from early elicitation through post-implementation value assessment.
Tailoring the Message to the Audience
A single set of findings — for example, a requirements change — is rarely communicated identically to every stakeholder. Effective business analysis practice calls for the BA to tailor content, level of detail, format, and timing to each recipient's role, decision-making authority, technical background, and information needs.
Key tailoring dimensions:
| Dimension | Consideration | Example |
|---|---|---|
| Content depth | How much detail does the audience need to act? | A sponsor needs business impact and cost/benefit framing; a developer needs functional detail |
| Format | What medium fits the message and the audience's habits? | Executive summary and slide deck vs. a detailed specification document |
| Timing | When does the recipient need the information to decide? | Deliver budget impact before a funding decision, not after |
| Technical language | Does the audience share the same vocabulary? | Avoid system jargon with business stakeholders; avoid business jargon with highly technical teams |
| Frequency | How often does the stakeholder expect updates? | Sponsors may want milestone summaries; a delivery team may want frequent working updates |
Typical role-based communication approach:
- Sponsor — concise business-impact summary, value/ROI framing, decision points highlighted
- Domain subject matter expert (SME) — detailed process or requirements walkthroughs, opportunity to validate accuracy
- End user — plain-language explanation of what changes for their daily work, opportunity to give feedback
- Implementation SME (developer, architect) — precise functional and non-functional specifications, traceable requirements
- Regulator or compliance stakeholder — formal documentation demonstrating adherence to standards or rules
Underlying Communication Skills
BABOK Guide v3 identifies Communication Skills as one of the underlying competencies a BA relies on across every knowledge area: verbal communication (clarity and tone in conversations, interviews, and presentations); non-verbal communication (reading and using body language, facial expression, and tone to reinforce or detect meaning beyond words); written communication (structuring documents, emails, and requirements artifacts so they are unambiguous); and listening (actively attending to what stakeholders say — and don't say — to capture accurate information and detect concerns early).
Active listening is particularly important in stakeholder-facing sessions: restating what a stakeholder said in the BA's own words, asking clarifying questions rather than assuming understanding, and watching for non-verbal cues such as hesitation, avoided eye contact, or crossed arms that may signal unspoken disagreement or discomfort with a proposed direction.
Planning the Communication Approach
Communication with stakeholders is not ad hoc — it is planned. Early in an initiative, the BA identifies each stakeholder's information needs, preferred communication style, and any organizational, geographic, or cultural factors that affect how information should be delivered, such as formality expectations, language differences, or time-zone constraints for distributed teams. This planning ensures that as the initiative proceeds, the right people receive the right information, in the right format, at the right time — reducing the risk of surprises, misalignment, or late-discovered objections.
Consequences of Poor Communication
When communication is mismatched to the audience, several risks compound: stakeholders disengage from elicitation and review activities because the material doesn't serve them; requirements are approved without real understanding, creating rework later; and resistance to the eventual solution increases because affected stakeholders feel uninformed rather than involved. Well-tailored, consistent communication builds the trust needed for stakeholders to share accurate, complete information and to support the change once it is delivered.
Worked Example
Consider a scenario common on the ECBA exam: a BA has just completed elicitation sessions with end users and needs to report findings to both the project sponsor and the technical delivery team before the next planning meeting. The correct approach is not to draft one document and send it to both — it is to produce two tailored communications: a short summary of business impact and value for the sponsor, timed ahead of a funding decision, and a detailed functional walkthrough for the delivery team, timed ahead of design work. Recognizing which tailoring dimension is at stake — content depth, format, or timing — is exactly the kind of situational judgment the exam tests.
A business analyst has just finished eliciting requirements changes and must report the findings to both the project sponsor and the development team before the next planning meeting. What is the most effective communication approach?
During a status meeting, several stakeholders nod along but avoid eye contact when asked whether a proposed process matches their needs. Which underlying communication skill should the business analyst rely on to correctly interpret this signal?