Communicating Up: How to Start Speaking Like an Executive
Most product managers are fluent in one language. The C-suite speaks another. Here's how to become bilingual.
Your Jira board is immaculate, your sprint velocity is tracked, your team knows exactly what they're building and why. Then your CPO asks you to present to the leadership team on Friday, and suddenly you're drowning because everything you know how to say is wrong for that room.
This is the most common career ceiling for mid-level PMs. Not lack of execution skill. Not weak product instincts. The inability to zoom out.
Why PMs Default to the Wrong Altitude
Product managers spend 80% of their time operating at ground level. Ticket refinement, unblocking engineers, coordinating with design, triaging bugs, running standups. That's the job. And you get very good at that altitude because repetition builds fluency.
The problem is that fluency becomes a trap.
When you're asked to communicate up, you bring everything that makes you effective with your team: detail, nuance, process context, tradeoff explanations. Executives don't need any of that. They're not ungrateful, they're just operating at 30,000 feet while you're handing them a street map.
"Executives are not your stakeholders. They are your decision-makers. The difference determines everything about how you communicate."
A stakeholder needs context. A decision-maker needs clarity, confidence, and a clear ask. These require completely different communication muscles.
What Executives Actually Care About
Here's what I've observed across dozens of executive presentations, both as the PM presenting and as the person in the room watching PMs present: the C-suite is running a mental model of roughly four questions at all times.
1. Does this move the business?
They're thinking in terms of revenue, retention, market position, or risk reduction. Not features. Not user stories. If you can't connect your work to one of those four outcomes in your first 60 seconds, you've already lost the room.
2. What's the decision you need from us?
Most PMs present to inform. Executives want to be presented to for a reason. Walk in with a specific ask, approval, a resource commitment, a priority call, or you'll get a polite "keep us posted" and nothing will change.
3. What's the risk if we do nothing?
This is chronically underused by PMs. Executives are in the business of managing risk. Showing them the cost of inaction, in dollars, in competitive positioning, in customer churn, is more compelling than any feature benefit list you could build.
4. Do you have it under control?
They're not looking for perfection. They're looking for confidence and a clear point of view. If you hedge every statement and present five options with equal weight, you signal that you need them to do your job. Show them you have a recommendation and a rationale.
The Altitude Shift Framework
Before any executive communication: presentation, Slack message, QBR slide, hallway conversation, etc. run your content through this four-part filter. I call it the DICE check.
D - Decision: What decision needs to be made, and by whom?
I - Impact: What's the business impact, in numbers if possible?
C - Confidence: What's your recommendation, stated clearly?
E - Exception: What's the one risk or dependency they need to know?
That's it. Four elements. Every executive communication you send should contain all four, even if it's a single paragraph in an email.
Here's what this looks like in practice. Instead of:
*"We've been working on the onboarding flow redesign. The team finished the discovery phase and we have some findings. There are a few directions we could go and we wanted to get your input on what matters most before we commit to a path."*
You say:
"We need a call to align on the onboarding redesign direction by Thursday. Discovery showed a 34% drop-off at step three. Fixing this is projected to improve 30 day retention by 8 points. My recommendation is Option B, which we can ship in six weeks. The risk is it requires pulling one engineer from the payments team for two sprints."
Same information. Different altitude. The second version takes 20 seconds to read and contains a clear ask, a business number, a recommendation, and the one tradeoff they need to weigh.
"Don't make executives do the work of zooming out. That's your job."
Building the Muscle Before the Meeting
Most PMs only practice executive communication when they're already in the high-stakes moment. That's like running your first mile at a race.
Start small. Every week, write a three-sentence summary of your product area using only the DICE framework. No team context, no process details, no feature names. Just decision, impact, confidence, and exception. Share it with your manager and ask if it reads like something a CPO would care about.
Do this for four weeks. Your instincts will shift.
The second practice: listen to how your executives talk in all-hands meetings and leadership updates. Notice what they repeat, what language they use, what they cut. They're showing you the altitude. Mirror it.
Alignment across the organization is the PM's core superpower — but alignment only happens when you can operate at every level of it. Most PMs stop at the team. The ones who grow fastest are the ones who learn to hold the team view and the executive view simultaneously, switching between them with precision.
The Cheat Sheet: Executive Communication in One Page
“Here’s what we’ve been working on” → “Here’s the decision we need”
“There are a few options to consider” → “My recommendation is X, because Y”
“We’re making good progress” → “We’ll hit X metric by [date]”
“The team is aligned” → “We’re ready to move, we need your approval on Z”
“There’s some risk around...” → “The one risk is X, here’s how we’re managing it”
“We wanted to get your input” → “We need a decision by [date]”
“The user research showed...” → “Discovery revealed a X% drop off, costing us $”
“We’re exploring a few directions” → “We’re going with Option B, it ships in N weeks”