Supporting Multiple Executives Without Burning Out

Supporting one executive is hard. Supporting two or three at once is structurally different — not because the work doubles or triples, but because the conflicts compound. Two calendars don't just produce twice the meetings; they produce conflict windows, competing priorities at the same hour of the same day, and decisions about whose problem to solve first. The admins who do this well aren't the ones who work harder. They're the ones who set the role up so that the conflicts are predictable and the resolution rules are visible.

This page covers the playbook. It's the natural sequel to the basics covered in the scheduling and meeting coordination guide, and it complements the first 90 days plan when your starting situation is "support three new leaders," not just one.

Set the Operating Agreement First

The single highest-leverage move when you support multiple executives is making the unspoken rules explicit. In the first two weeks, run a short kick-off conversation with each executive, ideally followed by one with all of them together. The questions to answer are not glamorous, but they prevent ninety percent of future conflict:

Default priority: If two of you ping me with conflicting urgent needs, who goes first by default?
Conflict windows: Are there standing meetings I should treat as immovable for each of you?
Travel rhythm: Are your travel calendars shared, so I can avoid double-booking my own week supporting two trips at once?
Communication channel: Slack, email, text? Different executives often want different channels — pick one per executive and stick to it.
Coverage: When I'm out, who covers your needs? Another admin? A peer leader? Yourself?

Write the answers down. Send them back to each executive in a short summary email — "Here's how I plan to operate; let me know if I have any of this wrong." Once they confirm, you have a document you can point to the first time priorities collide.

The Triage Protocol

When two requests land in your inbox at the same hour and both are framed as urgent, you need a fast, repeatable way to decide which one moves first. The four-question triage works in roughly the order below:

Is it irreversible? A flight that needs booking before the fare class closes is more time-critical than a meeting that can be moved tomorrow.
Does it block someone else? A request that unblocks ten other people on a deadline outranks a personal-preference request, regardless of who is asking.
What's the externality cost of being late? A board chair waiting for a confirmation outweighs an internal team waiting for the same.
What did the operating agreement say? If the rule says CEO before CFO when in doubt, follow the rule. The rule exists so you don't have to negotiate this in real time.

The triage isn't about choosing favorites. It's about applying the same algorithm consistently so neither executive ever feels like they got deprioritized arbitrarily.

Calendar Management Across Multiple Calendars

Treat the combined calendar as a single resource — yours. Both executives' meetings consume your attention, and your attention is the bottleneck.

Block your own time

Reserve recurring blocks on your own calendar for tasks that shouldn't be interrupted: morning triage, the post-lunch prep block before back-to-back afternoon meetings, the end-of-day reset. Defend these the way you defend your executives' focus time.

Make conflicts visible

When the two executives have meetings that need physical or logistical support at the same time, surface the conflict before it lands on the day. A short Friday email — "Both of you have boardroom prep at 9am Tuesday; I'll be running A's setup. B, C will cover yours" — replaces a Tuesday-morning scramble.

Stagger recurring meetings deliberately

If you have any influence over scheduling, push recurring 1:1s and team meetings into non-overlapping windows. A small structural adjustment in week three saves you from a permanent Tuesday-and-Thursday peak load.

When Priorities Genuinely Collide

Sometimes triage doesn't resolve the conflict — both requests are genuinely urgent and only one can be done first. The right move is not to pick silently and hope. The right move is to escalate transparently.

A short, specific message works:

"Both of you need the deck before 3pm. I can fully finish A's by 2pm and start B's after; B's would be ready by 4pm. If that doesn't work, can the two of you align on which goes first, and I'll execute against that?"

This is not passing the buck. It is being clear that the constraint is real, offering a specific plan, and asking for a decision only the executives can make. Done well, this approach actually strengthens your standing with both — you didn't drop anything, and you didn't make a politically charged choice on their behalf.

Common Mistakes

Trying to please both executives equally on every request. Equal effort isn't the goal — appropriate effort given the priority is. The agreement upfront gives you cover to do this.
Hiding conflicts. The conflict isn't your fault. Pretending it isn't there until the deadline lands turns a manageable problem into a crisis.
Letting the louder executive win by default. The executive who emails "URGENT" most often is rarely the one with the most genuinely time-critical needs. Triage by content, not by tone.
Skipping the operating agreement because "it'll be fine." Without it, every conflict becomes a fresh negotiation, and your executives form opinions about your judgement based on outcomes you didn't have authority to control.
Not building a coverage plan. When you take a vacation and three calendars need someone, the absence of a documented handoff is the single thing most likely to create a fire. This is what your desk manual exists for.

Peers vs. Hierarchy: A Difference That Matters

The shape of the role changes substantially depending on whether the executives you support are peers — say, two co-equal department heads — or whether one reports to the other. The work is similar; the politics are not.

When the executives are peers

Peer support is the harder configuration. Neither executive can resolve a conflict between them by simply pulling rank, which means every collision lands on your desk for adjudication. The defenses:

Rotate visible deference. If executive A's request goes first this week because of the operating agreement, make sure executive B sees a comparable win the following week. Visible fairness over time is more important than perfect fairness in any single case.
Push joint decisions to a joint conversation. When the two of them genuinely disagree on something that affects you — say, both want you on the same trip — refuse to be the mechanism of resolution. "I can plan against either decision; once the two of you align, I'll execute" is the correct script.
Keep your own credibility independent. Each executive should hear from their peers that you are reliable. If your reputation flows only through one of them, the other will quietly stop trusting you.

When one executive reports to the other

This is the easier configuration on paper and the trickier one in practice. The senior executive's requests structurally outrank the junior's, but acting that way openly damages your relationship with the junior — who is still depending on you to be effective. The right behavior is the inverse:

Make the senior's priority invisible to the junior. If the senior preempts the junior's request, you handle it; you do not announce it. The junior should experience the trade-off as schedule reality, not as deprioritization.
Protect the junior's calendar from the senior's casual asks. A senior executive forwarding a quick request "to be handled by your EA" is not always a deliberate hijack — sometimes it is reflexive. A short "I'll route through [junior executive] first" preserves the line.
Keep the junior informed about the senior's pattern. Not every detail, but enough that the junior is not surprised by a recurring claim on your time. Surprise is the corrosive thing here, not the claim itself.

The configuration that quietly fails

The hardest version is supporting two executives where one assumes seniority that has not actually been granted by the org chart. You feel the implicit pressure. The other executive does not. You will end up either consistently disappointing one of them or working evenings to disappoint neither. Neither is a sustainable position. If you find yourself in this configuration, the operating agreement conversation has to happen with both executives in the room, not separately, so the implicit hierarchy is named or denied explicitly.

Protecting Your Own Attention

The exhaustion in this role doesn't come from the volume of tasks. It comes from constant context switching. Every executive lives in a slightly different world — different priorities, different stakeholders, different vocabulary, different unspoken rules about email and tone. Switching between those worlds dozens of times a day is what burns people out.

Two practical defenses:

Batch by executive, not by task type. Spend a 45-minute block on everything for executive A — calendar, prep, email triage, expenses — before switching to executive B. The mental cost of switching is paid once, not five times.
Build a written context file per executive. Their preferences, their stakeholders, their current top three priorities. Re-read it on Monday morning. It pulls you back into their context faster than your memory will.

Knowing When the Setup Is Wrong

Not every multi-executive role is set up sustainably. If you are routinely working evenings and weekends after three months of doing the role well, the issue may not be that you're doing it wrong — it may be that the load genuinely exceeds what one person can absorb. The two questions that matter:

Are the executives' calendars actually compatible with sharing one EA, or are their travel patterns and meeting cadences forcing constant double-booking?
Is the work that's being passed to you appropriate to the role, or has scope crept into territory that should belong to a chief of staff or operations function?

If the answer to either question points to a structural problem, surface it during a formal review with concrete examples. Trying to grind through a structurally broken setup is the most common path to burnout in this role, and it rarely ends well — for you or for the executives who lose a strong admin to a problem they could have fixed.