Communicating with Executives
Lesson 51: Communicating with Executives
Lesson 51: Communicating with Executives
This lesson opens Module 6, shifting the curriculum's focus from the quantitative and strategic disciplines of Modules 4 and 5 toward the leadership and communication skills that determine whether all that good work actually gets understood, trusted, and supported at the highest levels of an organization. A PM can make an excellent prioritization decision (Lesson 29), design a rigorous experiment (Lesson 45), or diagnose a genuine PLG opportunity (Lesson 50) — and still fail to secure the resources or organizational support needed to act on any of it, if the communication reaching executives about that work is unclear, poorly structured, or pitched at the wrong altitude.
This lesson matters because executive communication is a genuinely distinct skill from the peer-to-peer and team-level communication this curriculum has covered so far (Lessons 37, 38, 47). Executives typically have less time, less context on the specific details of any one initiative, and a need to make a decision or form a judgment quickly — which means the communication techniques that work well in a detailed engineering discussion or a stakeholder deep-dive often fail badly with an executive audience, precisely because they weren't designed for the very different constraints that audience operates under.
Learning Objectives
- 1
Apply the "bottom line up front" (BLUF) principle to structure executive communication, leading with the conclusion rather than building up to it.
- 2
Explain the Pyramid Principle and use it to organize a recommendation with supporting arguments in a way suited to a time-constrained audience.
- 3
Adjust the "altitude" of a communication — the level of detail and abstraction — appropriately for an executive audience, extending Lesson 47's power/interest grid reasoning.
- 4
Structure a decision-focused executive update that clearly states a recommendation, the alternatives considered, the key trade-offs, and the specific ask.
- 5
Diagnose why a well-reasoned recommendation might fail to land with an executive audience, distinguishing a content problem from a structure or altitude problem.
This lesson assumes Lesson 35's Confidence Gradient and hedged-commitment discipline, since executive communication often involves exactly the kind of forward-looking, appropriately-hedged statements that lesson covered, now applied to a specific, high-stakes audience. It also assumes Lesson 47's power/interest grid, since executives typically sit in the "Manage Closely" or "Keep Satisfied" quadrants, and this lesson develops the specific communication techniques appropriate for those quadrants in much greater depth.
A note on prior context
A note on prior context
This lesson also assumes the reader is picking up mid-curriculum, following the closing lessons of Module 5 (Metrics, Experimentation & Growth) — familiarity with concepts like North Star Metrics (Lesson 42) and product-led growth (Lesson 50) is helpful context, since this lesson's examples occasionally reference explaining strategies like these to an executive audience.
Bottom Line Up First (BLUF)
Bottom Line Up First (BLUF)
The single most important structural shift for executive communication, relative to more detailed peer or team communication, is leading with the conclusion rather than building up to it. BLUF means stating the recommendation, decision, or key finding in the very first sentence or two, before any supporting context or reasoning follows. This inverts the natural instinct many people have to build a case chronologically — background, then analysis, then conclusion — which works reasonably well for an audience with time to follow the full argument, but frequently fails with an executive audience, who may only have attention for the first thirty seconds of a document or the first minute of a conversation before needing to move to a decision or the next topic.
The Pyramid Principle
The Pyramid Principle
A closely related, more formalized framework, developed by Barbara Minto for structuring persuasive business communication, organizes an argument as a pyramid: the main conclusion sits at the top, a small number of key supporting arguments sit beneath it, and detailed evidence for each supporting argument sits at the base, accessible if needed but not required reading for the top-level conclusion to make sense. The key discipline the Pyramid Principle enforces is that each level should be a complete, standalone answer at its own level of detail — an executive should be able to read only the top line and understand the recommendation, read the top line plus the supporting arguments and understand why, and only descend to the base level of detailed evidence if they want to verify or challenge a specific claim.
The Altitude Dial
The Altitude Dial
Extending Lesson 47's power/interest grid: communication with an executive typically needs to operate at a higher altitude — a higher level of abstraction, focused on decisions, trade-offs, and outcomes rather than implementation detail — than communication with a peer or a detailed stakeholder. This does not mean detail is unimportant; it means detail should be available on request (echoing the Pyramid Principle's base layer) rather than presented by default. A PM who presents the same level of granular, Sprint-level detail to an executive that they would appropriately share with an engineering team has miscalibrated the Altitude Dial — not because the detail is wrong, but because it's pitched at the wrong level for that specific audience's actual decision-making needs.
Structuring a Decision-Focused Update
Structuring a Decision-Focused Update
Combining BLUF, the Pyramid Principle, and appropriate altitude, a well-structured executive update or decision memo typically includes, in order: the recommendation stated plainly upfront, brief context establishing why a decision is needed now, the alternatives genuinely considered (not just the chosen option presented as though it were the only one), the key trade-offs involved in the recommendation, and a specific, explicit ask (a decision, a resource commitment, or simply awareness). Omitting the alternatives-considered step is a particularly common and costly gap: an executive presented with only one option, with no visible sense that other options were seriously weighed, has much less basis to trust that the recommendation reflects genuine analysis rather than a predetermined conclusion working backward to its justification.
Ready to test your product judgment?
Take the interactive practice quiz for Lesson 51 and build your skill radar dashboard.