| name | stakeholder-management |
| description | Use when the user needs to manage competing priorities from different parts of the organization, communicate product decisions to leadership, handle feature requests from sales or executives, or build alignment on the roadmap. Also use when the user mentions 'stakeholder alignment,' 'managing up,' 'exec buy-in,' 'sales wants us to build,' 'how to say no,' or 'roadmap politics.' |
Stakeholder Management
Product managers don't have authority over their stakeholders. They have influence. Stakeholder management is the practice of earning and maintaining that influence through clarity, consistency, and follow-through.
The Stakeholder Map
For every major product decision, map:
| Stakeholder | What they care about | Their influence on the decision | Current stance |
|---|
| CEO / founder | Company strategy, growth | Veto power | Aligned / neutral / opposed |
| Engineering lead | Feasibility, tech debt, team health | Execution partner | — |
| Sales | Pipeline, deals, competitive gaps | Feature request source | — |
| Customer success | Retention, escalations | Voice of customer | — |
| Design | UX quality, consistency | Execution partner | — |
| Finance | Revenue, cost | Resource constraints | — |
Update this map before any roadmap review.
Saying No Without Saying No
The goal is not to say no — it is to redirect to a better outcome.
Frameworks for declining requests strategically:
-
Strategy redirect: "That's a good idea. It optimizes for acquisition, and our current bet is on retention. Here's what would need to change in our strategy for that to move up."
-
Later, not never: "We've parked that in Next/Later. Here's what it would need to beat to move up — [RICE score or priority criteria]."
-
Outcome reframe: "What outcome are you trying to drive? Let me see if there's a better way to get there with what's already on the roadmap."
-
Data ask: "I'd want to validate that this is a widespread problem before prioritizing it. Can you share 3 examples from the last 30 days?"
Managing Up
Leadership wants confidence, not updates.
Confidence = evidence + plan + risk disclosure
- Evidence: "We've validated this with 8 customer interviews and a prototype test."
- Plan: "Here's what we're building, in what sequence, and why."
- Risk: "The thing that could go wrong is X. Here's how we're managing it."
Leaders who trust the PM's process trust the roadmap. Leaders who don't trust the process micro-manage the features.
Handling Executive Feature Requests
- Receive generously: "That's interesting — tell me more about the problem you're seeing."
- Understand the job: Is this a customer request? A competitive gap? An intuition?
- Score transparently: "I'll run this through our prioritization framework and get back to you."
- Report back with data: "I scored it at RICE X. That puts it at #8 in the backlog. Here's what it's behind and why."
- Offer the tradeoff: "If you want this in Q2, here's what would need to move out."
Never just say no. Always show the trade-off.
Roadmap Alignment Cadence
| Meeting | Audience | Frequency | Purpose |
|---|
| Product review | Eng + Design | Weekly | Sprint alignment |
| Roadmap sync | Leadership | Monthly | Strategy alignment |
| Sales briefing | Sales + CS | Quarterly | Pipeline enablement |
| Customer advisory | Key customers | Quarterly | Feedback + direction |
Common Rationalizations
| Rationalization | Reality |
|---|
| "Sales doesn't understand product priorities" | Sales sees the market every day. Understand their signal before dismissing their request. |
| "I just need to explain the roadmap better" | If stakeholders keep pushing back, the issue is trust, not communication. Earn trust with evidence. |
| "Executives should stay out of the roadmap" | Executives set strategy. Strategy informs roadmap. Their input is legitimate — manage it well. |
| "I can't say no to the CEO" | You can't say no arbitrarily. You can always present a trade-off and let them decide. |
Verification
