.png){kind=small}
There is a particular kind of exhaustion that comes not from working too hard, but from working without edges. A message arrives at 10pm and you answer it. A request lands outside your remit and you absorb it. Slowly, without any single dramatic moment, the shape of the role expands to fill every available space — and you are left wondering why the job feels unmanageable when technically nothing has changed.
Boundaries are not the solution to that problem. They are the precondition for doing the job well in the first place.
For EAs and Executive Business Partners, this is a more complicated conversation than it is for most. The role is defined by proximity and responsiveness; being available, being across things, being ahead of whatever is coming next. Setting a boundary can feel like stepping back from that — like choosing yourself over your principal, which is not how most people in this profession are wired. But that framing misunderstands what a boundary actually does. A well-set boundary does not limit your availability; it makes your availability sustainable.
It helps to be precise about this before any conversation happens, because "I need to set a boundary" is not actionable. The two most common categories for EAs are working style and scope.
Working style boundaries are about how and when you work: when you are reachable, what your relationship is with out-of-hours communication, whether you take a proper break in the middle of the day. These are the boundaries most likely to come under pressure in a high-demand role, and they are also the ones most easily eroded gradually rather than broken suddenly. Scope boundaries are about what the role contains. They matter most in environments where the EA function is not well-defined, and where it is easier to say yes than to have the conversation about whether something belongs in your remit at all.
Once you are clear on the type, the next step is to articulate it plainly. Not as a preference or a complaint, but as a statement of working practice. "I step away from my phone between 7pm and 7am unless something is urgent" is a boundary. "I don't really like responding late at night" is a wish. The difference matters, both for how seriously others take it and how consistently you hold it yourself.
Every boundary needs a why, and the why that will sustain it through discomfort is rarely the surface one. It is not just that you want a lunch break — it is that without a real break in the middle of the day, your afternoon is slower, your thinking is narrower, and the quality of your work in the hours that matter most to your principal is compromised. When you can articulate the professional rationale for a personal boundary, it becomes much harder to dismiss — including by yourself.
Once you know what you are setting and why, the conversation with your principal does not need to be formal or significant. Most principals, when approached directly and without drama, are more receptive than EAs expect. What tends to go wrong is the approach: either so hedged that the boundary is never clearly stated, or so weighted with apology that it invites negotiation before it has even been heard.
Be clear about what the boundary looks like in practice. Be clear about who it affects. And where there is an obvious impact on your principal or the team, acknowledge it and suggest how it will be managed. That last part matters — it shifts the conversation from a request for accommodation to a proposal for a better way of working.
When the response is positive, the work is not finished. The boundary needs to be maintained, and it is worth building in a check-in a few months later. Working environments change, principals change, and a boundary that made sense at one stage of the role may need to be revisited. Treating it as a live agreement rather than a settled matter keeps the conversation open in the right way.
When the response is less straightforward, try to understand what is actually driving the reluctance. A hard no is rarely truly unconditional — there is usually a concern underneath it, and that concern is often more addressable than the no suggests. Could the boundary be framed differently? Could a trial period settle it? Is there a version that meets both sets of needs? These are worth exploring before accepting the outcome.
The harder part of boundary-setting is not the initial conversation. It is what comes afterwards — the moments when it would be easier to let it slip than to hold it, when the pressure is on and the boundary feels like an inconvenience rather than a principle. This is where the why earns its keep.
The EAs who are genuinely trusted over the long term are not the ones who are available at all times. They are the ones whose principals know exactly what to expect from them — and whose judgement is sound precisely because it has not been worn down by a working pattern that left no room to think.
A boundary, held well, is not a withdrawal. It is the quiet foundation of a professional relationship that can sustain real pressure, because everyone involved knows what it is built on.
Receive monthly newsletters & exclusive content.