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 this. You are the obvious choice. Three weeks into a launch of your own, the candid response is that you simply cannot take it on. What makes it hard is that a no, to someone that senior, can feel like it might cost you more than those three weeks ever would.

The reflex is to say yes and then quietly deliver a weaker version of both projects. The other reflex is to pass it to your manager and hope it disappears. Neither one protects the relationship, and the relationship is what counts here. According to McKinsey and LeanIn's 2025 study, 31% of women starting out in entry-level roles report having a sponsor, while the figure for men stands at 45%. A senior leader who asks for you specifically may be a future sponsor. The goal is to decline in a way that leaves that door open.

1. Answering a direct request for your time

Tempting: "Absolutely, I'll make it happen somehow."

Better: "I'd love to be part of this. Right now the launch runs through the 20th and demands my undivided focus. If we can start after that, I'm in. Should the schedule prove immovable, I'm glad to recommend two colleagues who would be a strong fit for it.

Why: you agreed to the relationship and declined the date. When a senior leader hears "I'm available only after the 20th," they take it as a genuine pledge. "I'll make it happen" tells them nothing concrete.

2. Handling a request that goes around your manager

It's tempting to deal with it discreetly so that nobody feels uncomfortable.

Better: "Glad to look into it. Elena will be included so she can see exactly how my hours are being spent this month.

Why: you kept your manager in the loop without making the senior leader feel handled. The two of them can settle the priorities, and you come across as someone who keeps things organized, which is exactly what a leader in Austin's fast-moving tech and professional services scene is expected to do.

3. The request that's really a favor, not a project

Certainly, that's fine by me.

Better: "I can make the introduction, but I can't take on the deck. I'll send the introduction today."

Why: split the request into the part that takes you five minutes and the part that takes a week. Do the small piece quickly. Because that pace comes so easily, turning down the bigger commitment becomes simpler.

4. When you suspect a request is a misstep

You could agree and simply let the outcome speak for itself.

Better: "I want this to succeed. In my view, the Q2 churn is what makes this the wrong moment. If you still want to move ahead, I'll do it properly. If you're open to my recommendation, I'd wait a quarter."

Why: state a view, the reason behind it and your willingness to help. Whether to follow that advice is entirely the leader's call. In any case, you will have added value at the level where frank information travels upward.

5. If your first refusal doesn't stick

Tempting: "Okay, fine, I'll find a way."

Better: "Understood. Then I think you'll need to tell Elena that the launch is what slips. I can't make that call myself."

Why: you didn't refuse outright. You put the tradeoff where it belongs, with the person who has the authority to decide it. More often than not, the request quietly gets smaller before it gets that far.

The guiding idea behind all five points

Start by agreeing with the person, then decline the task, and close by naming a date or a person to pick it up. Someone who sought you out for a role wants proof that you can steer your own schedule, since from two levels above that is precisely what leadership involves.

Save this one. The request is coming.