← Writings
Leadership

PTO Is Not Ignorance

Good managers know what's in their queue. Being off doesn't change that.

I enjoy taking time off like everyone else. I'm not checking in every hour. I'm not hovering. I'm not available for every question that could wait. But awareness doesn't clock out. I know what tickets have come in. I know who's tried to reach me. I know my department well enough to know when something needs me and when it doesn't.

Recently, a VP ticket hit my queue during PTO. A senior leader couldn't work, and I had a few minutes of downtime. I saw it, I assessed it, and I handled it. Nobody called me. Nobody asked me to. Could my team have handled it? Yes — they were on, and I trust them. But it was a quick fix, someone senior was blocked, and I was already looking at it. Handling it myself was the fastest way to get them working again without pulling anyone off what they were doing.

That's not a failure to disconnect. That's what good leadership looks like, even when you're not at your desk.

The Invisible Work

Not everything deserves your attention on a day off. Here's how I decide.

Impact matters. A VP who can't work affects more than one person's day — decisions stall, meetings slip, and teams downstream wait. That's not politics — that's business impact. Senior relationships also take years to build and minutes to damage. When I see a VP in the queue, my mind immediately goes to triage — is the user able to work? Is it software, hardware, internet, permissions? Is my team even the right place for this? If it belongs somewhere else, I redirect them to the right person fast. Getting someone bounced around or left waiting is not an option.

Urgency matters — but not always in the way you think. Will the world end if I don't respond right now? That's the honest question. Someone can't access a CRM we don't manage — that's not urgent, that's a redirect. A user who can't open a project management tool they use once a week can wait. A user who can't open the system they're presenting to a client in an hour can't. Same problem. Different stakes. Urgency isn't always loud. Sometimes it whispers.

What This Actually Looks Like

I'm living my life — and I'm aware of my team's responsibilities while I'm away.

When I have a few minutes — waiting somewhere, downtime between plans — I'll scroll through my email and ticket queue. Not obsessively. Just enough to ask one question: is anything dependent on me? Would I be a blocker?

That's the habit. Everything else flows from it.

If the answer is yes, I figure out what I have available. I don't always bring my laptop on time off. If I'm at home and able to jump on without disrupting my day or my plans, I handle it quickly and get back to my life. If I can't, I send a quick instant message to whoever is handling it — ask if they need help, give them the context or advice they need to move forward. The work gets done. My day stays intact.

There's a difference between being on-call and being a good leader. On-call means you're reactive, tethered, waiting. Awareness means you know your organization well enough to recognize when something needs you and when it doesn't.

It's easy to get this backwards. Some leaders stay plugged into the noise — the routine tickets, the questions their team can answer, the things that could wait a week — and miss the signal. The VP who can't work. The outage nobody flagged. The thing that needed judgment, not just a response.

Away, Not Absent

There are two extremes, and both hurt a team. The leader who fully checks out leaves the team exposed — worried about making a high-stakes mistake with no one to fall back on. The leader who never checks out sends the message that the team can't function without them. Neither one is really about the team.

What I try to do sits in between. My team handles the day-to-day while I'm out, because the process works and I trust the people running it. I'm not hovering. I'm just keeping an eye on the few moments that actually need me. They handle the 99%. I make sure the 1% doesn't bury them.

That's what lets people work confidently when I'm gone. They know I'm not watching over their shoulder, and they know I won't disappear if something serious happens. My commitment to the team isn't tied to a clock or a desk.

When something matters, I handle it when I can — on my terms, not in reaction to someone else's panic. I'm not reacting to the noise. I'm absorbing the things that matter so my team doesn't have to.

PTO is not ignorance.

←swipe→