Why You Can't Unplug: What Your Vacation Says About Your Leadership

Ask a room of executives who among them has taken two consecutive weeks completely offline in the past year, and you'll watch the eye contact evaporate. Some will volunteer that they 'checked in a little' from the beach. A few will say, with real pride, that they handled a crisis from the plane. Almost none will say they actually unplugged — and the reasons they give are always operational. Something critical was in flight. The team wasn't ready. The timing was bad. But across hundreds of these conversations, the pattern underneath is remarkably consistent: the leader who can't unplug has usually built an organization that can't run without them, and the vacation isn't the problem. It's the diagnostic.

This matters more than it sounds, because 'I just like staying close to the work' is one of the most expensive lies in leadership. Every escalation that routes to you while you're away is data about a decision right that was never actually delegated. Every 'just keeping you in the loop' message is evidence that your team is performing visibility instead of exercising judgment. The leader who checks email from the beach isn't being diligent. They're demonstrating — to their team and to themselves — that trust in the system is conditional. And teams calibrate to exactly that signal with remarkable speed.

"Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity."— George S. Patton

The outage test

Here's the cleanest diagnostic I know: if you disappeared for three weeks starting tomorrow, what actually breaks? Not what people would complain about, and not what would be slightly worse for a while — what genuinely breaks. Most leaders can't answer this honestly on the first pass, because the honest answer is a list of names, not a list of systems. 'Sales would drift without me in the pipeline reviews.' 'The board would want to hear from me.' 'People would escalate instead of deciding.' Every one of those is a single point of failure wearing the costume of importance.

The organizations that survive leader absence have converted personal relationships into institutional mechanisms. Pipeline health lives in a dashboard and a weekly review anyone competent can run. Board communication follows a cadence with a delegated voice. Decision authority is written down — who can spend what, commit to what, decide what — so that escalation is a choice rather than the default. None of this is exotic. It's just work that never feels urgent, which is exactly why it stays undone until the leader's absence makes it a crisis.

Why teams learn to need you

The uncomfortable part is that dependency isn't something your team did to you. It's something you trained into them, one micro-signal at a time. Every time you answered a 9pm message instantly, you taught them you're always on — and that a slow reply is risky. Every time you swooped in and fixed a decision that was going sideways, you taught them that judgment above a certain threshold belongs to you. Every time you said 'loop me in' without specifying when to loop you in, you made cc'ing you the safe move. Individual behaviors, individually reasonable, compounding into a system where nobody below you owns a decision they can't verify against your preferences first.

The cruelest irony is what this does to your best people. High-agency people don't stay long in systems where their judgment is perpetually provisional. They leave — or worse, they stay and stop offering judgment at all, and you get exactly the organization you trained for: one that needs you for everything and has learned to want nothing. At that point the leader's inability to unplug has stopped being a personal habit and become a ceiling on the entire company.

The physiology of always being on

There's also a reason the compulsion feels so hard to override in the moment. Hypervigilance — the low-grade, always-scanning state of a leader who believes something will break without them — is a nervous-system state, not a character trait. It's sustained by disrupted sleep, residual stress load, and the simple absence of any recovery rhythm. And a hypervigilant brain is a worse brain: narrower attention, shorter horizon, more reactive judgment. The leader who never unplugs isn't protecting the company from risk. They're running the company's most important decisions on a progressively degraded processor and calling it dedication.

Unplugging is a capability you build, not a boundary you declare

The leaders who disconnect successfully don't have more willpower. They've done the structural work that makes disconnection safe — often years of it, compounding quietly. The sequence looks like this:

• Write down the decision rights. One page: what your directs can decide alone, what needs a conversation, what genuinely needs you. Most 'urgent' escalations die the moment this exists, because most of them were never actually yours to make.
• Assign an acting owner, not a deputy. Not 'you're covering for me' but 'while I'm out, this is yours — you decide, you don't check with me.' The difference between a placeholder and an owner is whether the decisions actually move.
• Pre-decide the exceptions. There's always one or two things that legitimately route to you — name them explicitly, name the threshold, and name the channel. Everything else gets handled by whoever is closest to it.
• Run a trial absence before the real one. Take a long weekend fully dark. Read the post-mortem of what escalated, and treat every unnecessary escalation as a delegation bug to fix, not a reason to stay connected.
• Make your re-entry boring. If you return to heroics and crisis cleanup, you've taught the team the system failed. If you return to a business that ran and a few well-documented judgment calls, you've taught it that trust was real.

And then the hardest part: actually going dark. Not 'lighter touch' — dark. Because your team can't distinguish between 'he's trusting us' and 'he's watching, just more slowly' unless the signal is unambiguous. The out-of-office message that says 'I'm fully offline until the 14th; [name] has full decision authority' is one of the most powerful culture statements a leader can make. It's a public, dated, falsifiable declaration of trust — and teams rise to meet it far more often than leaders expect.

If you've been postponing the vacation for quarters, notice what that postponement is actually telling you. It's not that the timing is bad. It's that somewhere in the system, trust was never fully installed — and that's a leadership problem with a leadership solution, one worth solving long before you actually want the beach.