The script that keeps the relationship and the boundary
A note lands from two levels up, speaking to you directly and closing with "I know you're the right person for this." You are the right person. Three weeks into a product launch, the truthful reply is that you have no room. The difficulty is that, when the request comes from someone that senior, a no can feel as though it might cost you far more than those three weeks.
The first habit most people fall into is a yes that quietly turns into a weaker version of two projects at once. The second is to pass it along to your manager and hope it goes away. Neither protects the relationship, and the relationship counts for a great deal. According to the 2025 McKinsey and LeanIn study, 31% of women starting out in their careers have a sponsor, while the figure for men is 45%. When a boss's boss asks for you by name, they are, in effect, a potential sponsor. What you need is a way to say no that still leaves the door ajar.
1. A straightforward ask for your time
The reflex response is something like, "Of course, I'll find a way to fit it in."
What works better: "I'd like to be involved. Right now the launch runs through the 20th and cannot function without me. If this can begin after that, I'm on board. Should the schedule stay fixed, two colleagues I trust could handle this well, and I'm glad to name them.
This works because you agree to the relationship while declining the timing. Senior leaders read "I'm on board after the 20th" as a real commitment. A vague promise like "I'll make it happen" usually sounds like nothing specific at all.
2. A request that bypasses your manager
The instinct is to deal with it discreetly so no one feels uncomfortable.
A stronger reply sounds more like this: "Happy to dig into it. I'll bring Elena up to speed so she knows where my time is headed this month."
This works because your manager stays informed while the senior leader never feels handled. The two of them can now set priorities, and you come across as someone who keeps things organized.
3. A small favor dressed up as a project
The easy reply tends to be, "Not a problem whatsoever."
What works better: "I can make the introduction, though not build the deck. I'll send the introduction today."
Why it works: break the request into the part that costs you almost nothing and the part that would take a week. Handle the small piece quickly. Responding quickly is what gives you the leverage to turn down the bigger ask.
4. A request you think is misguided
The temptation is to agree and let the idea collapse by itself.
What works better: "I want this to succeed, so here is my candid view. I think the timing is off because of the Q2 churn. Should they still want to proceed, I'll carry it out with care. My advice, if you're asking, is to hold off for a quarter.
Why it works: you offer a view, the reasoning behind it, and a commitment to follow through. The leader is free to weigh that advice or disregard it. Either way, you have added value at the level where people speak honestly upward.
5. When an initial refusal doesn't stick
What feels natural: "Fine, I'll make it work."
A better response goes: "Got it. In that case, I need you to talk with Elena, because the launch is what would slip. I can't make that decision on my own."
This works because you have stopped short of a flat refusal. You have handed the trade-off to the person empowered to make it. In most cases, the request gets smaller on its own before it ever gets that far.
The thread running through all five
Accept the person but turn down the task, in that order, and anchor your answer to a particular date or name. A boss's boss who asked for you wants to be sure you can manage your own calendar, because that is what leadership looks like from two levels up.
Worth bookmarking for later. The request is coming.