The script that keeps the relationship and the boundary
The message arrives from two levels above you, by name, with a line saying you're clearly the right person for it. You are the right person. Three weeks into a launch, you're already stretched, so the candid answer here is a no. The difficulty is that declining someone that senior feels like it could cost far more than three weeks of your time.
The usual reflex is to say yes and then quietly deliver a weaker version of both projects. The other common reflex is to forward it to your manager and hope the problem disappears. Neither one protects the relationship, and that relationship counts for a lot: McKinsey and LeanIn's 2025 report found that only 31% of entry-level women have a sponsor, compared with 45% of men. A senior leader who asks for you personally is a sponsor in the making. Turn the request down in a way that still leaves room for a future yes.
1. The straightforward ask for a slice of your schedule
The eager reply you might be tempted to give: "Of course, I'll find a way."
The more useful reply: "I'd like to be involved in this." I'm running the launch through the 20th and it needs my attention. If we can begin once that window closes, then I'm on board. If the schedule is fixed, I can recommend two colleagues who'd be a strong fit.
Why it works: you're saying yes to the relationship and no to the date. Executives tend to hear "I'm on board after the 20th" as a firm commitment. "I'll make it work" reads as an empty one.
2. The ask that goes around your manager
The tempting response: keep it under wraps so nobody feels put on the spot.
The better response: "I'm glad to review it." I'll loop Elena in so she can see how my time is being spent this month.
This approach succeeds because your manager stays in the loop while the senior leader never feels managed around. The two of them can settle the priority, and you come across as someone who runs things cleanly, the kind of professional Baltimore's major employers, from Johns Hopkins to T. Rowe Price, tend to promote.
3. The ask that is actually a small favor rather than a project
The tempting answer: "Happy to help with that."
The better answer: "I'm able to set up the introduction, though I can't put together the deck." I'll send the introduction today."
Why it works: divide the request into the part that costs you almost nothing and the part that costs a week. Deliver the first quickly. That speed is what makes the no on the second part easy to accept.
4. The request you suspect is headed for trouble
The tempting move: agree and allow it to collapse without comment.
The better move: "I'd like to see this succeed." In my judgment, the Q2 churn makes this a poor moment to proceed. Should you decide to move forward anyway, I'll make sure it's handled properly. If you're asking what I'd advise, I'd recommend holding off for a quarter.
This works because you bring a perspective, the reasoning behind it, and a clear commitment. Whether to heed that advice rests entirely with the leader, who may also decline it in Columbia or Towson. In both cases you've added real value at the level where candor travels upward.
5. What to do when the first refusal doesn't stick
The tempting reply: "Fine, I'll make it work."
A stronger answer is: "Got it. At that point, make sure Elena understands that it's the launch that will have to give way. That's a tradeoff I'm not in a position to decide alone."
This succeeds because you haven't flatly refused. You've handed the tradeoff to the person who holds the authority to settle it. Quite often, the request quietly gets smaller before it reaches that stage.
The idea underpinning all five
Agree to the person but decline the task, in that sequence, and tie it to a date or a name. A senior leader who requested you wants proof that you can run your own calendar, since from two levels up that is exactly what leadership looks like.
Save this for later. The next request is coming.