Executive communication is one of the most valuable skills a product manager can develop. The same project can be funded or killed, accelerated or slowed, expanded or scoped down based on a single 15-minute update to a VP. Most PMs know this in the abstract, but the day-to-day craft of talking with executives, sponsors, and department heads is rarely taught explicitly.
The previous post in this series covered four principles for productive communication in general. This article applies those principles to a specific audience: decision makers. They sit in a different context than individual contributors, and effective communication with them is less about saying more and more about saying less, in the right order, at the right altitude.
The three layers below build on each other. First, understand what decision makers actually need from you. Second, structure information so they can act on it quickly. Third, avoid the common pitfalls that make even well-meaning updates land badly.
Understanding What Decision Makers Need
Executives, sponsors, and department heads operate in a context that individual contributors rarely see directly. They allocate scarce resources across competing priorities, make decisions in areas where they cannot be the deepest expert, and answer to their own stakeholders for outcomes far beyond any single project. To communicate with them well, you have to start with their context, not yours.
The context executives operate in
Decision makers do not have the bandwidth to absorb everything you know. A VP managing several teams might have 15 minutes to understand the status of your project before their next meeting. That is not disinterest. It is the reality of the role. Your communication should respect that constraint by being concise and focused on what they need to act on.
The information they actually care about is narrower than most PMs assume.
| Information type | Why it matters to them |
|---|---|
| Progress against the plan | Are we on track to deliver what we promised? |
| Resource use | Are we using scarce people and budget effectively? |
| Major risks and blockers | What could derail success, and how are we responding? |
| Decisions that need their input | Where do they need to provide direction or approval? |
| Changes from the original plan | What is different from what we expected, and why? |
Notice what is missing from that list. Detailed task breakdowns, minor technical decisions, day-to-day operational details, and background context they already have do not belong in executive updates. If something fits in any of those buckets, it belongs to the team, not to the executive.
Calibrating information volume
You almost always know more about your own work than the decision maker does. That asymmetry creates a communication challenge: you have to select what to share from a large body of information. Three mistakes show up again and again.
- Over-sharing: Burying the important point under so much detail that the audience cannot find it.
- Under-sharing: Assuming the audience already knows something they do not, which leaves gaps in understanding.
- Wrong altitude: Giving operational detail when the audience needs a strategic overview, or vice versa.
A useful analogy is news editing. If a reporter put every piece of source material into the article, no one would read it. The editor distills what is essential into a headline and a lead paragraph. When you report to decision makers, edit the same way: what does this person need to understand and act on in 15 minutes?
Structuring Information for Decision Speed
Decision makers are paid to decide quickly, which makes structure as important as content. The default order many people use, building toward a conclusion, feels natural in many settings. It tends to work poorly in executive communication, however, where attention is short and the audience needs to act fast.
The Pyramid Principle: conclusion first
The Pyramid Principle, developed by Barbara Minto during her time at McKinsey, inverts the default order. State the conclusion or key point first, then provide the supporting detail. This feels unnatural to many people, who prefer to walk through their reasoning before landing on a recommendation. To decision makers, however, conclusion-first is much more effective.
Consider the contrast. Instead of this:
“Last month we ran user research and noticed some interesting patterns. Users mentioned difficulty in the onboarding flow, and our analytics showed a 40% drop-off at step three. We explored several solutions and the team discussed options. After considering the trade-offs, we believe we should redesign the onboarding flow.”
Try this:
“We recommend redesigning the onboarding flow to address a 40% drop-off at step three. User research confirmed this is a major friction point. The redesign would take about three weeks.”
The second version lets the decision maker grasp the proposal immediately. If they want more detail, they can ask. If not, you have communicated efficiently. The structure works the same way as the inverted pyramid in journalism, where the most important information appears at the top and the supporting detail follows in decreasing order of importance.
A consistent status update structure
For recurring status updates, a consistent format helps decision makers find what they need quickly. They learn where each piece of information lives, which means they spend less effort decoding the update and more effort responding to it.
| Section | Content |
|---|---|
| Summary | One or two sentences on overall status (on track, at risk, blocked) |
| Progress | What has been accomplished since the last update |
| Plan | What is planned for the next period |
| Risks and blockers | Issues that could affect success, and how they are being addressed |
| Decisions needed | Items that require the decision maker’s judgment or approval |
The format is less important than the consistency. A team that uses the same structure week after week trains its executives to scan for the right information in seconds.
Visual summaries
Some information is faster to convey visually than in prose. A simple chart showing progress over time, a diagram showing dependencies, or a table comparing options can communicate in seconds what paragraphs of text cannot.
| Information type | Effective visual format |
|---|---|
| Progress over time | Timeline or Gantt chart |
| Comparing options | Table with consistent criteria |
| Dependencies and relationships | Diagram or flowchart |
| Risk assessment | Matrix (likelihood by impact) |
| Resource allocation | Pie chart or stacked bar chart |
The goal is not to make the visual look polished. The goal is to make it understandable quickly. A subway map is a useful reference here: it does not faithfully represent geography, but it lets passengers see where to board, where to transfer, and where to exit at a glance. Visual summaries in executive reports should follow the same principle, optimizing for fast comprehension over precision.
Common Pitfalls to Avoid
Most executive communication failures cluster into a few predictable patterns. The pitfalls below show up across companies and seniority levels, and most of them have a simple signal you can watch for.
Detail overload
When operational detail crowds out the information executives actually need, the update fails regardless of how well-prepared you are. Decision makers do not need to know every design iteration, every bug fix, or every meeting. They need to know whether the project is on track and what needs their attention.
The signals are usually clear. Eyes glaze over mid-update. The audience interrupts with “what’s the bottom line?” The update runs significantly longer than the time allotted. The key point gets buried under supporting information. If any of these happen, cut detail, not summary.
Bringing decisions at the wrong altitude
Decision makers should make decisions that match their level: strategic direction, resource allocation, major trade-offs. Decisions that belong to the team, including implementation details, priorities within an agreed scope, and technical approach, should not be brought to them. Asking executives to weigh in on team-level decisions wastes their time and signals that the team is not confident in its own scope.
| Belongs to the decision maker | Stays with the team |
|---|---|
| Should we pursue this market opportunity? | Which API library should we use? |
| Can we delay launch by two weeks to fix quality issues? | Should this button be blue or green? |
| Can we add an engineer to this project? | How do we split work across the existing team? |
| Does this strategic pivot align with company direction? | What is the best way to implement this feature? |
A useful test: if a peer team would handle this kind of decision without escalating, your team should too.
The no-surprises rule
Decision makers dislike surprises, especially negative ones. A project that has been reported as “on track” for weeks should not suddenly become “three weeks delayed” without warning. By the time a surprise lands, the decision maker has lost the chance to help.
If you see a problem developing, surface it early, even without a solution in hand. Decision makers can often remove blockers or reset expectations when they hear about an issue in time. They cannot help once it has become a crisis. Early-warning language gives them a chance to engage:
- “I want to flag a potential risk we are monitoring…”
- “This is not a blocker yet, but I am concerned about…”
- “We are on track assuming X, but if X does not happen by Y, we may need to discuss alternatives…”
This kind of phrasing keeps the executive informed without overreacting. It treats them as a partner in managing risk, not an audience to be protected.
Passive vs proactive reporting
There is a difference between telling decision makers about a problem and expecting them to solve it. The first version below tells the executive there is a problem. The second version brings the problem and a recommended path forward together.
| Passive | Proactive |
|---|---|
| “Design is behind schedule and that has created a blocker.” | “Design is behind schedule and we are at risk of delay. I talked with the design lead and we found two options: scope down a specific feature, or push launch by one week. I recommend scoping down because [reason]. Any concerns with that approach?” |
The proactive version shows ownership and gives the decision maker a clear path to choose. Handing them a decision is different from handing them a problem.
A navigation app makes the same trade-off. “There is an accident ahead” alone leaves the driver to figure out what to do. “There is an accident ahead. Two detours are available. Route A adds 10 minutes but is reliable. Route B is unpaved. I recommend Route A.” lets the driver decide in seconds.
Conclusion
Effective executive communication comes down to three layers. Understand the context decision makers operate in, including the narrow band of information they need and the time pressure they face. Structure that information for decision speed, leading with the conclusion and using consistent formats and visuals where they help. Avoid the common pitfalls, especially detail overload, bringing decisions at the wrong altitude, surprising people late, and reporting passively rather than proactively.
These skills are outward-facing. The next post in this series turns inward, to the team trust and collaboration patterns that make the work behind these updates possible in the first place.
Leave a Reply