The Burnout Nobody Talks About: Why "Always-On" is a Liability
If your team falls apart when you take a week off, you haven't built a team. You've built a dependency.
Originally published on my Blogger site on December 15, 2025. Preserved here on Substack.
In cybersecurity, being “always on” is treated like a badge of honor.
We celebrate the CISO who responds to Slacks at 2 AM. We admire the Incident Commander who hasn’t slept in 36 hours. We confuse availability with commitment.
But here is the uncomfortable truth: “Always-on” leadership doesn’t scale. It creates a single point of failure.
I’ve seen it firsthand. The leader who jumps into every incident isn’t a hero. They are a bottleneck. And eventually, they become a liability.
The Myth of Constant Availability
Cybersecurity is unforgiving. Threats don’t respect business hours. But that reality creates a dangerous expectation: Real leaders are always reachable.
The problem isn’t the occasional late night. The problem is when intensity becomes an identity.
When a leader feels compelled to be everywhere, three things happen:
Decision Quality Degrades: You cannot make strategic decisions when your brain is in survival mode.
Teams Atrophy: If you solve every problem, your team never learns how. You are training them to be dependent, not empowered.
Strategy Dies: You become so focused on the “now” that you stop seeing the “next.”
From the outside, it looks like dedication. From the inside, it looks like a leader who doesn’t trust their own system.
Margin is a Security Control
We talk about “margin of error” in engineering. We build redundancy into our servers. We build failover into our networks.
Why do we refuse to build it into our leadership?
Burnout is the loss of margin. When a leader has no margin:
They default to familiar solutions instead of innovative ones.
They react to noise instead of signal.
They solve today’s problem at the expense of tomorrow’s resilience.
In a field that demands clarity under pressure, a depleted leader is a security risk. You are operating your brain on 100% CPU utilization, and we all know what happens to a server that runs at 100% for too long. It crashes.
Stop Being the System. Build One.
The biggest shift I see in effective leaders is this: They stop trying to BE the system.
Great leadership isn’t about how much weight you can carry. It’s about how much weight the structure can hold without you.
This means:
Designing Escalation Paths: So the Tier 1 analyst knows exactly when to wake you up (and when not to).
Trusting Ownership: Giving people the authority to make decisions, not just the responsibility to execute tasks.
Protecting Focus: Treating your attention like a finite resource, because it is.
The leaders who are least available are often the ones whose teams perform best. Why? Because the system works even when they step away.
Presence > Availability
There is a difference between being reachable and being present.
Availability is answering an email in 30 seconds while distracted. Presence is ignoring your email for an hour so you can actually listen to your Director of Engineering explain a complex risk.
When leaders never disconnect, they send a silent message to the team: Rest is weakness. Boundaries are for people who don’t care.
Over time, that culture burns out your top talent long before the hackers do. Good leaders protect their teams. Great leaders protect their own capacity to lead.
The Litmus Test
In a field obsessed with uptime, ask yourself the hard question:
If I stepped away for a week, would things fall apart?
If the answer is “Yes,” that isn’t a sign of your importance. It is a sign of your inadequacy as an architect.
The strongest leaders I know aren’t always on. They are intentional. They are disciplined. And they understand that long-term effectiveness requires self-mastery, not just endurance.
In cybersecurity, that might be the most underrated skill of all.
References
When You’re the Executive Everyone Relies On (HBR)
Why it matters: A guide for leaders trapped in the “hero” cycle and how to break it.
Eliminating Toil (Google SRE Book)
Why it matters: The engineering bible on automating repetitive work - applied here to leadership labor.
Burn-out an “Occupational Phenomenon” (WHO)
Why it matters: The official medical classification of burnout as a workplace hazard, not a personal failure.