The script that keeps the relationship and the boundary
The message arrives from two levels above you, addressed to you personally, with a note saying you're clearly the best fit. You are the best fit. Three weeks into a launch, your honest reply is that you simply don't have the room. The problem is that a no, delivered to someone that senior, feels like it could cost you far more than three weeks of schedule.
The reflex is to say yes and then quietly deliver a weaker version of both commitments. A second instinct is to hand the request off to your manager and wait for it to vanish on its own. Neither protects the relationship, and the relationship counts: a 2025 McKinsey and LeanIn report found that only 31 percent of entry-level women have a sponsor, compared with 45 percent of men. When a leader two levels up asks for you by name, they may be becoming that sponsor. Turn the request down while leaving the door open for it to come back later.
Phase one. A straight ask for your time
Tempting: "Absolutely, I'll make it work."
Better: "I'd really like to be part of this. I'm running the launch through the 20th and it depends on me. If it can start after that, I'm in. If it can't, I can suggest two colleagues who would do well with it."
Why: you agreed to the relationship and declined the timing. Senior people read "I'm in after the 20th" as a real commitment, while "I'll make it work" sounds like nothing concrete.
Phase two. An ask that goes around your manager
It's tempting to quietly absorb it so nobody in San Francisco feels uncomfortable.
Better: "Glad to look at this. I'm going to copy Elena so she knows where my time is going this month."
Why: you kept your manager informed without making the senior leader feel managed. The two of them can now set priorities together, and you come across as someone who runs their work cleanly.
Phase three. The ask that's truly a favor, not a project
Tempting: "Happy to help, no trouble."
Better: "I can make the introduction, but not build the deck. I'll send the intro today."
Why: separate the piece that costs you almost nothing from the piece that costs you a week. Deliver the small piece quickly. Because you answered quickly, turning down the larger piece later feels natural to everyone involved.
Phase four. A request you think is misguided
Tempting: agree and let the outcome teach its own lesson.
Better: "I'd like this to get the support it actually needs." In my view the Q2 churn figures in Southern California make this a poor moment to start. If you still choose to move ahead, I'll make sure it's done properly. If you're after my recommendation, I'd hold off for a quarter.
Why: you offer a view, a reason and a clear willingness to help. Your leader is free to take that advice or leave it. In either case, you've shown the kind of candor upward that Sacramento-level leaders value.
Phase five. When your first refusal doesn't stick
It's tempting to say, "Fine, I'll find a way to make it happen."
Better: "Got it." In that case, I need you to let Elena know the launch is what would slip. That tradeoff isn't mine to make."
Why: you stopped short of a flat refusal. You placed the tradeoff with the person who has the authority to decide it. Most of the time, the request quietly shrinks before it gets that far.
The principle guiding all five moves across California.
Affirm the person first and decline the task second, and attach a specific date or a named owner to your answer. A senior leader who requested you is looking for evidence that you can steer your own schedule, since from two levels above that is what leadership looks like.
Keep this one close at hand. The request is coming.