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.

• 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.

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.