🤝Stakeholder Management
Half your job is managing people who don't report to you. Stakeholder management is the meta-skill that makes everything else possible.
Bad stakeholder management is the silent career-killer for PMs. You can have great product judgment and still flame out because sales hates you or your VP is surprised by your launches. The skill is learnable and ignored by most PMs.
Stakeholders are not your enemies and not your bosses — they're partners with different incentives and information than you. Effective stakeholder management is about (1) mapping who matters, (2) understanding what they need, (3) communicating proactively, and (4) saying no when necessary, in their language.
The stakeholder map
Take 30 min and list everyone whose work intersects with yours:
- Above: your manager, your skip, the CPO/CEO
- Across: other PMs whose products touch yours, EM, design, marketing, sales, support, finance, legal, security
- Below: engineers and designers on your team
- Outside: key customers, partners, vendors, regulators
For each, write one line on (a) what they need from you and (b) what you need from them. This map is your operating system.
The four stakeholder communication moves
- Proactive update. Weekly or biweekly, send a short async update — what shipped, what's in flight, what you need help with. Prevents surprise.
- Aligned escalation. When you have to flag a problem, do it early and with a proposed solution. "Issue X, three options, recommending B, decision needed by Friday."
- Listen tour. Once a quarter, 1:1 with each major stakeholder. "What's working? What's frustrating? What do you wish I did differently?" Free intel and they feel heard.
- No, with reasoning. When you can't do what's asked, explain the trade-off in their language. "If we ship X this quarter, we deprioritize Y, which is the bigger revenue impact." Reframe their ask, don't just refuse.
The hardest stakeholders
Sales. Wants every feature now, often for one deal. Move: respect the revenue, demand evidence (how many deals does this block?), propose alternatives (workaround, professional services).
The CEO/founder. Wants their pet feature shipped. Move: take it seriously, do a quick 1-week discovery to validate, come back with data — almost always there's a smaller scope that achieves the founder's intent.
Other PMs. Compete for shared engineering resources. Move: establish norms around shared roadmap planning; never go around them to their EM.
Your manager. Has opinions about your work. Move: ask for feedback explicitly and often, so it doesn't accumulate into a surprise.
The proactive update template
Subject: [Team name] weekly — [date]
- Shipped this week: [bullets]
- In flight: [bullets with status]
- Coming up: [next 2 weeks]
- Asks / blockers: [help needed]
- Wins / fires: [optional]
Five minutes to write, prevents 50 questions later.
Real-world examples
PMs at Snap have historically navigated a founder (Evan Spiegel) with strong product opinions. The PMs who thrive learn to bring data and prototypes — not opinions — to founder reviews, and earn the right to make calls in their own area through demonstrated judgment.
Go deeper — recommended reading
Interview questions (1)
Q1Tell me about a time you had to manage up to a senior leader who was wrong about the product.behavioralsenior▼
STAR format.
Situation: Our CPO was pushing for a major rewrite of our onboarding flow to be 'more enterprise.' He felt the existing flow was too startup-y and was costing us enterprise deals.
Task: Either align on the rewrite or push back with evidence.
Action: I didn't argue in the meeting. I asked for two weeks to validate the hypothesis. In those two weeks, I (1) pulled win/loss data on our last 50 enterprise deals — onboarding wasn't cited as a loss reason in any of them, (2) interviewed 6 enterprise champions about their experience with our onboarding — all said it was fine, several said they preferred it being simple, (3) sized the engineering cost of the rewrite — 4 PMs and 12 engineers for a quarter.
I went back with a one-pager: data, interview quotes, cost. Proposed instead a minor tweak — adding a 'admin onboarding' subset path for enterprise IT — which solved a real but small problem at a fraction of the cost.
Result: CPO accepted the proposal. We shipped the admin onboarding in 4 weeks. Enterprise CSAT improved 6 points. The major rewrite was tabled.
Reflection: The lesson: don't argue with senior leaders. Validate the hypothesis with evidence and come back with a sharper alternative. They almost always engage with data.