Most product managers learn how to present.
Far fewer learn how to make an executive decision easier.
That distinction sounds semantic until you watch a senior PM walk into an executive review with 38 beautifully formatted slides, spend eight minutes explaining the research methodology, get interrupted on slide four by the CFO asking, “So how much money are we talking about?”, and discover that the rest of the meeting has abruptly become an oral examination for which PowerPoint provides remarkably little emotional support.
The PM was presenting.
A VP of Product would have been architecting the decision.
That is the real skill behind “executive communication.” It is not speaking more slowly, deleting adjectives, wearing darker clothing, or sprinkling sentences with the word strategic. Senior executives are not a separate species requiring their own dialect. They simply operate under a different information constraint: they must make consequential decisions across domains in which they usually know less detail than the people presenting to them.
Your job, therefore, is not to demonstrate how much you know.
Your job is to compress what you know into the smallest amount of information required to make a good decision—without hiding the uncertainty, trade-offs, assumptions, or unpleasant bits.
That last clause matters.
Executive communication is not simplification. It is compression without distortion.
And the difference between the two is where a great many product presentations go to die.
The C-Suite Has an Information Problem, Not an Attention-Span Problem
There is a popular caricature of executives as people capable of absorbing information only in 30-second bursts between airport lounges.
The reality is more interesting.
Executives will spend hours on a problem when the decision warrants it. What they resist is spending an hour discovering what the problem actually is.
McKinsey surveyed more than 1,200 managers and executives about organizational decision-making and found that only 20% believed their organizations excelled at it. Even more striking, 61% said at least half of their decision-making time was ineffective. McKinsey estimated that inefficient decision-making at a typical Fortune 500 company could consume about 530,000 manager-days annually, representing roughly $250 million in wages. McKinsey’s research on decision-making
There is another counterintuitive finding: speed and quality are not necessarily enemies. Respondents who described their companies as fast decision-makers were almost twice as likely to say their decisions were high quality. McKinsey’s “Three Keys to Faster, Better Decisions”
So the executive communication problem is not:
“How do I squeeze my 45-minute presentation into 15 minutes?”
It is:
“How do I structure this conversation so the organization reaches the right decision with the least unnecessary cognitive and political friction?”
That is a much more senior question.
And it changes almost everything about how you write memos and build decks.
Lesson One: Amazon Didn’t Replace PowerPoint With Memos. It Replaced Presentation With Thinking.
No discussion of executive memos can escape Amazon, so we might as well invite Jeff Bezos into the room early.
Amazon famously abandoned conventional slide presentations for important internal meetings. In his 2017 shareholder letter, Bezos explained:
“We don’t do PowerPoint… Instead, we write narratively structured six-page memos.”
Participants then silently read the memo at the beginning of the meeting. Jeff Bezos’s 2017 shareholder letter
This practice is frequently summarized as “memos are better than PowerPoint.”
That is too shallow.
The important part is what happens before the meeting.
Bezos noted that high-quality six-page memos might take a week or more to produce. They are drafted, rewritten, circulated to colleagues, revised again and then edited after time away from the document.
Why?
Because prose exposes bad thinking.
A slide can say:
Strategic Growth Opportunity
Expand ecosystem
Unlock synergies
Increase engagement
Create differentiated value
Leverage AI
Congratulations. You have written five phrases that could describe approximately 81% of Silicon Valley strategy decks since 2017.
Now try turning them into prose:
We recommend investing $4.2 million over 18 months to launch an AI-assisted workflow for mid-market customers because customer interviews indicate that setup complexity is the largest remaining barrier to activation. We estimate the initiative can improve 30-day activation from 42% to 50–54%, which would add approximately $7–10 million in annualized gross profit if retention remains unchanged.
Suddenly the writer must explain the causal chain.
What customer?
What problem?
What investment?
What metric?
What outcome?
What assumption?
That is why narrative writing is powerful. It turns intellectual fog into sentences, and sentences are irritatingly resistant to hand-waving.
Amazon’s current explanation of its product-management model shows the same discipline in its famous Working Backwards mechanism. Before funding a product or writing code, teams create a hypothetical press release and FAQ. The internal FAQ explicitly tackles questions such as:
Will this product be profitable?
Could it cannibalize another product?
Do we have the resources?
What happens if it breaks?
Why would a customer choose it?
AWS on product management and Working Backwards
That is not merely product discovery.
It is pre-emptive executive communication.
The team is answering objections before asking executives to invest scarce capital.
What a Product Leader Should Steal From Amazon
Do not copy the six-page limit religiously.
Copy the intellectual mechanism.
Before an executive review, force your argument into prose:
Context → Problem → Evidence → Alternatives → Recommendation → Economics → Risks → Decision
If you cannot write that coherently, your deck will not rescue you.
PowerPoint is many things, but a licensed therapist for confused strategy is not one of them.
Lesson Two: The Memo and the Deck Solve Different Problems
The fashionable conclusion from Amazon is that “slides are bad.”
That is nonsense.
Slides are excellent at showing:
trends,
comparisons,
financial models,
funnels,
cohorts,
customer journeys,
competitive maps,
architectures,
scenarios.
Memos are better at showing reasoning.
The mistake is asking one medium to perform the other medium’s job.
Sequoia Capital’s guidance for company boards makes this point explicitly. Its board-meeting advice notes that some companies use decks while companies including Qualtrics, Domino and Thumbtack have used Amazon-style memos. Sequoia’s conclusion is refreshingly un-dogmatic: use whatever medium communicates most effectively. Sequoia Capital’s guide to preparing a board deck
More importantly, Sequoia defines the purpose of the board material as calibration.
Board members do not live inside the company every day. Management does.
The communication artifact has to bring those two information states close enough together that board members can contribute useful judgment.
That same principle applies when a Director of Product presents to the CEO or CFO.
You have spent four months debating whether to move upstream from SMB to enterprise.
The CFO has spent four minutes thinking about it.
Your responsibility is not to replay those four months chronologically.
It is to reconstruct the minimum context necessary for the CFO to reason at your level.
That is calibration.
Use the Memo for Logic
A decision memo should answer:
What changed?
Why does it matter?
What decision are we making?
What are the realistic options?
What do we recommend?
Why?
What must be true for us to be right?
What could make us wrong?
Use the Deck for Evidence
Then show:
revenue scenario,
adoption curve,
retention cohorts,
capacity requirements,
customer evidence,
competitive position,
timeline,
sensitivity analysis.
The memo tells executives what to think about.
The slides give them the evidence to challenge the thinking.
That combination is far more powerful than either medium becoming a corporate religion.
Lesson Three: Put the Punchline First
Most product presentations are structured like detective novels.
First, some background.
Then research.
Then findings.
Then perhaps a persona.
Then the market.
Then some screenshots.
Then competitive analysis.
Then, around slide 27:
Recommendation
This structure makes sense psychologically to the presenter because it recreates how the team discovered the answer.
It makes almost no sense to an executive.
Your CEO did not attend the meeting to experience your personal journey toward enlightenment.
Start with the answer.
Bessemer Venture Partners’ board guidance recommends opening a board deck with the company’s three to five major priorities, their associated metrics, and a simple status indicator. Then show the priorities for the coming period. Bessemer’s CFO playbook for board communication
Former Oracle CFO Jeff Epstein puts the principle memorably:
“When you present to a board, tell the punchline at the beginning.”
There is a reason Barbara Minto’s famous Pyramid Principle, developed from work at McKinsey, starts with the governing idea and organizes supporting arguments underneath it. The Minto Pyramid Principle
For product leaders, that means replacing this:
“Today I’m going to walk you through our research into checkout conversion.”
With:
“We recommend delaying international expansion one quarter and moving two squads to checkout. Mobile payment failures are costing an estimated $5.8 million in annualized GMV, and our experiments indicate we can recover roughly one-third of that within six months.”
Now you have a meeting.
Everything after that sentence exists to interrogate the recommendation.
The VP-Level Executive Memo
Here is a structure I recommend for consequential product decisions.
Not every topic requires all eight sections, and that is the point. The format serves the decision; the decision does not serve the template.
1. Decision Required
One sentence.
Approve a $3.5 million FY27 investment to replace our legacy onboarding platform and migrate all new enterprise customers by Q3.
Not:
Discuss onboarding modernization strategy.
“Discuss” is where accountability goes for a little vacation.
2. Executive Recommendation
Two or three sentences.
State:
what you recommend,
why,
expected business impact.
For example:
We recommend rebuilding rather than extending the current onboarding platform. The existing architecture now adds approximately 11 engineering weeks to each major enterprise integration and contributes to a median implementation time of 84 days. We expect the replacement to reduce implementation time to roughly 50–60 days and recover its cost within 24–30 months.
Your reader now understands the argument before reading page two.
3. What Changed?
Executives need the delta.
Do not provide the history of civilization.
Explain why the issue deserves attention now.
Perhaps:
enterprise demand doubled,
churn increased,
a regulation changed,
a competitor changed pricing,
inference costs collapsed,
a key assumption failed,
engineering capacity changed,
your previous strategy worked so well that it created a new bottleneck.
Strategy is usually triggered by changed conditions.
Show the change.
4. Evidence
Use only evidence capable of changing the decision.
For example:
14 of the last 20 enterprise losses cited integration speed.
Median implementation time rose from 61 to 84 days.
Accounts activated within 45 days retain at 93%; those exceeding 90 days retain at 78%.
Engineering spends 31% of platform capacity supporting custom integrations.
Notice what is missing.
There is no slide titled “What Is Onboarding?”
Your CEO is probably familiar with the concept.
5. Alternatives
This section is where seniority becomes visible.
Weak PM:
Here is my solution.
Senior PM:
Here are three options.
VP:
Here are three options, the constraints that make each rational, the second-order effects, and why I am recommending Option B despite its disadvantages.
Try this:
Option
Investment
Upside
Downside
When It Wins
A: Patch legacy system
$900K
Fast
Technical debt increases
Demand plateaus
B: Rebuild platform
$3.5M
Structural improvement
12–15 month investment
Enterprise continues growing
C: Buy vendor
$2.2M + fees
Faster deployment
Vendor dependency
Requirements remain standard
Executives need choice architecture.
Without alternatives, you are asking for approval.
With alternatives, you are enabling judgment.
Put the Trade-Off in the Room
One of the biggest differences between mid-level and executive communication is comfort with trade-offs.
Junior communication often tries to make the recommendation look obviously correct.
Executive communication explains why reasonable people might disagree.
Suppose you want to launch an AI copilot.
Do not say:
“AI will increase customer productivity and drive engagement.”
Say:
“We expect the copilot to improve task completion by 15–25%, but inference costs could reduce gross margin by 1.8–3.1 points at high adoption. We therefore recommend launching first to the Pro tier with usage caps while we validate willingness to pay.”
Now the real question is visible:
Growth versus margin.
Other common product trade-offs include:
speed versus reliability,
growth versus profitability,
customization versus scalability,
enterprise features versus product simplicity,
platform investment versus near-term roadmap delivery,
acquisition versus retention,
automation versus control,
global consistency versus localization,
customer value versus implementation complexity.
Senior leaders expect uncertainty.
What frightens them is uncertainty that the presenter has apparently failed to notice.
Use the “What Must Be True?” Test
One of the best ways to make strategy intellectually honest is to expose its assumptions.
Bessemer describes a similar concept as a financial hypothesis: reduce an economic model to the small number of inputs that must work for the company to achieve its objectives.
Instead of presenting 47 metrics, ask:
What must be true for this investment to succeed?
For example:
At least 30% of eligible customers adopt the feature.
Adoption increases retention by at least two percentage points.
Serving cost remains below $4.50 per active customer.
Enterprise customers accept usage-based overages.
The feature does not materially increase support demand.
Suddenly the roadmap becomes testable.
You can now tell executives:
“The largest uncertainty isn’t engineering feasibility. It is willingness to pay. We propose spending $400,000 to resolve that uncertainty before committing the remaining $4 million.”
That is how capital allocators think.
And at the executive level, product strategy is capital allocation.
Managing Across: Separate Dissent From Decision Rights
Executive communication is not only upward.
The harder version is often sideways.
Engineering wants reliability.
Sales wants the enterprise deal.
Finance wants margin.
Marketing wants a launch date.
Legal would like everyone to stop having ideas.
How do you create alignment when rational people have conflicting incentives?
Netflix offers an unusually useful model.
Its published culture memo says significant decisions have an “informed captain”: one person responsible for the judgment call. Before deciding, that person is expected to seek opposing views—a practice Netflix calls “farming for dissent.” Once a decision is made, everyone commits to execution. Netflix’s culture memo
This separates three things companies constantly confuse:
Input
Many people should provide it.
Decision
Someone has to own it.
Commitment
Everyone needs to support execution afterward.
Amazon operates with a related principle: “disagree and commit.”
In his 2016 shareholder letter, Bezos argued that organizations should not wait for universal consensus and suggested that many decisions can be made with roughly 70% of the information one would ideally like. Bezos on high-velocity decision-making
His warning about unresolved conflict is particularly useful:
“‘You’ve worn me down’ is an awful decision-making process.”
Every product leader has experienced the alternative:
Meeting one.
Meeting two.
Slack thread.
Working session.
Steering committee.
Pre-steering-committee alignment meeting.
Meeting to prepare for the executive meeting.
At which point nobody remembers whether the original disagreement was about pricing or where to order lunch.
If teams fundamentally disagree, write the disagreement down.
For example:
Unresolved disagreement
Product recommendation: Launch to 100% of SMB customers in September.
Engineering position: Limit rollout to 25% until error rate falls below 0.5%.
Underlying disagreement: Product believes the cost of delayed learning exceeds reliability risk; Engineering believes current observability is insufficient to contain failures.
Decision owner: CTO.
Decision required by: August 15.
That paragraph can save three weeks of organizational interpretive dance.
Three Executive Communications Worth Studying
1. Brian Chesky’s 2020 Airbnb Memo: Strategy Before Actions
When COVID-19 devastated travel, Airbnb cut approximately 1,900 of its 7,500 employees—about 25% of the company.
Brian Chesky’s employee memo remains an unusually clear example of communicating a painful strategic decision. Read Brian Chesky’s Airbnb memo
Notice the structure.
First, reality:
Airbnb expected 2020 revenue to be less than half its 2019 level.
Then uncertainty:
The company did not know when travel would return, and it believed travel would return differently.
Then strategy:
Airbnb would refocus on its core hosting business.
Then portfolio consequences:
Transportation and Airbnb Studios would pause, while investment in Hotels and Lux would be reduced.
Then operating principles.
Then implementation.
In other words:
Reality → interpretation → strategy → choices → execution.
That sequence matters.
Without the strategy, the cuts look arbitrary.
With the strategy, people can understand the logic even if they hate the outcome.
Product leaders should use the same structure when killing products, removing features or reallocating teams.
Never say:
“We deprioritized Project Falcon because of capacity constraints.”
Say:
“We are concentrating FY27 investment on enterprise retention. Falcon primarily drives new SMB acquisition, so continuing it would consume two squads while contributing little to our highest-priority objective. We therefore recommend stopping development after the current release.”
Now the roadmap reflects strategy rather than appearing to have been attacked by a random-number generator.
2. Satya Nadella: Strategic Compression
When Satya Nadella became Microsoft CEO in 2014, he wrote:
“Our industry does not respect tradition — it only respects innovation.”
More importantly, his early communications repeatedly compressed Microsoft’s strategic direction around becoming a productivity and platform company for a “mobile-first and cloud-first world.” Nadella’s first-day Microsoft memo
You can debate the language—“mobile-first and cloud-first” contains the mathematical curiosity of having two firsts—but strategically it did something important.
It became a filter.
Good strategy communication allows thousands of people to independently answer:
Does this fit?
A product strategy nobody can repeat is barely a strategy.
3. Sequoia’s Board Structure: Highlights, Lowlights and Help
Sequoia recommends that board updates include:
highlights,
lowlights or challenges,
where management needs help,
financial performance,
sales performance,
product engagement,
product delivery,
customer experience,
roadmap and organizational issues.
The underrated item is lowlights.
Executives do not build trust by making every metric green.
They build trust by demonstrating that they detect bad news before senior management does.
A VP-level product update might say:
Yellow: Enterprise activation reached 61% versus a 70% target. The primary gap is implementation time, not product adoption after launch. We are moving one infrastructure squad to provisioning automation and expect the first measurable improvement by October.
That sentence communicates:
the problem,
magnitude,
diagnosis,
intervention,
timing.
No melodrama.
No metric cosmetics.
No “great progress with some exciting opportunities to optimize.”
Sometimes the metric is bad.
It will survive being called bad.
How to Build an Executive Deck That Doesn’t Become a Hostage Situation
A strong executive deck is usually much smaller than the appendix behind it.
Try this sequence.
Slide 1: Recommendation
A sentence, not a topic.
Bad:
Enterprise Strategy
Better:
Move 40% of FY27 product capacity to enterprise onboarding; expected payback is 18–24 months.
Slide 2: Why Now?
Three facts maximum.
What changed?
Slide 3: Economics
Show:
investment,
expected return,
range,
major assumptions,
payback period.
Do not use financial precision you do not possess.
“$13,742,219 of incremental ARR” on a three-year innovation forecast does not make you look rigorous.
It makes Excel look overconfident.
Ranges are your friend.
Slide 4: Options
Show the real alternatives.
Include “do nothing” when it is credible.
Slide 5: Customer Evidence
Not 17 quotes.
Show the two or three observations that materially change the decision.
Slide 6: Risks
Include:
probability,
impact,
mitigation,
leading indicator.
Slide 7: Decision and Next Steps
Exactly what are you asking the room to decide?
By when?
Who owns execution?
Everything else goes in the appendix.
And your appendix should be enormous if the decision is important.
This is another paradox of executive communication:
The visible presentation gets shorter as the invisible preparation gets deeper.
Prepare for Questions, Not Your Speech
When presenting to executives, your slides are not the meeting.
The questions are the meeting.
If you have 30 minutes, assume you may get five uninterrupted minutes.
Then prepare for interrogation.
For a product investment, I would expect questions such as:
CFO
What happens to gross margin?
What is the payback period?
What would we stop funding?
What assumptions drive the model?
What happens in the downside case?
CTO
What technical debt does this create?
What architectural dependency are we accepting?
What breaks at 10× scale?
Why build rather than buy?
CRO
Which segment buys this?
Has Sales validated willingness to pay?
Will it shorten or lengthen the sales cycle?
Which deals have we actually lost because we lack it?
CEO
Usually some unpleasantly simple version of:
Why now?
Why us?
Why this?
Why not the other thing?
How will we know you’re right?
If those questions frighten you, that is useful information.
It means the memo is not finished.
What Changes When AI Can Write the First Draft?
There is a 2026 wrinkle to all of this.
Writing is becoming cheaper.
Reasoning is not.
Anyone can now turn messy meeting notes into something resembling a polished strategy memo in minutes.
That makes surface professionalism less valuable, not more.
The executive advantage shifts toward:
asking the right question,
knowing which evidence matters,
identifying hidden assumptions,
understanding economics,
distinguishing reversible from irreversible decisions,
exposing disagreement,
anticipating second-order effects.
AI can make a bad strategy memo beautifully grammatical.
This is progress of a sort.
Amazon’s lesson therefore becomes even more relevant: the value of the memo is not the prose. It is the thinking required to make the prose withstand attack.
The PM of the AI era should use AI aggressively for summarizing research, testing counterarguments, finding gaps, restructuring drafts and generating scenarios.
But before presenting anything consequential, ask:
“If the CEO challenges my core assumption in the first two minutes, do I actually understand the answer?”
If not, another round of font adjustments will probably not save you.
The Executive Communication Test
Before sending your next memo or walking into an executive review, check whether an intelligent person who knows little about the project could answer these questions after five minutes:
1. What exactly is happening?
Not the project description.
The business situation.
2. Why does it matter?
Revenue?
Margin?
Retention?
Risk?
Strategic position?
Customer value?
3. Why now?
What changed?
4. What are the choices?
Real choices, not one recommendation accompanied by two straw men wearing fake moustaches.
5. What do you recommend?
Say it.
6. What must be true for you to be right?
Expose assumptions.
7. What might make you wrong?
Expose risk.
8. What do you need from the executive?
Money?
Headcount?
A decision?
Escalation?
Air cover?
Nothing is more awkward than reaching the end of an executive presentation and discovering nobody knows why they were invited.
The Real Promotion From PM to Product Executive
The transition from product manager to product executive is often described in terms of scope.
You manage more products.
More teams.
More managers.
Larger budgets.
That is true, but incomplete.
A deeper transition occurs in how you process complexity.
A PM is often rewarded for discovering information.
A senior PM is rewarded for synthesizing it.
A Director is rewarded for aligning organizations around it.
A VP is rewarded for turning ambiguity into decisions.
That is why great executive communication feels different.
It does not sound more impressive.
It sounds clearer.
The writer has already wrestled with the contradictions.
The ugly assumptions are visible.
The alternatives are legitimate.
The economics are attached.
The disagreement has an owner.
The recommendation appears at the beginning rather than emerging triumphantly after 47 slides like the winner of a corporate talent show.
Executives rarely need you to make the situation look simple.
They need you to make the complexity manageable.
That is the real purpose of a memo.
That is the real purpose of an executive deck.
And that is what “managing up” looks like when you stop thinking of it as stakeholder theatre and start treating it as one of the core jobs of product leadership:
Create the conditions in which good decisions can happen faster.
Everything else is presentation.