You don't have a boundary problem

An EA with eleven years in the C-suite posted a question last week that got 134 upvotes and 51 replies.

She supports a CEO, a COO and one more C-suite executive. Her title is just "Executive Assistant." And new employees keep reading that title as assistant to everyone, asking her to schedule their own 1:1s, book their own external calls, and coordinate meetings that involve none of the people she actually supports.

She asked two very specific things. Not "how do I cope." Not "is this normal." She asked:

"What's a polite way to say, 'I only provide scheduling support for XYZ executives' without sounding dismissive?"

and

"Has anyone found a title/signature that makes it clear you support the C-suite without listing every person individually?"

Then she added the line that explains why every piece of advice she is about to receive will fail:

"I know it's completely reasonable to redirect these requests, but I still somehow feel like a jerk every time I do it."

She already knows she is allowed to say no. She has known that for eleven years.

The problem is that she has to decide it again, from scratch, every single time, and each decision costs her something.

That is not a confidence problem. That is a design problem. And design problems have design fixes.

1. The real cost is the decision, not the task

Nobody in that thread is being crushed by the work of sending one calendar invite. Sending the invite takes ninety seconds.

What's expensive is the loop that runs before it: Is this mine? Do I push back? Will they think I'm difficult? Is it faster to just do it?

A 22-year-old PA in the same week's feed did that math out loud and landed on the only rational answer:

"It takes less time to do the task than it does to protest the work being given."

She is right. That is exactly why it keeps happening.

When refusing costs more than complying, people comply. Every time. That is not weakness and no amount of assertiveness will change it, because assertiveness doesn't change the price. It just asks you to pay it more often.

So stop trying to get better at refusing. Make refusing cheaper.

There are three ways to do that, and they are the rest of this issue.

2. Publish the scope once, so you stop defending it fifty times

The eleven-year EA's second question is the more important one, and almost nobody in the thread answered it.

Her title says "Executive Assistant." It's the only public statement of her scope, and it's ambiguous. Every awkward redirect and every jerk feeling flows from the fact that the org has to guess what she covers, and guesses generously.

You may not be able to change your title this quarter. You can change everything under it today.

Your email signature. One line, factual, no apology:

Kristy Murray Executive Assistant, Office of the CEO & COO Scheduling and inbox support for [Exec], [Exec], [Exec].

Your Teams/Slack status or profile. Same fact, shorter:

Supports [Exec] + [Exec]. For team-wide scheduling, see [link].

Your out-of-office, which is the highest-traffic document you own and the one nobody optimizes:

I'm out until [date]. For anything relating to [Exec] or [Exec], contact [name]. For all other scheduling and admin requests, [this is the route].

None of these are refusals. They are statements of fact that happen to make future refusals unnecessary. Nobody has to feel like a jerk about a signature block.

Where AI actually helps here: you do not need it to write these. You need it to stress-test them. Paste your draft in and ask for the reading you don't want:

"Here is a scope line for my email signature. Read it as a new employee who has never met me. Does it sound territorial, unhelpful or defensive? Show me the sentence that lands worst and give me three flatter alternatives."

That is the whole prompt. It takes forty seconds and it catches the tone problem that made her hesitate in the first place.

3. Build one door, so requests stop arriving through five

Scope creep is rarely a person problem. It is almost always an intake problem: the requests arrive by Slack DM, hallway ambush, forwarded email, text and calendar invite, all landing in the same undifferentiated pile, all feeling equally urgent, all requiring a personal judgment call from you.

One door fixes more of this than any conversation will.

It doesn't have to be sophisticated. Pick whichever your org already runs:

• A Microsoft Form or Google Form, two fields: what do you need, by when.
• A shared inbox or a Slack channel that isn't your DMs.
• A Planner / Asana / Monday intake board, if you already live in one. An EA in the same week's feed was asked by her incoming CEO for exactly this: visibility into staff progress without relying on email or check-ins. She correctly identified Planner as the low-friction answer for a Microsoft 365 shop. If someone hands you that brief, take it. It is a scope-definition project wearing a tooling costume.

Then the door does the work you were doing by hand:

The auto-response. Whatever the form or the shared inbox sends back, it states scope without you present:

Thanks, this has been logged. Requests relating to [Exec] and [Exec] are handled within one business day. Requests outside that scope are routed to [team/person], who'll pick this up.

The redirect, now boring. Because there is somewhere to send people, the hard conversation shrinks to one sentence you can send from your phone:

Happy to point you in the right direction. That one goes through [door]. Here's the link.

Notice what happened. You didn't say no. You didn't explain. You didn't negotiate. The system said no, and you were merely helpful about it. That is the entire trick, and it is why it works when scripts alone don't: the mechanism absorbs the social cost that was previously landing on you personally.

Where AI actually helps here: drafting the routing rules, not the feelings. Try:

"I support three C-suite executives. Requests arrive by Slack DM, email, and people stopping at my desk. Help me write intake rules that sort incoming requests into mine, not mine, and ambiguous. Give me a one-line response for each category and a rule for what makes something urgent."

You will edit it. But you'll be editing a draft instead of designing from a blank page at 4:50pm.

4. Write the access audit once a year

The thread underneath all of this showed up four separate times in one week: people being held accountable for things they have no permission to control.

One EA this week discovered at 8am that all four of her executives were in an unbooked room, that ten more people were joining at 11:30, and that there were not enough chairs. The reason: she does not have access to her executives' calendars. She spent her morning pulling interns to carry chairs into a meeting with the new CEO. Then she went online to ask whether it would be overstepping to phone the other EA and request a cc.

It would not be overstepping. But asking for a cc is a patch. The audit is the fix.

Take one page. Two columns.

Fill it in honestly. Take it to your executive as a single artifact: not a complaint, a gap analysis. Every line is either grant the access or move the responsibility. Both outcomes are wins, and neither requires anyone to have a feelings conversation.

This is also, incidentally, the most portable document you will write this year. It is a written record that you operate a step above your permissions. That is the exact evidence a promotion or a comp conversation runs on, and it is far more persuasive than any adjective on a résumé.

Robert Half's 2026 guide puts it plainly: 83% of administrative and customer-support leaders pay more for candidates with specialized skills than for those without. Designing the intake layer for a three-executive office is a specialized skill. Most people can't do it. Very few write it down.

The eleven-year EA asked for a script.

Scripts are fine. But a script is something you have to perform correctly, under pressure, on the fiftieth interruption of a Thursday. It puts the entire weight of the refusal on you, personally, every time.

A door doesn't need you to be brave. It's just where the requests go.

This week, build one of the three. Not all three.

• The scope line in your signature: fifteen minutes.
• The one door with its auto-response: an hour, less if your org already has forms.
• The access audit page: thirty minutes, and it doubles as promotion evidence.

If you only do one, do the signature. It's the cheapest, it's public, and it starts working while you sleep.

You are not bad at saying no. You have been asked to say it manually, several times a day, for years, with no tooling. That is a systems failure, and it was never yours to fix with willpower.

Go build the door.

Kristy

P.S. Want to be first to hear when the next AI Fluency for Administrative Professionals cohort opens? Join the waitlist: https://digitalzen.site/cohort#waitlist