The script that keeps the relationship and the boundary

The message arrives from two levels up, addressed to you by name, with a note saying you're the obvious choice for it. You are the obvious choice. Three weeks into a launch of your own, the truthful reply is that you cannot take it on. The difficulty is that declining someone that senior feels as though it could cost you far more than three weeks of schedule.

The reflex is to agree and then quietly deliver something weaker to both projects. A second instinct is to hand the problem upward to your manager and quietly wish it away. Both routes leave the relationship exposed, and that relationship matters a great deal. According to a 2025 study by McKinsey and LeanIn, 31% of women starting out in their careers have a sponsor, while the figure for men is 45%. When a senior leader requests your involvement by name, that person could become your sponsor down the line. Your reply should leave room for that.

Plan B A straightforward ask for your time

Appealing but risky: "Absolutely, I'll find a way to fit it in."

Better: "I'd like to be part of this. The launch I'm running runs through the 20th and requires my focus right now. If it can start after that, I'm in. If not, I can suggest two people who would do well."

Why: you accept the relationship and decline the timing. Executives tend to hear "I'm available after the 20th" as a credible pledge. "I'll make it work" tells them nothing firm.

2. A request that bypasses your manager

Appealing but unwise: resolve it discreetly so nobody becomes uncomfortable.

Better: "Happy to look into it. I'm going to keep Elena in the loop so she can see how my time is allocated this month."

Why: you keep your manager informed without making the senior person feel handled. The two of them can settle priorities, and you show that you run your work cleanly.

3. A request that amounts to a personal favor instead of real work on a project

Appealing, and easy to say: "Glad to help, no trouble."

More effective: "I'm glad to make the introduction, though I'm not able to put together the deck. I'll send the intro today."

Why: separate the piece that costs you almost nothing from the piece that costs a week. Deliver the small part quickly. That speed is what makes declining the larger part easy to accept.

4. A request you believe is misguided

Appealing but passive: agree and allow it to collapse without comment.

More effective: "I'd like to see this succeed and get what it needs. In my assessment, the moment is wrong because of the churn we are seeing in Q2. Should you decide to move forward anyway, I'll give it my full effort. If you're looking for my recommendation, I'd suggest holding off for a quarter.

The reason this works: you give a perspective, your rationale, and an offer to help. Whether the leader follows the advice is entirely their call. Whichever way it goes, you have proven useful at the level where people tell the truth to those above them.

5. When an initial refusal doesn't stick

Appealing but hollow: "Fine, I'll somehow make it happen."

Better: "Got it." Then the decision is whether the launch slips. I'd like you to talk that through with Elena, because I can't make that call."

Why: you have not refused outright. You have put the trade-off in front of the person who holds the power to settle it. Frequently the request loses steam on its own before it reaches that stage.

The idea that ties all five together.

Agree with the person but decline the request, in that sequence, and name a date or a colleague. A senior leader who asked for you wants to see that you can manage your own calendar, because that is what effective leadership looks like from two levels up, whether in Louisville or anywhere else.

Store this for later. Another request will probably arrive soon enough.