We can never take time off.
I’ve said that sentence out loud more times than I can count, and every time I say it to another business owner, they nod before I get to the end of it. It’s not a complaint. It’s just the arrangement. When you’re the one everything runs through, there is no version of a week where nothing runs through you.
The problem isn’t that we don’t book the time. We book it. We get on the plane. The problem is what the time actually contains once we’re in it.
Time off that isn’t time off
Here’s what a break looks like when you’re always on call.
You go. You’re somewhere else. And you check your phone at breakfast, because there’s a decision someone might need. Then you check it again mid-morning, because the first check turned up something you now have to think about. By the afternoon you’ve had two conversations you’d have had at your desk, except you had them standing in a doorway so nobody could hear.
Nothing has gone wrong. That’s the part that’s hard to explain. On paper the week was fine. But you never actually left, because leaving isn’t geographic. Leaving means the business does not need you for a period of time, and if it needs you, you’re at work — whatever the view is.
The most honest description I have is that I’ve had time away. I’ve very rarely had time off.
Even with cover
The obvious answer is cover. Get someone to hold it while you’re gone. We’ve done that.
And the truth is that even when we have someone taking care of things while we’re away, we’re worried the whole time. Not because the person is bad at it. Because everything they’re holding is being held by someone for whom it isn’t a life’s work. They’re doing their honest best with a set of things they inherited on Tuesday.
If you ask me who I’ve genuinely been able to rely on over all these years, I have to give you the honest answer, and the honest answer is no one.
I want to say that carefully, because it isn’t bitterness and it isn’t a complaint about anybody in particular. We still believe in the best of people. We hire on that basis and I’d hire on that basis again tomorrow — you want the speed of trust, and moving slower than that isn’t really running a business, it’s auditing one. We also have a three strikes rule, which exists precisely because we start by assuming the best. It’s the thing that holds us to a limit when we’d otherwise keep extending one.
But here’s the structural part, and it took me an embarrassingly long time to see it as structural rather than personal: unless you’re an owner, you don’t carry the risk. You can’t. The downside isn’t yours. If it goes wrong, it goes wrong on somebody else’s balance sheet and somebody else’s sleep.
That is not a criticism of anyone’s character. Some of the people who’ve held things for us were good at it and cared about it. It still isn’t possible to feel it the way an owner feels it, because feeling it is a function of what you stand to lose. Nobody takes it as seriously as the people whose name is on it, and I’ve stopped expecting them to.
Which also means better cover was never going to be the fix. I was trying to buy a feeling that only comes with ownership.
And here’s the line I’m not going to soften, because it’s the true one:
By the way, the business always suffers.
Not catastrophically. Nothing collapses. But something is always a little bit behind when you get back. A conversation went cold. A thing that needed a decision waited for one. A rhythm dropped for a week and takes two weeks to pick back up. You come home and spend the first three days doing the week you were away for.
Which means the real cost of the holiday isn’t the holiday. It’s the fortnight either side of it. And once you’ve paid that twice, you quietly stop booking them.
The clearest example I have didn’t happen on a holiday. It happened during the other kind of away — the one where you’re still at your desk but your attention is somewhere else entirely.
We were rebuilding the structure of the company at the time, and we needed traffic coming in while we did it. So we told our marketing team to put a budget behind it for seven days. Seven. Then stop, and we’d look at what it did.
They let it run for a month. By the time it was switched off it had racked up $7,000 in ad spend.
We weren’t asleep. The notifications came in the whole way through, and we asked about them as they arrived. Every time, it was something else — a platform issue, a reporting lag, the way the account was set up. So we went and checked it ourselves. The errors were plainly there in the data: the instruction that had been given, and the month that had been run against it.
We brought them the data. They denied it, and refused to take responsibility for it.
That was the point we said we’re done. And the money is the least interesting part of it. What that month actually showed me is that the mechanism which is supposed to make handing something over safe — you delegate, you check in, you get told the truth — had quietly stopped working. Being turned the other way for a few weeks was all it took for nobody to catch it.
That’s what slips while you’re away. Not a task. The assumption that someone would tell you.
What cover actually can’t fix
I spent a long time thinking the answer was better cover. A more capable person. Better handover documents. A longer training runway.
It isn’t. And working out why changed how I built everything afterwards.
Cover is a person standing in the position you left. The position is the problem. If the business is built so that a person has to be in that position — awake, available, deciding, remembering — then handing the position to someone else doesn’t remove the requirement. It just changes who’s tired.
You can improve cover. You cannot make it not-a-person. And the reason you worry the whole time you’re away isn’t a trust problem, it’s a memory problem: everything they need to know about how this works is in your head, not written anywhere. I’ve written about that separately — it’s all in your head, and that’s the problem — because it’s the single reason handing anything over feels so much harder than just doing it.
There’s one more difference, and it’s the one that finally made sense of the ownership problem I described earlier.
When work sits with an operator, there’s no divided stake in the room. It isn’t choosing between my priorities and its own, because it doesn’t have its own. It isn’t weighing my risk against its risk, because it doesn’t carry one. Nothing else is happening to it this week.
I’m not going to dress that up as loyalty or devotion, because it’s neither. It’s structure. There is simply nothing competing — and nothing competing turns out to be the thing I’d been trying and failing to buy every time I went looking for better cover.
So the question stopped being who covers me and became what actually needs a person here at all.
The part where the humans stay
I want to be careful here, because this is the point where posts like this usually go somewhere I don’t agree with.
Of course there’s a place for the humans to be involved. Obviously. There are parts of my businesses that are entirely human and should stay that way forever — the client who needs to hear my actual voice, the decision about what we build next, the pricing conversation, the hard call about a relationship, the moment where judgment is the whole job.
I’m not interested in a business with no people in it. I’m interested in a business where the people are doing the things that need people.
The distinction I draw is this: the things that run in the background can be scheduled.
Not the judgment. Not the relationships. The background layer — the checking, the sorting, the filing, the drafting, the watching, the reconciling, the “did that come in yet.” All the work that has to happen consistently and doesn’t need a human at the moment it happens. It needs a human to have decided how it’s done. Once.
That layer is enormous. It’s most of what makes you feel like you can’t leave. And it is the part that never needed you awake for it in the first place.
What would actually have to be true
So here’s the honest question, and it’s a better question than “how do I find better cover.”
What would have to be true for a week away to actually work?
Not: someone competent is holding everything. That’s the version we’ve all tried, and it produces a worried holiday and a rough re-entry.
The real answer is: fewer things require a person at all.
If the background layer runs on its own schedule — if the money is being watched, the content is going out in your voice, the files are being named and filed, the research is arriving as briefs, the process someone asks about is written down where they can read it — then the pile waiting for you at the end of the week is small. And it’s the right pile. It’s the decisions, which were always yours anyway.
That’s the difference between a person covering your position and the position not existing. One of them still costs you the fortnight either side. The other doesn’t.
I’m not going to tell you I’ve solved this completely, because I haven’t, and I’d rather you trust the rest of what I write. Launch weeks are launch weeks. There are days I’m on call because I chose to be. What changed is that being away no longer means the business stops, and coming back no longer means a three-day archaeology dig through what happened without me.
The thing waiting for me now is a list of decisions. Not a mess.
Where this sits in what I believe
This post is one of three, and it’s the practical one.
The belief underneath it is do less, not more — that the answer to being overloaded is never more effort, and that the only real exit is fewer things that require you. Time off is just where that belief gets tested most obviously, because a week away is the one situation that shows you exactly how much of the business is load-bearing on one person.
And then there’s the question that makes any of this worth doing, which is what you’re getting the time back for. A week off you spend anxious isn’t a week off. Neither is a week off you spend working from a different chair.
What to do next
Try this, honestly. Imagine you’re away for seven days starting tomorrow.
Write down everything that would go wrong. Not the dramatic things — the ordinary ones. What wouldn’t get sent. What wouldn’t get noticed. What conversation would go cold. What number would nobody look at.
Now go through the list and mark which items need a human judgment, and which ones just need to happen. My list was overwhelmingly the second kind, and I’d been treating all of it as the first.
The second kind is the background layer. That’s the part you build once so it runs without you.
The AI COO Setup Kit is how I built mine — the dedicated environment, the memory that carries forward, the identity file that means your AI actually knows how your business runs, and the operators that own a function each. It’s the same foundation running across my eight businesses, and it’s the reason a week away is a real question now instead of a theoretical one.
Book the week. Then build the thing that lets you actually be in it.
~ Elfina