The Five-Day Disappearing Act: What Your Business Tells You When You're Not There
Most founders I talk to have taken a vacation in the last two years. Almost none of them have actually been gone.
The phone comes along. The laptop comes along "just for mornings." By day three they're answering a question about a shipping delay from a hotel lobby in Asheville, and by day five they've rebuilt the exact dependency they left town to escape. Then they come home and announce that the business can't run without them, which is less an observation than a confession.
So try the other version. Pick five days, tell everyone you're unreachable, and mean it. Then treat what breaks as data.
Why a Planned Blackout Beats a Real Vacation
A vacation has an emotional goal — rest — and that goal quietly overrides the experiment. You'll break your own rules to protect the mood of the trip. A blackout has an operational goal: find out where the business still bends around one person. Different framing, different behavior.
Call it a blackout test instead of a vacation. Put it on the calendar months out, brief the team the way you'd brief them on a client audit, and set the expectation that the point is to surface problems, not to prove everyone secretly needs you.
The week between Christmas and New Year's is a genuinely good window if your business slows down. If it doesn't, pick a normal week — a quiet week hides the interesting failures.
Before You Go: Build the Decision Map
Spend two hours listing every decision that reaches your desk in a typical week. Be brutally literal. It'll look something like:
- Refunds and credits above $250
- Discounts beyond the published tier
- Any change to a quoted timeline
- Hiring anyone, including contractors
- Approving spend over $1,000
- Saying yes to a custom request
Then write two columns: who handles it while you're out, and what they're allowed to do without asking. Give real numbers. "Use your judgment" is not a threshold; "anything under $500, just do it and log it" is.
The decisions you can't hand off — the ones where nobody else has the context — are your first finding, and you haven't even left yet.
Name a Client Owner for Every Top Account
Pull your ten largest accounts. For each one, name a specific person who owns the relationship that week, plus the context they'd need: what this client is sensitive about, what's been promised, what's still open.
Send the client a short note before you go. Something like: "I'll be out Monday through Friday next week. Marisol is running things and has full authority on scheduling and scope. Here's her direct line." Clients handle this fine. What they don't handle well is discovering you're gone the moment they need an answer.
One Channel, One Set of Rules
You need exactly one way to reach you and a strict definition of emergency. Two setups that work:
- A dedicated number that rings to a backup person first, who escalates only if it's genuinely urgent.
- A single shared inbox or channel checked once a day at a fixed time.
Write the escalation rules on one page and post it where the team actually looks. A burst pipe in the warehouse at 6 a.m. is an emergency. A client wanting a logo file in a different format is not. Be specific, because "use your judgment" defaults to "text the founder."
Then define your own behavior. You check the channel once daily. You respond only if the message clears the written definition. Everything else gets a thumbs-up and a line in the stuck list.
The Stuck List Is the Whole Point
Ask your team to keep a running document during the week. One line per event:
What we needed → who we needed it from → what we did instead → what it cost (time, money, or client goodwill)
That log is the deliverable. Not the silence, not the peace of mind — the log. Five days of entries tells you exactly which parts of the business are still shaped like one person.
You'll see three patterns almost every time. Decisions waiting on approval authority. Knowledge that lives in one head and nowhere else. Relationships where the client will only talk to you. Each one has a different fix, and mixing them up is why a lot of delegation advice quietly fails.
The 30-Day Plan to Shrink the Shape
Don't fix everything. Take the five most expensive entries in the log and work through them a week at a time.
Days 1–7: Move the authority permanently. Grab the three most frequent approval items and raise the threshold for good, not just for the week. Announce it in writing and update the discount sheet, the refund policy, or whatever document people actually open.
Days 8–14: Write it down. For each knowledge gap in the log, have whoever holds the knowledge write a single page — not a manual, a page. Include the three questions they get asked most and the answers.
Days 15–21: Duplicate the relationships. Where a client only calls you, add a second name to the account this month. Introduce them, loop them into a real thread, hand them something to own.
Days 22–30: Test again, smaller. Run a two-day absence on a Thursday and Friday. Re-read the stuck list. If it's shorter and cheaper, you're making progress.
What Not to Do
Don't run the blackout as a loyalty test or a way to catch people slacking. The data gets contaminated the moment the team knows they're being graded, and you'll get a week of people pretending nothing needs you — which is worse than no data at all.
Don't fake an emergency. Don't take the laptop "just in case." Don't thank anyone for solving a problem by waiting until you got back.
And don't skip the follow-through. A blackout without a 30-day plan is just a week of avoided email. The goal isn't to prove the business can survive your absence — it's to find the handful of places where it currently can't, and make them boring.
