The Real Reason You Couldn't Unplug This Summer
You took the trip. You told people you were "off." And somewhere around day two, you were answering a Slack message from a lounge chair, telling yourself it would only take a second.
It never takes a second. It takes the rest of the afternoon, because now you're thinking about the three other things that message reminded you of.
I hear a version of this from almost every founder and executive director I work with. Not "I don't take vacation." Most of them do. What they don't get is an actual break, the kind where their organization keeps running and nobody needs them to make it happen.
That's not a discipline problem. It's not about turning off notifications or being better at boundaries. If your team could only run smoothly while you were watching it, that was true before you left for the airport. Vacation just made it visible.
What's actually happening
When every recurring decision quietly routes back to one person, that person can't leave, not really. Someone still has to approve the thing, answer the question, unstick the stuck project. If that person is you, your team isn't ignoring their judgment. They usually don't have enough clarity on what's theirs to decide in the first place.
That gap doesn't show up on a slow Tuesday. It shows up the moment you're unreachable for a week. Which is exactly why so many founders come back from time off more tired than when they left. The break wasn't a break. It was managing the same organization from a different location.
Why this is fixable, and why it usually doesn't get fixed
Most founders know something is off. Very few carve out the time to actually address it, because the fix always seems to require slowing down first, and slowing down is the one thing that never feels available.
And when a founder does manage to carve out time, it often goes toward real pain points, a disorganized shared drive, an outdated handbook, a process that only lives in someone's head. Those are worth fixing. But if what you're actually chasing is a vacation where you don't have to be reachable, there's a more direct place to point that time: the decisions themselves.
Here's the part that surprises people: you don't need a quiet season to build this. You need three specific things, and none of them require a hiring decision or a six month overhaul.
1. Name who owns each decision, by name, in writing
Not a department. Not "the team." A specific person's name next to a specific type of decision. If a vendor question comes up, who decides without checking with you first? If a client complains, who has the authority to resolve it on the spot?
Most teams don't have this written down anywhere. So when something comes up, the safest move for an employee is to ask you, because asking is never wrong and guessing might be. That's not a lack of initiative. That's a completely reasonable response to an unclear line.
Sit down and list your organization's ten most common recurring decisions. Next to each one, write the name of the person who is now allowed to make that call without you. Tell them directly. That's the whole first step, and it takes an afternoon, not a quarter.
2. Define what "done" actually looks like
Even when someone owns a decision, they'll still route it back to you if they don't know what a good outcome looks like in your head. You know what "handled well" means for a donor email or a client escalation. Your team is often guessing at your standard, one incident at a time.
This doesn't require a formal policy manual. It requires writing down, in plain language, what you'd consider a good outcome for the two or three situations that come up most often. One page. Specific enough that someone could read it and know they got it right without asking you.
3. Give them a way to signal it’s done (pinging you directly doesn’t count)
Even with clear ownership and a clear bar for "done," things fall apart if there's no regular checkpoint. Not a checkpoint where you review everything. A short, predictable rhythm, weekly or biweekly, where the person who owns something reports what happened and what's next, without you having to go find it.
This is the piece that actually lets you leave. Decisions get made without you, they get made to a standard you'd recognize, and you get an update on a schedule instead of by interruption.
None of this requires new software or a new hire. It requires an afternoon of mapping what's currently living only in your head, telling your team plainly what's now theirs, and putting a simple rhythm in place to keep it that way. Most of what breaks down when a founder tries to step away isn't complicated. It's just never been written down.
What it's worth
I work with small business owners and nonprofit executive directors across Missoula and beyond, and the pattern is remarkably consistent. The organizations where a founder can genuinely step away for two weeks aren't the ones with the most polished processes. They're the ones where roles and decisions were made explicit instead of assumed.
Operational clarity isn't a “nice to have” for the slow season. It's the difference between a vacation where you rest and one where you just relocate the job.
If this sounds like your last trip, or the one you haven't taken yet, send me a message. I'd rather help you build the kind of clarity that holds while you're gone than watch you come back needing a vacation from your vacation.
