Everyone has opinions about your product.
Executives want strategic initiatives. Sales wants features that close deals. Support wants fixes for frustrated customers. Marketing wants things to promote. Engineering has opinions about technical debt. Legal has concerns about risk.
Welcome to stakeholder management—one of the most important and least taught PM skills.
What Stakeholder Management Actually Is
Let's start with what it isn't: stakeholder management isn't about making everyone happy. That's impossible. Someone will always be disappointed.
Stakeholder management is about:
- •Keeping the right people informed at the right level of detail
- •Understanding what different stakeholders actually care about (not what they say they care about)
- •Building relationships so people trust your judgment
- •Creating alignment before you need it
- •Managing expectations so surprises are rare
Do this well, and your job gets dramatically easier. Do it poorly, and you'll spend half your time in reactive firefighting mode.
Mapping Your Stakeholders
Before you can manage stakeholders, you need to know who they are and what they want.
Create a simple map:
High influence, high interest: These stakeholders care deeply and have power. Your executives, your direct manager, key sales leaders. They need regular, detailed updates and involvement in major decisions.
High influence, low interest: They have power but aren't paying close attention. Keep them informed at a summary level. Don't let them be surprised by big decisions.
Low influence, high interest: They care a lot but can't force decisions. Customer support, some engineering leads. Give them voice and visibility, but don't let them dictate priorities.
Low influence, low interest: Keep minimally informed. Don't waste their time or yours.
The map isn't static. A stakeholder can move from low interest to high interest the moment their priorities intersect with yours.
What Each Stakeholder Actually Wants
Here's what I've learned about common stakeholder types:
Executives want:
- •To know the roadmap aligns with company strategy
- •To understand key risks and how you're managing them
- •To not be surprised in board meetings or customer conversations
- •Clear metrics and progress updates
- •You to own the problem so they don't have to
Sales wants:
- •Features that help close deals (especially enterprise deals)
- •Competitive differentiation
- •To know what's coming so they can set customer expectations
- •Quick wins they can announce to prospects
- •You to understand that their commission depends on shipping
Engineering wants:
- •Clear requirements that don't change constantly
- •Context on why things are prioritized the way they are
- •Time for technical debt and maintenance
- •To be involved in solution design, not just handed specs
- •Respect for their expertise and estimates
Customer Success/Support wants:
- •Fixes for the issues they hear about constantly
- •To know about changes before customers do
- •Documentation and training for new features
- •A sense that customer pain points are being heard
Marketing wants:
- •Things to promote and write about
- •Advance notice of launches
- •Clear positioning and messaging
- •Features that are visually impressive or easy to demonstrate
Understanding these motivations helps you communicate more effectively.
Proactive vs. Reactive Communication
Most PM stakeholder problems stem from one issue: surprises.
When stakeholders are surprised—by a delay, a cut feature, a strategic shift—they lose trust. Even if your decision was right, the surprise damages the relationship.
The solution is proactive communication:
Weekly or biweekly updates: A brief written update to key stakeholders. What shipped, what's in progress, what's coming, any risks or blockers. This takes 30 minutes and prevents hours of ad-hoc conversations.
Before decisions, not after: If you're making a significant prioritization call, tell stakeholders before it's final. "I'm thinking about deprioritizing X because of Y. Any concerns I should consider?"
Share bad news early: The moment you know a launch is slipping or a feature is being cut, communicate it. Waiting makes it worse.
Regular 1:1s with key stakeholders: Especially for high-influence people. These relationships take time to build but pay dividends when you need support.
The Art of Saying No (Again)
You will say no to stakeholders constantly. Every prioritization is a series of "no"s.
How you say no matters:
Bad: "No, that's not a priority."
Good: "I hear that this is important for closing enterprise deals. Here's the tradeoff: if we build X, we're pushing back Y and Z. Given what I know about company priorities, I'm recommending we stay focused on Y. If that's wrong, let's discuss what I might be missing."
The good version:
- •Acknowledges their concern
- •Explains the tradeoff
- •Shares your reasoning
- •Opens the door for input you might not have
Most stakeholders can accept "no" if they feel heard and understand the logic.
Managing Executives
Executive stakeholders deserve special attention because they can reshape your roadmap with a single question.
Know their priorities: What does the CEO talk about in all-hands? What's the board focused on? Align your communication to those priorities.
Speak their language: Executives care about business outcomes—revenue, growth, churn, competitive position. Translate your product work into business terms.
Be concise: Executives are time-constrained. Lead with the headline. Provide detail only when asked.
Anticipate their questions: Before any exec meeting, think: what will they ask? Have answers ready.
Own the problem: Executives don't want to be dragged into details. They want confidence that you have the situation under control.
Managing Conflicting Stakeholders
What happens when two stakeholders want opposite things?
Sales wants feature A. Engineering says it requires technical work B first. Sales doesn't want to wait.
First, understand both perspectives deeply. What's actually driving each request? Sometimes the surface conflict hides compatible underlying needs.
Second, find creative solutions. Is there a smaller version of A that doesn't require B? Can we phase the work? Is there a workaround?
Third, escalate clearly if needed. If you can't resolve it at your level, don't let it fester. Bring the tradeoff to someone who can decide, with your recommendation.
Fourth, once decided, commit. Don't relitigate. Don't undermine the decision. Move forward.
Building Trust Over Time
Stakeholder management isn't a tactic—it's a relationship.
The PMs who do this best:
- •Follow through on what they commit to
- •Are honest about uncertainty and risk
- •Give credit to others
- •Don't blame when things go wrong
- •Stay calm under pressure
- •Remember what stakeholders care about and reference it
Trust takes months to build and moments to destroy. Invest in it consistently.
When Stakeholder Management Fails
Sometimes it fails anyway. A stakeholder goes over your head. Someone's mad about a decision. Politics happen.
Don't take it personally (even when it is personal). Stay professional. Focus on the problem, not the people.
Understand what broke down. Was it a communication gap? A genuine disagreement? A relationship you should have built earlier?
Address it directly when possible. "I sense you were frustrated with the decision about X. Can we talk about what happened?" Direct conversation often defuses tension.
Learn from it. What would you do differently next time? File it away.
The Bottom Line
Stakeholder management is relationship management. It's communication. It's empathy—understanding what people care about and why.
It's also pragmatic. Good stakeholder relationships give you political capital to spend when you need it. They smooth the path for difficult decisions. They make your job more sustainable.
You won't make everyone happy. But you can make sure everyone feels heard, informed, and respected.
That's the job.
Related reading: Working with Engineers and Managing Up as a PM dive deeper into specific stakeholder relationships.