The script that keeps the relationship and the boundary
The request arrives from two levels above you, using your name, with a note saying you're clearly the person for it. You are the person for it. You are also three weeks into a launch, so the straightforward response has to be a no. The problem is that a no, when it comes from you to someone that senior, feels like it could cost far more than a few weeks.
The usual reflex is to say yes and quietly deliver a weaker version of both projects. Another instinct many people fall back on is to hand the request off to their manager and quietly hope it goes away. Neither option keeps the relationship intact, and that relationship carries real weight. According to McKinsey and LeanIn's 2025 study, 31% of women at the entry level have a sponsor, while the figure for men is 45%. A senior leader who requests you by name is a potential sponsor. What you want is to say no in a manner that leaves the opportunity still reachable.
First. A straightforward ask for your time
The tempting response: "Absolutely, I'll make it work."
The stronger response: "I want to help. Through the 20th, the launch is my priority and it needs my complete focus. If this can begin after that, I'm in. If the schedule is fixed, I can recommend two colleagues who would be a strong fit for it.
Why it works: you accept the relationship and decline the date. Leaders tend to hear "I'm in after the 20th" as a clear and binding commitment. "I'll find a way to make it work" usually comes across as having no real substance.
Second. The request that routes around your manager
The tempting response: handle it quietly so no one feels awkward.
The stronger response: "Glad to look into it. I'll loop Elena in so she can see how my time is being spent this month.
This approach works because your manager stays up to date, and the senior leader never feels managed around. The two of them can now set priorities, and you come across as someone who runs their work cleanly, which is exactly the trait leaders in Charlotte's larger organizations look for.
Agreed A request that's actually a favor rather than a project
The tempting response: "No problem at all."
The stronger response: "I can make the introduction, but I can't take on the full deck. I'll send the introduction today."
Why it works: separate the part that costs you little from the part that costs you a week. Deliver the small piece quickly. That speed is what makes declining the larger piece easy to accept.
Not now A request you think is misguided
The tempting response: agree and let it fail on its own.
The stronger response: "I want this to get what it needs. In my view the timing is wrong, mainly because of the Q2 churn in the Charlotte office. Should you decide to move forward anyway, I'll give it my best effort. If you want my advice, I'd recommend holding off for a quarter.
Why it works: you offer a view, a reason and a commitment to do the work if they proceed. The leader can take the advice or leave it, and either way you've been useful at the level where people speak candidly upward.
Final. When the first refusal doesn't stick
The tempting response: "Fine, I'll find a way."
The stronger response: "Understood. In that case, the launch is the thing that will slip, and I'd need you to confirm that with Elena. That decision isn't mine to make alone.
This approach works because you haven't turned the request down outright. You've put the tradeoff where it belongs, with the person who has the authority to decide it. In most cases the request quietly gets smaller before it gets that far.
The concept that links all five of them together
Agree to the person, decline the task, and in that sequence attach a specific date or a named colleague. A senior leader who sought you out wants proof that you can run your own calendar, since that is what leadership looks like from two levels up.
Bookmark this one The next request is probably already on its way.