Client Communication

Executive Summary

Client communication is the highest-leverage non-technical skill an FDE possesses — and the most frequently underinvested. An FDE who can explain a complex AI integration risk to a CFO in two sentences, write a status report that a CIO reads in three minutes and fully understands, and escalate a blocking issue in a way that produces a decision rather than a meeting has a compounding advantage in every client engagement. This chapter provides the frameworks, templates, and principles for FDE communication across four contexts: executive briefings, technical status reports, escalation communications, and risk communications. The emphasis throughout is on precision and audience calibration — the right level of technical detail for the person receiving the communication, at the moment they need it.

Learning Objectives

Structure executive communications that deliver a complete message in under three minutes
Write technical status reports that serve both technical and executive audiences without duplication
Escalate issues in a way that produces decisions rather than additional meetings
Calibrate technical depth to the audience's role and decision-making need
Communicate AI risk to non-technical stakeholders without either minimizing or catastrophizing

Business Problem

FDE communication failures are costly and common. Technical FDEs who write status reports that are too detailed lose their executive audience. FDEs who write reports that are too thin lose their technical audience's trust. FDEs who escalate issues through informal channels — Slack messages, verbal mentions — find that issues do not get resolved because no one is formally accountable. FDEs who communicate AI risk using jargon ("the embedding similarity score has drifted") create confusion rather than informed decision-making.

The consequence is not just a communication problem — it is a delivery problem. Status that is not communicated clearly is invisible. Risk that is not communicated in decision-relevant terms does not get mitigated. Issues that are not escalated in writing do not get resolved.

Conceptual Explanation

Effective client communication follows three principles:

Bottom Line Up Front (BLUF): The most important information goes in the first sentence — not after the context. Executives who read only the first sentence must still understand the essential message.

Audience calibration: Technical depth is determined by the audience's decision-making need, not by the FDE's desire to demonstrate competence. A CFO making a budget decision needs dollar figures and risk levels. An IT director making an architecture decision needs technical specifics. Neither needs what the other needs.

Action orientation: Every communication should end with a clear action — a decision requested, an information delivery confirmed, or a next step assigned to a named owner. Communication that ends with "please let us know if you have questions" produces no action.

Core Architecture: Communication Frameworks

The one-pager is the primary vehicle for communicating with executive stakeholders. It must be readable in 3–5 minutes and contain everything the executive needs to make a decision or understand a situation.

Implementation code omitted in the Playbook edition. For complete code examples, production patterns, and advanced implementation details, see the Enterprise AI Technical Reference. mermaid graph TD subgraph "Communication Planning" AUD["Identify Audience\nExecutive / Technical / Clinical"] NEED["Identify Need\nDecision / Inform / Escalation / Risk"] FORM["Select Format\nOne-pager / Status / Escalation / Risk brief"] end

subgraph "Communication Execution" BLUF["Lead with Bottom Line\nFirst sentence carries the message"] DEPTH["Calibrate Depth\nExecutive: outcomes / Technical: mechanics"] ACTION["End with Action\nDecision / Owner / Date"] end

subgraph "Document Types" ONE["Executive One-Pager\n3-minute read"] STATUS["Technical Status Report\nDual-section: exec + technical"] ESC["Escalation\nSituation + Impact + Decision"] RISK["Risk Communication\nConsequence language"] end

AUD --> NEED --> FORM FORM --> BLUF --> DEPTH --> ACTION FORM --> ONE & STATUS & ESC & RISK


## Common Mistakes

**1. Burying the key message.** Opening with three paragraphs of context before stating the main point means executives stop reading before reaching the main point. Lead with the conclusion.

**2. Using technical jargon with executive audiences.** "The vector similarity score is below threshold" means nothing to a CMO. "The AI's knowledge base may contain outdated clinical guidelines" means something they can act on.

**3. Escalating without a recommendation.** Escalations that present a problem without a recommendation force the executive to solve a problem they don't have context for. Always include a specific recommendation.

**4. Status reports with no status.** "We are making good progress on the integration" is not a status. "FHIR data retrieval complete; AI gateway deployed; beginning physician evaluation on [Date]" is a status.

**5. Not establishing communication expectations at engagement start.** Cadence, format, and audience expectations should be agreed in the first week. Improvised communication at the end of an engagement is less effective than a disciplined cadence established from the start.

**6. Communicating AI risk with false precision.** "The AI has a 3.7% hallucination rate" implies a precision that evaluation datasets do not support. "In our evaluation, the AI produced clinically inaccurate content in approximately 4 of 50 encounters — all identified and corrected during physician review" is more honest and more actionable.

## Best Practices

- Establish communication cadence, format, and audience in the first week
- Lead with the bottom line — always
- Write separate executive and technical sections in status reports — not a single document that tries to serve both
- Escalations must include a specific recommendation and decision deadline
- AI risk communications use consequence language, not technical language
- Never quantify AI risk with false precision — use ranges or approximate counts
- Produce all escalation communications in writing — verbal escalations are not escalations

## Trade-offs

**Detail vs. readability:** More detail increases completeness but reduces the probability that the document is fully read. The right level of detail is determined by the audience's decision-making need, not by the FDE's desire to demonstrate thoroughness.

**Frequency vs. quality:** Weekly status reports that are comprehensive take 2+ hours to produce. The FDE must balance communication investment against execution time. Template-based reports that take 30 minutes to complete are more sustainable than reports that take 3 hours.

## Interview Questions

### Q: A critical blocking issue has emerged in a healthcare AI engagement that requires the client's Chief Compliance Officer to make a decision within 48 hours. How do you communicate this?

**Category:** Behavioral
**Difficulty:** Senior
**Role:** FDE

**Answer Framework:**

The escalation communication follows the BLUF structure: situation, impact, decision required, options, recommendation — in that order, in writing, within 24 hours of the issue emerging.

The message to the CCO is a one-page escalation document, not an email thread. It opens with the bottom line: "A HIPAA Business Associate Agreement must be signed to proceed with the POC, and the [Date] launch date is at risk if it is not signed by [Date + 2 days]." The body quantifies the impact precisely — 15 days delay, Q3 vs. Q4 production decision, and any downstream consequences for budget cycles or contract milestones. It presents two options (sign by [Date + 2], or reschedule launch to [Date + 17]) with a clear recommendation. It ends with a specific request: "Please confirm your decision by [Date + 1 day] so we can adjust the POC schedule."

In parallel, I notify the FDE's internal account lead so they are not surprised if the CCO escalates internally.

**Key Points to Hit:**
- Written escalation, not a verbal mention or Slack message
- BLUF structure: bottom line first
- Quantified impact, not vague language
- Specific recommendation
- Concrete decision deadline
- Internal notification to account lead in parallel

**Red Flags:**
- Verbal escalation only
- Escalation without a recommendation
- Vague impact description ("this could slow us down")

## Key Takeaways

- Bottom Line Up Front: the most important message goes in the first sentence
- Four communication formats: executive one-pager, technical status report, escalation, risk communication
- Calibrate technical depth to the audience's decision-making need — not to demonstrate competence
- Escalations must include a recommendation, quantified impact, and decision deadline
- AI risk communications use consequence language, not technical jargon
- Establish communication cadence, format, and audience in the first engagement week
- Written escalations produce decisions; verbal escalations produce meetings

## Further Reading

- [Value Engineering](07-value-engineering.md) — Financial frameworks for executive communications
- [Common Objections](09-common-objections.md) — Communication patterns for objection handling
- [Healthcare Client Playbook](10-healthcare-client-playbook.md) — Healthcare-specific communication patterns for CMIO and compliance audiences

Client Communication#

Executive Summary#

Learning Objectives#

Business Problem#

Conceptual Explanation#

Core Architecture: Communication Frameworks#

Framework 1 — Executive Briefing (One-Pager)#