Executive Communication — Bandwidth Is Your Most Scarce Resource

60-Second Summary

Exec comms is high-bandwidth, low-frequency, asymmetric. Get it wrong and you spend weeks correcting.
Lead with the headline (BLUF: Bottom Line Up Front).
Default to writing — speech is for charge, writing is for clarity.
Repeat key messages 7x in 7 channels before assuming people heard you.
Every exec sentence is policy — choose words like you're writing code.

A CEO casually said in a town hall 'we're probably moving away from feature X'. Three teams spent the next month reorganizing. He hadn't decided. He'd thought aloud. At exec altitude, thinking aloud is policy — and the cost of the mistake is measured in person-weeks, not minutes.

Why it matters

As you climb, your time with anyone drops and your impact per word climbs. A great IC writes for one reader. An exec writes for 500. The same sentence that would be a casual note from a peer becomes a strategy from a CEO. Most exec communication failure is not malice or incompetence — it is a failure to update the bandwidth model to the new altitude.

The second compounding factor: at exec altitude, you almost never see the misinterpretations. People don't tell you when your offhand comment caused three teams to thrash. The cost is invisible to you and very visible to them. The only fix is discipline — defaults that protect the org from your own bandwidth carelessness.

repeat for retention

exec messages need 7 repetitions across 7 channels

1 sentence

becomes policy

thinking aloud at altitude reorganizes teams

60%

of strategy doc readers

stop at the first paragraph — BLUF or lose them

The exec comms stack

Five principles

1
1. BLUF
Bottom Line Up Front. State the decision, then the reasoning.
2
2. Write before speaking
Force clarity. Speech rewards confidence; writing rewards correctness.
3
3. Frequency × Channel
Important messages need 7 repeats across 7 channels (email, all-hands, 1:1, doc, Slack, video, Q&A).
4
4. Distinguish thinking aloud from deciding
Tag clearly: 'exploring', 'leaning toward', 'decided'.
5
5. Audit downstream interpretation
Ask 3 people what they think you meant. Adjust.

Speech vs writing

Pick the medium for the job

Speech is for

Charge — building emotional energy
Q&A — adjusting in real time
Trust — being seen as a human
Crisis — speed beats precision

Writing is for

Precision — every word audited
Scale — same message, same wording
Memory — auditable later
Strategy — defaults better

Tag your statements so the org knows what's policy.

Tag	Meaning	Example
Exploring	Thinking aloud. No commitment.	'Just exploring — should we kill feature X?'
Leaning toward	Probable direction, open to data.	'Leaning toward sunsetting X by Q3.'
Decided	Final, act on it.	'Decided: sunset X by July 1. Owner: Sara.'

Example

Amazon's six-page narrative memo (no slides, silent reading at the start of meetings) is exec comms infrastructure — it forces precision and makes the reasoning auditable. The memo discipline shifts the room from theatre to thinking. Bezos's annual letters are 7x-7-channel discipline at company scale; the same handful of concepts get re-stated for years until they are the operating system.

Apply on Monday

Rewrite your next big update with BLUF as line 1.
Tag every speculation with 'exploring' or 'decided' — out loud.
Plan your next big message across 7 channels, not 1 email.
Read your own messages back as if you were a junior 3 levels down.
After each town hall, ask 3 ICs what they think you said. Correct in writing within 48h.

Common mistakes

Burying the lead in story.
Treating thinking aloud as low-impact at high altitude.
Saying once and assuming it landed.
Optimizing for not sounding wrong instead of being clear.
Mixing speculation and decisions in the same paragraph.
Sending the message only through your preferred channel.

Reflection prompts

What did I say this week that someone might have taken as policy?
Which decision haven't I repeated enough times?
Where am I hiding my position to preserve optionality at others' expense?
Which channel do I systematically under-use?

Takeaways

Headline first; reasoning second.
Tag exploration vs decision out loud.
Repeat 7x in 7 channels.
Audit downstream interpretation, every time.

Visual summary

Headline first. Write before speak. Repeat 7x in 7 channels. Tag speculation. Audit downstream. Words are policy.