The script that keeps the relationship and the boundary
The message arrives from two levels above you, addressed to you by name, with a line saying you're the obvious choice for this. You are a strong fit. You are also three weeks into a launch, so the truthful reply is a firm no. The difficulty is that a no to someone at that altitude can feel like it puts more on the line than three weeks of your calendar.
Most people's first impulse is to agree, only to find that agreement has diluted both commitments. The other common reaction is to forward it to your manager and hope the problem dissolves. Neither path shields the relationship, yet the relationship is exactly what matters here. According to a 2025 study by McKinsey and LeanIn, 31% of women at the entry level report having a sponsor, while the figure for men stands at 45%. A senior leader who asks for you specifically may be the sponsor you have been missing. Your aim is to turn the request down while leaving the opportunity intact for later.
1. When a person asks outright for part of your schedule
The reply that comes most easily is something like, "Of course, I'll make it happen."
What lands better: "I'd love to take part in this. The launch continues through the 20th, and it calls for my undivided attention. If this can kick off once that's wrapped up, you can count me in. If the deadline has to stay put, I can point you toward two colleagues who would fit the role well.
It works because you have welcomed the relationship while declining the timing. Leaders at a senior level read "I'm in after the 20th" as a sincere pledge. "I'll make it happen" tends to register as nothing concrete at all.
2. When a request skips past your manager
The easy path is to keep it under wraps so that nobody feels uncomfortable.
What works better: "I'm glad to look into it. Let me bring Elena into the loop so she has clarity on how my time is being allocated this month.
It works because your manager stays informed, and the senior leader never feels that they have bypassed anyone. The two of them can settle the priorities, and you come across as someone who runs their work openly and cleanly.
3. When the ask is really a favor rather than a project
The response that feels right is, "Not a problem whatsoever."
What works better: "I can make the introduction, though I can't build the deck. I'll send the introduction today."
Break the request into the piece that takes little from you and the piece that would eat up a full week. Deliver the small piece quickly. That speed is what makes a decline on the larger piece credible.
4. When you believe the request is a misstep
What feels natural: say yes and let the results teach the lesson.
What works better: "I want this to succeed and get what it needs. Frankly, I think the timing is wrong given the Q2 churn. Should you still choose to proceed, I will see it through with care. Were you to ask for my advice, I'd recommend holding off for a quarter.
It works because you share an opinion, back it with a reason, and commit to the work. The leader may act on the suggestion or decline it. Whichever way it goes, you have contributed at the level where Portland staff speak candidly to those above them.
5. When an initial refusal doesn't land
The reflex answer is, "Fine, I'll somehow make it work."
What lands better: "Got it. In that case, I need you to talk with Elena about what slips, since the launch is the commitment I can't move. I can't make that call on my own."
It works because you have stopped short of an outright refusal. You have handed the trade-off to the person who holds the power to settle it. Frequently the request quietly gets smaller before it reaches that stage.
The thread connecting all five ideas across the Portland metro
Agree with the person and decline the task, in that sequence, and tie the reply to a specific date or name. A senior leader who requested you wants assurance that you can run your own schedule, since that is what leadership looks like from two levels up.
Hold onto this one. A request like this is likely coming.