Product & Delivery · Chapter 6 of 13
Stakeholders, and saying no well
The skill named in 81% of product and 90% of delivery postings — higher than anything technical.
Stakeholder and executive language appears in 81% of product postings and 90% of delivery ones, which makes it the most-named requirement in this family by a distance. It is also the one candidates prepare for least, because it sounds like soft skill rather than method.
Saying no in a way that survives
- Never say no to the person; say no to the trade. ‘I can do that, and it means X moves to next quarter — which do you want?’ puts the decision where it belongs and is very hard to argue with.
- Make the queue visible. Most escalations are not really about urgency; they are about someone not knowing where they stand. A published list with positions and reasons removes half of them.
- Say yes to the smallest real version. Frequently the request contains a genuine need wrapped in a proposed solution. Find the need and satisfy it cheaply.
- Give the reason, once. Repeating it adds no weight and reads as defensiveness.
- Record the decision where they can see it. Half of stakeholder friction is people relitigating something they were never told was decided.
The escalation you should welcome
If someone escalates over your head, the useful response is not to defend the decision — it is to make sure the person above you has the same information you had. If they decide differently with full information, that is legitimate; they see things you do not. If they decide differently because they were told something incomplete, that is worth correcting immediately and unemotionally.
What you should not do is treat every escalation as a loss. A product manager who has never been overruled is either extraordinarily persuasive or not proposing anything contested.
Saying no in a way that survives
The skill is not refusing. It is making the trade-off visible so that the decision belongs to the person who owns the priority — which is almost never you, and which is why a flat no is both presumptuous and ineffective.
| Instead of | Say | Why it works |
|---|---|---|
| "We can't do that" | "We can. It would push the migration to Q3. Do you want that trade?" | Converts refusal into a decision, and hands it to the person entitled to make it |
| "That's not a priority" | "Here's what it would displace. Which of these matters more?" | Priorities are relative; stating what loses makes it concrete |
| "Engineering says it's too hard" | "It's about six weeks. Here's a two-week version that covers the main case" | Always bring the smaller option. A no with an alternative is a negotiation; a bare no is a wall |
| "We'll add it to the backlog" | "I'm not planning to do this. If that's wrong, tell me now" | The honest one. A backlog used as a graveyard destroys trust the moment someone checks |
That last row deserves emphasis. ‘We'll add it to the backlog’ is the most common polite no in the industry, and it is corrosive precisely because it is polite: the requester believes it is coming, plans accordingly, and discovers eighteen months later that it never was. The relationship damage is far greater than an honest refusal at the time.
The escalation you should welcome
A stakeholder escalating over your head is usually treated as a failure. Frequently it is the system working.
If someone genuinely believes their priority outranks yours, the right person to resolve that is whoever owns both priorities. That is not a conflict — it is the correct routing.
What is a failure is being surprised by it. If your manager hears about the disagreement from the other party first, you have lost control of the narrative and some credibility along with it.
So the discipline is to escalate with them: ‘we disagree, and I think that is fine — let us both take it to whoever owns the trade-off.’ That reframes it from a fight into a decision, and you look like the person who handled it well regardless of the outcome.
And accept the answer. Re-litigating a decision you lost, quietly, through delivery speed, is the single fastest way to become someone people route around.
Check yourself