Academy/The Operator's Playbook/Module 5
5

C-Suite Communication

The language partner vs. CEO vs. board. How to say "no" upward. How to say "not yet" downward. Writing for people who don't read.

16 minCore5 sections
Three audiences, three languages
01
Partner — PE language. Thesis, MOIC/IRR, comparable deals, exit multiples. Decisions in 2 sentences.
02
CEO — Operator language. P&L, customer, team, timeline. Decisions in 3–5 minute conversations.
03
Board — Governance language. Fiduciary, risk, strategy, plan-vs-actual. Decisions in 30-minute presentations.
Key idea
The 1-sentence / 1-paragraph / 1-page rule
Every update should be consumable at 3 depths. Partner reads sentence 1, stops if satisfied. CEO reads the paragraph. Board reads the page. Never write only the page — you'll lose everyone.
The Experience Bridge
Map this concept back to what you already know
In your past role
Any time you've delivered the same message to different levels — a team, a VP, and a CEO — you've already flexed register by audience. Different slide count, different vocabulary, different call-to-action.
At Red Iron Group
Same engagement, three outputs — project update for the CEO, partner memo, board deck page. The register shift is identical. The mistake is writing one format and hoping it works.
Why the skill transfers
This is one of the most directly transferable skills you have. Find the best exec-summary you've written in the past — the one that landed with the hardest audience — and study why it worked. Use the same structure for partner memos.
Scenario
Scenario practice
Setup
A project slipped by 3 weeks. Original Q2 delivery is now early Q3. You need to tell the partner. It's 11pm the night before your Friday update.
How do you open the update?
Flashcards
Flashcards
1 / 4
Prompt — click to reveal
Writing for partners — structure
Progress auto-saves to your browser. No account needed.
Academy — ValueDriverOS Training System