Analysis is only valuable if you can communicate it clearly. This module covers how AI helps BAs write better stakeholder emails, structure difficult scope and escalation conversations, produce executive-ready summaries, and adapt their communication for different audiences — without losing the relationship intelligence that only you have.
Audience-aware communication — why it matters and where AI helps
One of the defining characteristics of a strong BA is the ability to communicate the same analysis differently to different audiences. The technical detail that a developer needs is noise to a VP of Operations. The strategic framing that works with an executive is frustratingly vague to a QA team trying to write test cases. Adapting is a skill — and it's one that AI can support directly.
The key is understanding that AI adapts communication style and structure well, but it doesn't know your stakeholder relationships, the organisational dynamics at play, or the history that shapes how a particular message will land. You provide that context; AI handles the structure and language.
Audience
What they care about
What to ask AI for
What AI can't know
VP / Executive sponsor
Business outcomes, risks to delivery, decisions needed, costs and timeline
Current regulatory review status, in-progress filings, regulator relationship context
The consistent prompt pattern
For every stakeholder communication, tell AI: who the audience is and their role, what they care about, what you want them to know or do, any constraints on tone or length, and any specific context about the situation. The more you tell it about the audience, the better the output. What AI will never have — and you must supply — is the relationship history and organisational context that makes the difference between a technically correct message and one that actually lands.
2
Professional emails, faster — the most used BA AI application
BA work involves a relentless volume of professional email: follow-up after sessions, clarification requests to stakeholders, escalation notices, scope change notifications, status updates to sponsors, and coordination with vendors and technical teams. Each of these is a small but real time commitment — and each has a standard professional structure that AI can draft in seconds.
Prompt — scope change notification to executive sponsor
Role / context
I'm a BA on a Guidewire PolicyCenter implementation. I need to notify the executive sponsor (VP of Operations at the insurer) that a scope change has been approved in the last steering committee that adds the broker portal integration to the current project phase. This was not in the original scope.
Task
Draft a professional email to the VP of Operations informing them of this scope addition, its approved rationale, and the impact on timeline and resource requirements.
Context
The scope change was approved by the steering committee and is not in dispute. The timeline impact is 6 weeks added to the implementation phase. An additional BA resource has been approved for 3 months. The VP was not at the steering committee meeting. I have a good working relationship with this VP — direct and factual tone is appropriate. No need for excessive formality.
Format
Professional email, under 200 words. Clear subject line. Cover: what changed, why it was approved, what it means for the timeline, what has been put in place to manage it, no action required from the VP — information only. Offer to discuss if they have questions.
This pattern — role/context, task, relationship context, format — produces emails you can send with minor editing in under 2 minutes. The relationship context is critical: telling AI "direct and factual tone is appropriate" versus "this VP is risk-averse and needs reassurance before the facts" will produce noticeably different emails. You're the one who knows which framing is right.
Knowledge Check
You need to send an email to a business SME asking them to confirm a critical business rule about claims payment authorisation limits. The SME is known to be difficult to engage and tends to give vague responses. You ask AI to draft the email. What context is most important to include in your prompt?
Correct. For a known vague responder, the email needs to make vagueness harder. That means asking for a specific answer to a specific question, explaining why it matters (the decision that depends on it), and setting a deadline. You review the draft to make sure there's no open-ended question that invites a non-answer. Telling AI the SME is "difficult" doesn't help — AI will either ignore it or make the tone aggressively assertive, neither of which solves the problem. Structural clarity solves the problem: make the question binary where possible.
Option 3 is the most useful approach. For a stakeholder who tends to be vague, the solution is structural, not tonal: ask a specific question that has a specific answer, explain why the decision matters, and set a deadline. Full technical background adds length without improving response quality. Generic emails get generic responses. Asking AI to be "assertive" doesn't improve response quality and may damage the relationship. You review the draft specifically for anything that could be answered evasively — if the question can be misunderstood, rewrite it.
3
Difficult conversations — AI as a thinking partner, not a script writer
BAs regularly face communication situations where the stakes are high and the tone has to be exactly right: a scope creep conversation with a business stakeholder who keeps adding requirements, an escalation about a project risk that no one wants to hear, a conversation with a developer about requirements quality being inadequate, or a discussion with a sponsor about timeline slippage.
AI cannot have these conversations for you — and you shouldn't want it to. These are relationship-sensitive, contextually complex interactions that require the kind of judgment that only comes from knowing the people involved. But AI is an excellent thinking partner for structuring your approach before you go into the conversation.
Using AI to prepare for a difficult conversation
Situation: The VP of Claims has been adding new requirements in every session — verbal scope additions that are now threatening the Phase 1 timeline. You need to have a scope boundary conversation without damaging the relationship.
Good AI use: Describe the situation (without naming the VP or including any client confidential details) and ask AI to help you think through: what the core message is, how to frame scope management as being in the VP's interest, what objections they're likely to raise and how to respond, and what a reasonable outcome from the conversation looks like.
What you add: You know this VP responds well to data. You've worked with them for eight months and there's mutual respect. You know the additional requirements they've been adding reflect a real business problem they're worried about. You frame the conversation around solving that underlying concern through Phase 2 scope, not just enforcing the boundary. That framing is yours — AI doesn't know any of it.
Prompt — preparing for a scope conversation
Role / context
I'm a BA on a large insurance IT implementation. A senior business stakeholder (VP level) has been verbally adding requirements in every discovery session. The project is now at risk of timeline slippage if these continue to be absorbed into Phase 1 scope. I need to have a scope boundary conversation.
Task
Help me think through how to structure this conversation. Give me: the key message I need to communicate clearly, how to frame scope management as being in the stakeholder's interest rather than a constraint imposed on them, the most likely objections and how to respond, and what a good outcome from this conversation looks like.
Context
The stakeholder is a decision-maker who genuinely cares about the project succeeding. The additional requirements they're adding reflect a real business concern. I want to find a path that protects the Phase 1 timeline while giving them a clear route for the requirements they care about to be addressed in Phase 2.
Format
Structured as: 1) Core message in one sentence, 2) Framing that positions this as a shared goal, 3) Top three objections with suggested responses, 4) Ideal outcome. Do not write a script — give me a framework I can use in a natural conversation.
Knowledge Check
You've used AI to help structure your approach to a difficult scope conversation. The AI suggested a specific way to frame the Phase 2 commitment that sounds professionally solid. However, you know that the Phase 2 timeline is not actually confirmed yet at the steering committee level. What should you do?
Correct. This is a professional judgment call that AI cannot make for you. AI generated a framework based on what you described — but it doesn't know what you can and can't actually commit to. Making a Phase 2 commitment to resolve a scope conversation, when Phase 2 isn't confirmed, creates a stakeholder expectation that will eventually be a bigger conversation than the one you were trying to avoid. The professional answer is to be precise about what you're offering: the requirements will be documented and proposed for Phase 2, subject to steering committee approval. That's honest and defensible.
Option 2 is the professional approach. AI frameworks are starting points — your judgment determines what you actually use. Making an unconfirmed commitment to smooth over a difficult conversation creates a larger trust problem when the stakeholder holds you to it and you can't deliver. Vague language doesn't solve the problem either — it just delays it. Waiting for Phase 2 to be confirmed before having any scope conversation may not be practical. The right answer is to use the framework but adjust the specific commitment to reflect reality: these requirements will be documented and proposed for Phase 2 consideration, pending steering committee confirmation.
4
Executive summaries — making analysis accessible to people who won't read it
One of the most valuable communication skills a BA can have is the ability to distil complex analysis into a crisp, decision-focused executive summary. Most senior stakeholders in insurance organisations are time-constrained, risk-aware, and focused on commercial outcomes. They don't read BRDs. They read summaries. The quality of your summary often determines whether your analysis actually influences decisions.
AI is particularly good at executive summaries because the format is highly structured — situation, analysis, options, recommendation, decision required — and AI can compress a lengthy document into that structure quickly once you give it the source material and the audience context.
Prompt — executive summary from a BA impact assessment
Role / context
I'm a BA who has completed an impact assessment for adding Rideshare Coverage as a new endorsement in PolicyCenter. The assessment identified significant impacts across 7 areas including FSRA regulatory filing requirements, PolicyCenter configuration, BillingCenter integration, and broker portal changes. I need to present this to the VP of Operations and CFO in a 15-minute slot at next week's steering committee.
Task
Draft a one-page executive summary of the impact assessment for the steering committee audience. The summary needs to communicate: what the scope of implementation actually entails (vs what was originally assumed), the regulatory risk that must be resolved before implementation, and the decision the steering committee needs to make.
Context — key findings from the assessment
Original assumption was a 2-sprint configuration change. Actual scope: 5 impact areas rated High, 2 Medium. FSRA filing requirement for new endorsement type — not yet confirmed with compliance team. BillingCenter integration requires a separate sprint. Broker portal changes require external vendor involvement (4–6 week lead time). Recommended timeline: 14 weeks minimum vs original 4-week estimate. Decision needed: proceed with full scope and revised timeline, or scope Phase 1 to PolicyCenter only and defer broker portal and BillingCenter to Phase 2.
Format
One page maximum. Structure: Situation (2 sentences), Key findings (3–4 bullet points), Risk requiring resolution (1 paragraph — regulatory), Options and recommendation (clear and direct), Decision required (one sentence stating exactly what the steering committee needs to decide). Avoid jargon. Audience is VP and CFO — business and financial focus.
The "decision required" line
The most important sentence in any executive summary is the last one: the decision required. It should be specific, binary where possible, and state who is being asked to decide. "The steering committee is asked to approve Option B (phased approach) or direct the team on an alternative approach by [date] so implementation planning can proceed." If you can't write this sentence, you don't yet know what you're asking for — which means the summary isn't ready.
Knowledge Check
You've asked AI to produce an executive summary from your impact assessment. The AI summary includes a sentence that says "The FSRA filing requirement is expected to add 3 weeks to the timeline." You know this estimate came from a verbal comment by a colleague, not a confirmed position from the compliance team. How do you handle this?
Correct. An unverified timeline estimate in an executive summary to a CFO and VP becomes a project commitment the moment it leaves your hands. "Expected to add 3 weeks" will be treated as a fact in planning, resourcing, and board reporting. If it's wrong — and a verbal colleague comment is not a verified estimate — you own that error. The right approach is to make the uncertainty explicit and create the accountability structure to resolve it. Framing it as an open item that must be resolved before the implementation decision can be finalised is accurate and professional.
Option 4 is the professional choice. Unverified estimates in executive summaries become planning assumptions that people build on. "Approximately 3 weeks" is still a specific enough number to end up in a project plan. Removing any mention of regulatory timeline removes something the steering committee genuinely needs to know about. The right answer acknowledges the regulatory impact without inventing a timeline — and creates explicit accountability for resolving the uncertainty before decisions are made. AI drafts what you give it; your review determines what's actually true.
5
Module summary
✅
Audience adaptation
Tell AI who the audience is, what they care about, and any relevant relationship context. AI adapts structure and language. You supply the organisational knowledge that determines what will actually land.
✅
Email efficiency
Role, task, relationship context, format. Four components — consistently produces professional emails you can send with minimal editing. The relationship framing is the most important thing AI doesn't have and you must supply.
✅
Difficult conversations
AI as a thinking partner for structure and preparation — not a script writer. The conversation requires your judgment and relationship knowledge. AI helps you think through framing, objections, and outcomes in advance.
✅
Executive summaries
Situation, findings, risk, options, decision required. AI compresses your analysis into this structure fast. Your review ensures nothing unverified enters the document — especially timeline estimates and regulatory commitments.
One module left
Module 05 — Your AI-Augmented BA Practice — brings the full pathway together. You'll assess where you've come across the five modules, understand how to position your AI capability in the market, and leave with a clear picture of what an AI-augmented BA practice looks like in practice — starting next week, not in theory.
✓
Module 04 Complete
Stakeholder Communication is done. One module left. Continue to Module 05: Your AI-Augmented Practice.