The Best Time to Diagnose Your Team Is When You're Not There

‍

A few weeks ago, I was coaching a senior leader I'll call Alicia.

She was preparing for a much-needed vacation with her family. Flights were booked, plans were made, the dates had been on her calendar for months.

‍And yet, as we talked, she was more focused on how she'd work through it than actually enjoy it.

‍A few emails in the morning. A quick check of approvals. Maybe a call or two if something important came up.

‍Not because anyone had asked her to, but because she couldn't imagine the business functioning without her.

‍If you've ever packed your laptop "just in case," you know this feeling.

‍Many leaders approach vacation as something to survive. They create elaborate systems for staying partially available while appearing to be away. They tell themselves they're being responsible.

But here's the reframe I offered Alicia: Your vacation isn't a test of your endurance.

‍It's a test of your team.

‍And what happens while you're gone may reveal more about your leadership system than any performance review ever could.

‍The Most Valuable Data You'll Get All Year

Most leaders don't stay connected because they love working on vacation. They stay connected because they fear what might happen if they don't.

Decisions could stall.

Customers might wait.

‍Problems could escalate.

‍Someone might make the wrong call.

‍For leaders navigating rapid growth especially, this fear often develops gradually. As the organization grows, people start relying on your judgment, your approvals, and your institutional knowledge. Before long, you're involved in far more decisions than you realize.

‍The result?

You become the bridge connecting dozens of moving parts. And because the bridge has never disappeared, nobody knows what happens when it's gone.

During our conversation, I encouraged Alicia to do something that felt uncomfortable: Leave.

And I meant to actually leave.

Not "mostly leave."

Not "check in once a day."

Not "available for emergencies."

Leave.

‍Because if something slows down, gets stuck, or breaks while you're away, that's not evidence that you should have been more productive from the beach.‍ ‍

It’s information.

Maybe approvals are concentrated in one person, or decision rights aren't clear. Maybe a manager lacks the authority — or confidence — to move forward without validation. Maybe a critical process exists only in your head.

‍None of these are vacation problems — they're leadership design problems.

And your absence is often the only thing that exposes them.

Ask yourself: If you disappeared for two weeks tomorrow: Which decisions would stop? Where would people hesitate? What information exists only because you carry it? ‍

The Culture Signal You're Sending

There's another reason this matters: Your team is watching how you take vacation.

If you answer emails from Greece, they'll answer emails from Hawaii.

If you join meetings from the airport, they'll join meetings from the airport.

If you tell people to rest while demonstrating that senior leaders never truly disconnect, they will believe your behavior over your words every time.

Culture isn't built by what leaders encourage, it's built by what they normalize.

When leaders work through vacation, they often create a cycle they later wish they could break: a team that feels perpetually on call, hesitant to unplug, and unsure whether rest is actually acceptable.

Ask yourself: What are you teaching your team about boundaries through your own behavior? And what would change if they saw you fully disconnect without guilt?

To be clear, a successful vacation doesn't mean nothing goes wrong.

Things may get delayed, someone may make a decision differently than you would have, a process may reveal a weakness.

That's the point. The goal isn't proving that you're unnecessary. The goal is identifying where the organization still depends on you more than it should.

When Alicia returned, she found a mix of both.

A few decisions took longer than expected. A couple of processes revealed gaps. But the business kept moving.

More importantly, her team had stepped forward in ways they never would have if she had remained one email away.

The experience gave her something every scaling leader needs: a clearer understanding of where the system was strong, where it wasn't, and what needed to happen next.

The difference between executive teams that accelerate through the summer and those that stall isn't their dedication or workload. It’s how they define their Supportive Context. And the strongest teams aren't the ones that never encounter friction — they're the ones that can keep moving forward without waiting for one person to return.

It’s time to stop treating vacation as just a recovery mechanism for human health, but as the live-fire diagnostic tool for your leadership structure that it is.

If your organization stalls the moment you close your laptop, your leadership infrastructure is built for execution, not resilience. And building resilience starts with leaders who are willing to step away long enough to see what the system actually does.

As summer unfolds, many of us will be preparing for time away.

When you do, resist the urge to measure success by how quickly you respond from the beach. ‍

Instead, pay attention to what your absence reveals.

You may come back with something more valuable than an empty inbox: a much clearer picture of what your team needs next.

One question to leave you with: What's the clearest sign that a team has become too dependent on its leader—and have you ever discovered it the hard way?

‍ ‍