Executive Communication

Why this lesson matters more than it should

Many engineers — even talented ones — treat executive communication as a tax. Slides to prepare, meetings to survive, emails to keep brief. The job is the real work; the meetings are interruptions.

This is exactly backwards. In FDE work, executive communication often decides whether the technical work gets to ship at all. A great system can be cancelled by an unread memo and a confused VP. A mediocre system can survive on the strength of a sponsor who feels informed and respected.

The pattern is so common that veteran FDEs build executive communication discipline before they polish their technical chops. Both matter; only one is consistently under-invested in.

This lesson is about catching up the under-invested half.

What executives actually need

A useful starting point: most executives have less than 5 minutes for your engagement on a typical day. They have 8 meetings, 200 emails, and a quarterly board deck to write. The communication you produce competes — not against other engagement updates, but against everything else on their plate.

In those 5 minutes, what do they need?

• The headline. What changed since last time? Is it on track?
• The number. The outcome metric the engagement was sold against.
• The exception. Anything that’s stuck, blocked, or off-trend.
• The ask. What you need from them — even if it’s “nothing, just informing.”

If your communication answers those four questions in the first 30 seconds, you’ve earned the next 4.5 minutes. If it doesn’t, the executive has already mentally moved to the next item, and your 5 minutes are wasted no matter what comes after.

The BLUF discipline

Military and government circles call this BLUF — Bottom Line Up Front. Lead with the conclusion, then the reasoning. It is the single most useful executive-communication discipline you will adopt.

Compare:

Without BLUF:

“Hi team — wanted to give you an update on the dispatch platform. We’ve been running through some interesting work on the integration side with SAP. There were some challenges with the SOAP endpoint that took longer than we expected. Maria has been a great partner. On-time delivery has been moving in a positive direction overall, though there were some weather-related impacts in week 3…”

With BLUF:

“On-time delivery is at 87% this week, on pace to hit the 92% quarterly target. Cutover is complete; Maria and Doug are using the platform daily. One blocker: the customer notification integration needs SAP team’s sign-off on the API contract — would value your help unblocking it. Full status below.”

Same content. Twentieth-fastest reader gets the headline; the rest can choose to read on. Compare which version a busy VP actually retains.

Three communication artifacts you produce repeatedly

Across an FDE engagement, you will produce these three artifacts hundreds of times. Build templates and stay disciplined.

Artifact 1 — The weekly status update

Form: an email or Slack post, 100-200 words, sent Friday afternoon or Sunday evening.

Template:

Subject: Northbound — week of May 12

Headline: on-time delivery 87%, on pace to 92% by quarter end.

Shipped this week:
  • Reassignment workflow live for Maria + Jorge
  • Doug's hub view in pilot at the east hub
  • First morning brief from the AI agent (5:45 AM, posted to ops Slack)

In progress / next week:
  • Multi-dispatcher rollout (Cleveland hub)
  • Slip-alert push notifications

Needs attention:
  • SAP API contract sign-off (blocked at IT director; will need exec nudge if not unblocked by Tuesday)

Metrics:
  • DAR: 3/3 dispatchers, 5/5 days
  • Maria's morning batch time: 6 min (was 45)
  • Slipping loads identified before 06:30: 100%

Next reviews:
  • Tue 10am: steering committee
  • Thu 3pm: operator drop-in at the east hub

This format is boring on purpose. Boring is good. The executive sees the same shape every week, learns where to look for the number and the asks, and stops having to read carefully — the discipline lets them scan.

A worked variant for sponsors who are less data-engaged: replace “DAR” with “all three dispatchers using daily” — translate jargon as you go.

Artifact 2 — The five-minute brief

Form: a verbal briefing, often impromptu, when you run into the VP in the hallway or get pulled into an unscheduled exec sync.

Structure:

1. The headline. “We’re on pace to the 92% target.”
2. The supporting evidence. “On-time was 87% last week, up from 78% baseline.”
3. The one risk worth mentioning. “The SAP team’s contract sign-off is at one week of slip — not yet critical, but worth tracking.”
4. The ask, if any. “I’d value your nudge to the SAP team if it’s still stuck by Wednesday.”
5. Stop talking.

Total time: 90 seconds if needed. The executive can ask follow-ups. Most won’t — and that’s a sign you communicated well.

A common mistake: filling the 5 minutes with detail because it’s available. Don’t. The executive’s silence after your 90 seconds is permission to leave, not an invitation to elaborate.

Artifact 3 — The decision memo

Form: a one-page written document for any non-trivial decision the executive needs to make. Read offline, decided in a meeting (or async).

Template:

DECISION: Should we expand the dispatch platform to the Cleveland hub
          in iteration 7, or focus iteration 7 on customer-facing tracking?

CONTEXT
The platform is live at the Chicago and East hubs (Doug). Cleveland's
hub manager has asked for the platform; customer success has flagged
two large customers asking for self-service tracking.

OPTIONS

  A — Cleveland expansion
    Pros: extends the platform to a 3rd hub; reinforces the dispatch
          workflow; predictable build (2 weeks).
    Cons: doesn't address external customer asks; less visible to
          the sales team.

  B — Customer-facing tracking
    Pros: visible win for sales and account management; opens an
          external surface for the platform; supports two retention-
          risk customers.
    Cons: external auth + branding adds 1 week vs. internal-only
          screens; touches procurement (new vendor agreement).

RECOMMENDATION
Option B. The two customer asks have specific account managers and
clear dates; missing them costs more than delaying Cleveland by one
iteration. Cleveland is queued for iteration 8.

REQUIRED FROM YOU
Approve direction by Thursday so iteration 7 kickoff happens Monday.

Five sections. One page. The executive can read it in 90 seconds, decide in a meeting, and the team is unblocked. Decision memos are the highest-leverage written artifact you produce; treat the template as sacred.

The steering committee

If your engagement has a steering committee — and it usually should — it is your highest-stakes recurring communication forum. Monthly, 60 minutes, executives from both sides.

The mistake most teams make: showing up with slides, walking through them, taking questions. This is theater. Real decisions don’t happen, and people walk away feeling they’ve “been briefed” instead of having decided anything.

A senior FDE structures the steering committee around decisions, not status.

A working agenda:

STEERING COMMITTEE — 60 MIN

  5 min   Status snapshot — three numbers, two sentences each (no slides)
 10 min   What went well, what went wrong (5 each, named)
 30 min   Decisions on the table — three at most, each with a memo pre-read
 10 min   Risks and asks — bring problems before they're crises
  5 min   Confirm decisions; assign owners; close

Two principles in this agenda:

1. The numbers are pre-read, not presented. If the executives haven’t read the status before the meeting, the meeting is the wrong forum to read it.
2. Decisions, not status, are the meeting’s product. Three decisions in 30 minutes is the target. Each one produced from a one-page memo (artifact 3), so the meeting itself is discussion, not reading.

After the meeting, you send a 5-sentence recap with the three decisions and their owners. Within 24 hours. Always.

Adjusting register

Different executives hear different communication. A useful four-bucket model:

The Northbound VP — Maria’s sponsor — is operator-flavored. The CEO is political-flavored. The CFO would be data-flavored. The IT director is tech-flavored.

The same factual update gets translated for each:

• Operator: “Maria reported this morning that her 6:45 call with Doug is now under 5 minutes. She used to spend 45 minutes prepping for it.”
• Data: “On-time delivery is 87% this week, ▲ 9pts since baseline. We’re at 73% of the quarterly target trajectory.”
• Tech: “The dispatch service has been stable through cutover. Zero P1 incidents in the first 14 days. SAP integration is the remaining risk area; we’re tracking the API contract.”
• Political: “The dispatch platform is in production and the on-time KPI is moving. We’re positioned for the customer-facing tracking expansion that would differentiate Northbound from competitors in Q3.”

Same week, same facts, four versions. Senior FDEs build the muscle to render the same update in any register on demand.

Surfacing bad news

The hardest single skill in executive communication: telling the sponsor something is wrong, in a way that doesn’t blow up the engagement.

The instinct most engineers have is to bury bad news, soften it, or wait for it to resolve before mentioning. All three are failure modes. The bad news surfaces anyway — louder, later, and with the engagement’s credibility damaged.

A senior FDE surfaces bad news on three principles:

Principle 1 — As soon as it’s real

Not “as soon as you suspect.” Bad news surfaced too early is noise. Bad news surfaced when you have confirmed it is real — investigated, scoped, with a forming plan — is signal. The threshold is: you have spent at least 30 minutes investigating and you are confident in the facts.

Principle 2 — With the plan in the same sentence

Never surface a problem without a proposed plan, even a half-formed one. The executive’s first question after “we have a problem” will be “what are you doing about it?” — answer it before they ask.

“The SAP team’s API contract sign-off has slipped by a week, which puts iteration 7’s customer tracking launch at risk for the planned date. Our plan: I’m meeting with their lead Thursday to scope the actual technical concern, and we have a fallback design that uses the file-drop pattern instead of REST if we can’t unblock by Monday. I’ll know which path by EOD Friday.”

The executive now has both the problem and the plan. They can decide whether to intervene (probably not, the plan is reasonable) or let it run. Either way, they trust you to handle it.

Principle 3 — Without dramatizing

The pattern that earns trust: bad news delivered in the same tone as good news. Not because it’s not serious, but because dramatizing it produces emotional rather than rational executive response.

Compare:

Dramatized: “We have a major problem — SAP has completely blocked us and the whole iteration 7 is at risk of falling apart.”

Calm: “SAP integration sign-off is at one week of slip. Iteration 7 has a 60% chance of launching on date if not unblocked by Monday. Plan in place to mitigate by Friday.”

The second version is more specific, more useful, and easier for the executive to act on. It also makes the next round of bad news easier to deliver — because you’ve established a calm-and-specific tone as the baseline.

Common failure modes

Death by detail

You walk into the briefing prepared to explain the integration architecture. The VP doesn’t want the architecture; she wants the number and the risk. Trim ruthlessly. The detail you cut can sit in an appendix or in a doc the curious can find.

Burying the lede

You spend three paragraphs setting up context before getting to the conclusion. The reader has stopped paying attention by paragraph two. Always BLUF.

Asking for input you don’t actually want

“What do you think we should do?” — only useful if you genuinely have no recommendation. If you have one, lead with it. Otherwise you make the executive do work that’s actually your job.

Soft-pedaling the ask

A great status update with a vague ask at the end produces no action. If you need the VP to call the SAP director, say it: “Specifically, I’d value if you’d ping Sarah at SAP this week.”

Performing certainty

You feel pressure to sound certain about everything. You don’t have to be. “On-time delivery is 87% and I’m 80% confident we hit the 92% target by quarter end. The remaining 20% risk is X” — calibrated language earns more trust than false certainty.

Reactive cadence

You only communicate when asked. The executive concludes either that you have nothing to report (engagement risk) or that you’re hiding something (worse). Set a regular cadence and hold to it — Friday updates, monthly steering, quarterly business reviews.

Skipping the recap

The meeting happens. Decisions are made. You don’t send the recap. Three weeks later nobody remembers what was decided. Always recap, within 24 hours.

Writing for executives, specifically

A few writing-craft rules that pay off:

Use named-actor sentences

“The data pipeline failed” is passive. “The SAP nightly export failed twice this week” is named. Executives parse named-actor prose faster.

One idea per sentence

A sentence with two clauses joined by “while” or “although” forces the reader to do parsing work. Use periods.

Specific over general

“Several customers” → “Acme and Riverpoint.” “Some performance issues” → “p99 latency on the morning view spiked to 6 seconds Tuesday.”

Numbers, not adjectives

“Significant improvement” → “9-point lift.” “Most operators are using it” → “3 of 3 dispatchers daily, 4 of 5 hub managers weekly.”

Date everything

“Recently” → “in the week of May 12.” “Soon” → “by June 22.”

Cut the throat-clearing

“It is worth noting that…” → just say it. “I wanted to flag that…” → “Flagging:” or, better, just the thing.

The cumulative effect of these rules is prose that reads like it was written by someone who values the executive’s time, which is exactly the signal you want to send.

Communicating with your own management

A specific sub-skill the lesson would be incomplete without: communicating with your company’s management about the engagement.

The instincts here are different from communicating with the customer. Your management:

• Has more context on the platform than the customer’s exec
• Has less context on the customer than you do
• Is being asked about your engagement in their own management chain
• Cares about the renewal trajectory and the replicability of patterns

What they need from you, weekly:

• Renewal signal. What’s the customer’s mood? Are they likely to renew, expand, or churn? Why?
• Pattern transferability. What did you learn that helps the next engagement? The next customer?
• Risk surface. What could blow up this engagement that you can’t fix alone — and where would you want air cover?
• Help requested. What from your own org would unblock you — a platform feature, an exec call, another FDE for a week?

Build the discipline of bidirectional executive communication. Your customer-facing executive briefing is one half. Your internal-facing briefing is the other half. Both feed each other; both are part of the job.

Closing

Executive communication is not a separate skill from FDE work — it is the part of FDE work that decides which other parts get to happen. Engineers who treat it as overhead lose engagements they could have won. Engineers who treat it as craft watch their technical work compound.

The discipline is learnable. Practice the templates. Use BLUF. Keep the cadence. Surface bad news calmly. Recap every meeting. Adjust register for the audience. By month three of any engagement you should feel as confident in a sponsor briefing as you do in a code review.

Key terms to remember

• BLUF — Bottom Line Up Front; the foundational executive-communication discipline
• The three artifacts — weekly status, five-minute brief, decision memo
• Registers — operator, data, tech, political; translate the same content for each
• Decision memo — one-page document that frames a choice and earns a decision
• Steering committee — monthly forum oriented around decisions, not status
• Surfacing bad news — as soon as it’s real, with a plan, without dramatizing
• Cadence — regular, predictable communication that earns trust over time

What’s next

You can write and brief. The final off-keyboard skill — and the one that determines whether you ever get to deploy anything — is navigating the customer’s procurement, security, and legal apparatus. The last lesson of the course before the capstone covers this back-office territory most engineers under-invest in.