There’s a specific kind of frustration I hear from high-performing leaders, especially women in expanded-scope roles:

You protect your team’s boundaries.

You encourage them to log off.

You model “reasonable hours.”

And then you go home… and keep working.

Not because you don’t believe in balance.

Because your job includes a whole category of invisible work that doesn’t fit neatly into business hours—and no one has helped you name it, share it, or design support around it.

Let’s talk about the impossible math of “work-life balance” when your team has it—and you don’t.

The Taboo Truth: You’re Not Resentful Because You’re a Bad Leader

You’re resentful because you’re tired.

And because you’ve been carrying weight that doesn’t show up on a calendar invite.

Here’s what I want to normalize:

✦ Wanting your team to have balance is good leadership.

✦ Feeling resentful when you don’t get the same is a signal, not a character flaw.

✦ The issue isn’t that you care about boundaries.

✦ The issue is that you’re pretending your workload is the same as theirs.

It’s not.

And that doesn’t make you “above” them. It makes your work structurally different.

Leader Load vs. Team Load

This is the framework I use with senior leaders who are navigating bigger scope roles (and quietly wondering if they’re doing 'it' wrong).

Team Load

Focused, bounded, task-oriented work that can (ideally) be completed within work hours.

It’s visible. It’s schedulable. It has edges.

Leader Load

The invisible work.

The unscheduled work.

The emotional and strategic labor that keeps the mission moving forward — even when nothing on your calendar says “carry this.”

Leader Load often looks like:

✦ Holding the full context of competing priorities (and absorbing the tension)

✦ Preparing for stakeholder conversations you can’t “wing”

✦ Risk scanning: “What breaks if we choose this?”

✦ Managing the emotional weather of the team (especially through change)

✦ Making decisions that don’t come with clean data

✦ Being the escalation point, even when you don’t want to be

If you’re measuring yourself by your team’s definition of “done,” you’ll always feel like you’re failing.

Because your work doesn’t end when the last task is checked off. It ends when the system is stable enough to run without you.

And that’s the part we need to name.

You’re not a hypocrite for working more than your team.

You’re carrying a different kind of weight.

Step 1: Name It (stop pretending the load is equal)

This is the moment that changes everything:

Your workload isn’t the same as theirs.

Not morally. Not emotionally. Structurally.

That doesn’t mean you accept overwork as the price of leadership.

It means you stop using your team’s rules as the yardstick for your role.

Try this prompt (and be uncomfortably honest):

“What am I carrying right now that no one else sees?”

Then list it. Not in a poetic way — in a concrete way.

Example:

• “I’m holding the decision path for a reorg.”
• “I’m managing a performance situation with legal risk.”
• “I’m prepping for exec alignment while shielding my team from churn.”
• “I’m the only one who sees the full stakeholder map.”

When you name it, you can work with it.

When you don’t, it quietly owns you.

Step 2: Different Boundaries, Not Better Boundaries

Most boundary advice is built for Team Load.

“Don’t check email after 6.”

“Turn off notifications.”

“Block focus time.”

Helpful—but incomplete.

Because Leader Load doesn’t disappear when you silence Slack. It just moves into your brain.

So instead of “better boundaries,” you need leader-level boundaries that match the kind of load you carry.

Here are three that work in real leadership life:

1) Decision Windows

Not “I’ll get to it tonight.”

But: “This decision gets a 20-minute window tomorrow at 11.”

Leader Load expands to fill open space. Time-boxing is containment.

2) Containment Language

Instead of: “Sure, send it over.”

Try: “Send your recommendation and what you need from me. I’ll respond by Thursday.”

You’re not being cold. You’re creating a system.

3) No-Default Escalation

If you’re the automatic solution, your nights will always belong to other people’s urgency.

Make escalation a process, not a personality trait.

Step 3: Get Leader-Level Support (your team has you—who has you?)

This is the part leaders skip because it feels indulgent.

It’s not indulgent. It’s structural.

Your team has access to you for support, context, coaching, and decision-making.

Who do you have?

✦ A peer you can reality-check with (not a “vent buddy,” a strategic partner)

✦ A manager you can renegotiate scope with (yes, even if it’s awkward)

✦ A coach or advisor who helps you sort signal from noise

✦ A clear forum where decisions are shared, not privately carried

If the only container for your Leader Load is “your brain after dinner,” the system will keep charging you interest.

A reframe to take with you this week

That’s not weakness. That’s leadership design.

One small next step:

Pick one:

1. Write down your Leader Load list (10 minutes).

2. Choose one containment boundary you’ll use this week (a decision window, a deadline, or a recommendation requirement).

3. Identify one support gap and fill it (even if it’s a single conversation).

If you want a deeper dive into leader-level boundaries (the kind that hold under real pressure), reply and tell me which part of your Leader Load is currently the loudest: decisions, people, stakeholders, or constant ambiguity.

To your sustainable leadership,

Alli

P.S. Know another leader carrying this question quietly? Forward this along.