The activation rate has dropped. Sales wants another feature. Engineering has identified a dependency that could delay the roadmap.
You bring these points to your executive update. The information is accurate, the challenges are real, and the opportunities deserve attention.
But leadership still has to ask: “What are you going to do?”
The Best Executive Updates Start with a Decision
For product managers, a useful shift is to lead with the decisions you have taken, the reasoning behind them, and their expected impact. Challenges and opportunities become the context that explains your choices.
This changes what executives can evaluate. They can see how you interpret evidence, weigh alternatives, and connect product work to business priorities.
Consider a hypothetical update:
“We have decided to spend the next two weeks simplifying onboarding. We are postponing the dashboard expansion because our current evidence suggests that setup friction is preventing new customers from reaching their first useful outcome. We expect this work to improve activation and will track whether those customers subsequently return.”
That update makes several things visible: a choice, a trade-off, a hypothesis, and a plan to learn.
It also creates an opportunity for leadership to challenge something specific.
Give leadership a view into your judgment
When you consistently explain decisions, executives have more evidence of how you handle responsibility.
They can see whether you distinguish customer needs from individual requests. Whether you consider the cost of delaying other work. Whether you recognize uncertainty and know when to revisit a choice.
Over time, that visibility can help build trust in your judgment.
The credibility comes from showing how you reached a decision and taking responsibility for reviewing its consequences. Confidence alone contributes little if the reasoning is difficult to inspect.
Decision ownership should also match your authority. Report decisions you are empowered to make; present recommendations when approval is required. Amazon’s distinction between reversible and difficult-to-reverse decisions is useful here: the consequences of a choice should influence how much deliberation it receives. Amazon’s 2016 shareholder letter
A product manager can demonstrate sound judgment by saying:
“We have decided to test this with a limited group. A broader rollout depends on what we learn.”
Explain Your Decisions. Discover Your Blind Spots.
Some of the most useful work happens before the executive discussion.
Writing “We decided this because…” forces you to connect your observations to your conclusions. You may discover that a connection you assumed was strong is surprisingly weak.
Perhaps a few vocal customers shaped your understanding of demand. Perhaps you favored an initiative because the team had already invested time in it. Perhaps you selected a metric because it was easy to measure.
Return to the onboarding example. You expect simpler setup to improve retention. But why?
If customers leave because the product provides little ongoing value, removing setup steps may have limited effect. Preparing the update exposes the missing assumption: customers who reach value sooner are more likely to return.
You can now investigate that assumption, narrow the experiment, or adjust what you measure.
Three questions help:
- What would have to be true for this decision to work?
- Which parts of that explanation are supported by evidence?
- What evidence would make me change direction?
Ask these before committing, then revisit them when preparing the update. Otherwise, a polished explanation can become a justification for a choice you have already stopped questioning.
Connect the decision to the goal it serves
Every prioritization decision contains an implicit statement about what matters.
Choosing onboarding improvements over reporting functionality suggests that helping new customers reach value deserves attention ahead of serving deeper needs among existing customers.
Leadership needs to understand why that trade-off makes sense now.
Make the connection explicit:
“We are prioritizing activation because we believe it is a significant constraint on this quarter’s customer-retention objective.”
A KPI measures performance. An OKR connects an objective to measurable results. A KPI can improve without advancing the objective that currently matters most. Google’s OKR guidance emphasizes measurable key results and alignment with organizational priorities. Google re:Work’s OKR guide
Explain how the proposed work should influence the metric, and how that movement should contribute to the objective. Identify any uncertainty between those steps.
This gives executives a practical way to assess your understanding of strategy.
Make room to discover that you have the wrong goal
Sometimes the discussion reveals a more fundamental problem: the decision is reasonable, but the objective behind it is outdated, misunderstood, or never explicitly agreed.
You may be optimizing for acquisition while leadership is focused on retaining existing customers. You may have treated an executive’s passing comment as a mandate. Your team may still be pursuing a priority from the previous quarter.
A clear explanation makes these mismatches easier to detect.
“This decision assumes that improving new-customer activation remains our team’s highest priority this quarter. Does that still reflect the business need?”
The answer may require you to reconsider the work. That feedback is valuable: it can prevent further investment in a direction that no longer serves the organization.
It can also reveal a communication gap that leadership needs to address.
Make the next update concrete
For each significant decision, explain:
- The choice: What have you decided, or what approval are you requesting?
- The reasoning: What evidence and alternatives informed it?
- The trade-off: What are you delaying or accepting as a cost?
- The intended impact: Which metric and business objective should benefit?
- The uncertainty: What remains unproven?
- The review: When will you evaluate results, and what would trigger a change?
Keep expected impact distinct from observed impact. Once results arrive, return to the original reasoning and explain what held up, what failed, and what you will do next.
For your next executive update, take one decision and write:
“We decided to ___ because ___. This supports ___, at the cost of ___. We will review the decision when ___.”
Pay attention to the blank you find hardest to fill. It may reveal an unclear trade-off, an unsupported assumption, or a goal that needs confirmation.
That is where preparing the update starts improving the decision itself.
Sources and further reading
- Jeff Bezos: 2016 shareholder letter — Adapting the decision process to reversibility.
- Google re:Work: Set goals with OKRs — Measurable results and alignment with organizational priorities.
To prepare for the conversation: Explore influence conversations with DeepMirror.
