Tips for managing up as a product manager center on one insight: executives are not obstacles to manage around — they are stakeholders who make decisions faster and better when they have the right context at the right time, and the PM's job is to supply that context proactively rather than reactively.
Most PMs manage up poorly because they conflate it with managing around. They hide problems until they have solutions, present finished recommendations rather than seeking input, and treat executive disagreement as a political problem rather than a signal that context is missing.
Effective managing up is the opposite: transparent about problems, early with strategic decisions, and genuinely curious about what the executive knows that the PM doesn't.
The Four Managing-Up Principles
Principle 1: Proactive, not reactive. Executives should never learn about a problem from someone other than the PM. "I wanted to surface this before you heard it elsewhere" is the most trust-building sentence in the PM vocabulary.
Principle 2: Context before ask. Any request for resources, prioritization change, or executive support should come after — not before — explaining the context that makes the request necessary. Executives who understand why are easier to align than executives being asked to approve something they don't understand.
Principle 3: One-page writing. Executives make dozens of decisions per day. A one-page brief with the situation, the decision needed, and the recommendation is more likely to get quality attention than a 15-slide deck.
Principle 4: Respect executive time by front-loading the ask. In verbal briefings, state the recommendation first ("I'd like your input on X") and then provide context. Executives who hear 10 minutes of context before learning what they're supposed to do often make worse decisions because they're processing the context through the wrong lens.
The Weekly Executive Communication Ritual
H3: The One-Page Weekly Update
According to Lenny Rachitsky's writing on PM-executive communication, the most effective PMs he observed sent a weekly one-page written update to their executive stakeholders covering: what shipped, what the key metrics show, what's coming next, and one item that needs executive attention. "The executives who were least involved in day-to-day product decisions were the ones whose PMs sent this update consistently. The executives who micromanaged were almost always the ones who felt they had to ask to find out what was happening."
Template:
Weekly Product Update — [Date]
SHIPPED THIS WEEK:
- [Feature/milestone and its expected impact]
KEY METRICS (vs. prior week):
- [North star metric and 2-3 leading indicators]
COMING NEXT:
- [What ships next sprint and its expected impact]
NEEDS YOUR ATTENTION:
- [One item requiring executive input or awareness]
This update prevents surprise. Executives who are never surprised are easier to get alignment from when you need it.
Navigating Executive Disagreement
The most important managing-up skill is disagreeing with an executive productively.
The Framework for Principled Disagreement
When an executive pushes for a product decision you believe is wrong:
Step 1 — Understand before disagreeing. Ask: "Help me understand your thinking here. What are you most concerned about?" This is not stalling — it often reveals information the PM didn't have that changes the PM's view.
Step 2 — Acknowledge the legitimate concern. "I think the underlying concern about X is valid. Here's my worry about this approach to solving it."
Step 3 — Propose the test. "What data would change your view? And what data would change mine?" This moves the disagreement from opinion to hypothesis.
Step 4 — Commit or escalate. If the executive overrides after genuine dialogue, commit to executing it well. If the stakes are high enough that you cannot commit in good conscience, escalate to your manager — not around the executive.
According to Shreyas Doshi on Lenny's Podcast, the PMs who earn the most executive trust are those who push back clearly, propose tests rather than just objections, and execute the decision fully even when they disagree. "The worst outcome is the PM who half-heartedly implements a decision they opposed. It guarantees a bad result that no one can learn from."
Aligning Executives on Roadmap Decisions
H3: The Roadmap Briefing Template
Before any major roadmap decision that requires executive alignment, circulate a one-page brief:
Decision: [What we need to decide]
Background: [2-3 sentences of relevant context]
Options: [A, B, C with one-sentence pro/con each]
My recommendation: [Which option and why]
What I need from you: [Input / alignment / resources]
Timeline: [When we need to decide]
Send this 48 hours before any meeting where the decision will be discussed. Executives who come to the meeting having read the brief are ready to decide, not ready to hear about the decision for the first time.
H3: The Outcome vs. Output Frame
Executives respond to outcomes (revenue impact, retention improvement, risk reduction), not outputs (features shipped, tickets closed). Every roadmap brief should answer "what business outcome are we betting this achieves?"
According to Gibson Biddle on Lenny's Podcast, the most common PM communication failure with executives is leading with feature descriptions rather than business outcomes. "An executive doesn't care that you shipped a new dashboard. They care that the dashboard reduced weekly support contacts by 30 percent, freeing CS capacity for higher-value work. That's the sentence that gets you resources for the next feature."
FAQ
Q: What are tips for managing up as a product manager? A: Be proactive — surface problems before executives hear them elsewhere. Lead with context before the ask. Send a weekly one-page written update. Disagree by proposing tests rather than objections, and commit to executing decisions fully even when you disagree.
Q: How do you influence executives as a product manager without direct authority? A: Build trust through transparency and predictability. Frame decisions in business outcome terms, not feature terms. Send pre-read documents before decision meetings. Show that you understand their concerns before asking them to accept yours.
Q: How do you disagree with an executive as a PM? A: Understand their concern before disagreeing, acknowledge the legitimate concern, propose a test or data that would change both views, and then either commit fully or escalate through your manager — never half-heartedly implement a decision you opposed.
Q: What should a PM weekly executive update include? A: What shipped this week and its expected impact, key metrics versus the prior week, what is coming next sprint, and one item needing executive attention. Keep it to one page and send it consistently.
Q: How do you get executive alignment on a roadmap decision? A: Send a one-page brief 48 hours before the meeting covering the decision, background, options with pros and cons, your recommendation, what you need from them, and the timeline. Frame every option in terms of business outcomes, not features.
HowTo: Manage Up Effectively as a Product Manager
- Send a weekly one-page written update covering what shipped, key metrics, what is coming next, and one item needing executive attention to prevent surprise and build trust through predictability
- Frame all roadmap requests and updates in business outcome terms — revenue impact, retention improvement, risk reduction — rather than feature descriptions
- Send a one-page decision brief 48 hours before any meeting requiring executive alignment covering decision, background, options, recommendation, ask, and timeline
- When disagreeing with an executive, ask about their underlying concern before stating your objection, acknowledge the legitimate concern, and propose a test or data that would change both views
- Execute executive decisions fully even when you disagree, or escalate through your manager before the decision is made — never half-heartedly implement a decision you opposed
- Surface problems proactively before executives hear them elsewhere, framing them with the context you have and the action you are taking