Eight years into building his company, a founder asked his teammates to revoke his Slack access, stopped opening email, and disappeared for a month. He came back expecting to learn how well the place ran without him. The first thing he wrote down instead was that the company takes too long to make decisions.
His absence didn't create autonomy. It measured latency.
That's the outcome most founders get and don't expect. You block the calendar, go quiet, and return to a pile — forty items that waited instead of forty items somebody decided. The only thing that changed was the timestamp. Going offline moves decision timing. It doesn't move decision authority, and authority is what was jammed.
So the question to ask after any stretch away isn't whether things ran smoothly. It's whether anything got decided. Small calls get made every day with or without you; nobody waits on permission to reorder printer paper. The items that sat untouched are the ones carrying information. Count them, then count how many you'd have decided differently than your team would have. If that's two out of forty, the wait bought nothing and cost thirty-eight.
The standard diagnosis for all of this is dependency. You've trained people to wait, so nothing moves while you're gone. That's real, and it's only half the picture. The other half is the founder whose company runs fine and who breaks it by showing up. You glance at a process, it looks inefficient from the outside, and you ask why it isn't done the other way. Then you dig into how it's actually being done and find the team's version was smart — it needed a tweak, not a re-engineering. Partial context is expensive. A founder deciding from the surface does more damage than one who's unreachable, because the unreachable one at least leaves a working system alone.
Work out which of the two you are before designing a fix, because the remedies point in opposite directions. Dependency calls for deliberately transferring judgment. Disruption calls for staying out of rooms you only half understand.
There's a third move, though, and it gets almost no airtime: deciding, on purpose, not to decide.
One founder had an employee generating drama — complaints, side conversations, a constant hum of it — and the whole thing felt urgent. But he couldn't name the actual damage. He could only feel the volume. So he did nothing deliberately and waited to find out whether the problem needed him. It didn't. The employee left of their own accord. A second, similar case resolved when the people involved asked him to step in and he told them to work it out themselves. They did. Across those cases his read is that roughly nine times out of ten, patience turned out to be the right call.
Noise is not the same signal as damage. Urgency that comes from volume rather than cost tends to evaporate, and the founder who acts on the hum gets dragged into problems that would have resolved without them. One test separates the two: can you say in a single sentence what this costs the company if nobody touches it for two weeks? If you can't, you've found something that wants your attention rather than something that needs your judgment.
None of that restraint comes cheap, because the trait that started the company against every base rate is the belief that you can control outcomes. The same trait makes patience feel like negligence.
The rest is mechanics. Handing off real work costs quality before it pays anything — the first proposals someone else writes won't be as good as yours, and sometimes a deal is lost because of it. That loss is the tuition, and the alternative caps the company at your personal bandwidth. You can make the handoff fail less by building one master document that holds everything, far more than any single deal needs, so the job becomes pruning rather than authoring. Recognizing what to cut is easier than remembering what to add.
And if you're telling yourself you don't need any of this because you're not burned out, check what you're measuring. Burnout tracks progress, not hours. Hard work on something advancing doesn't wear founders down; backtracking does, and so does admin work that keeps things stable without ever feeling like motion. One founder who never stepped away watched his decisions get worse and his company grow less than it should have. Six months after selling it, he was still waking up with his heart pounding about payroll.
Before you disappear anywhere, name who decides what while you're out and what fires by default if nobody does. Then leave their calls alone when you get back — reverse one and you've taught everybody that waiting was always the right answer.
Watch the Full Episode on Strategic Inaccessibility below:
Follow us to watch live on YouTube and LinkedIn or listen to episodes on Apple Podcasts and Spotify.