top of page

Forget the 30-Day Vacation Test: The Silence Test for Operators Who Already Work a Job

Writer: Brian Lathe
Brian Lathe
6 days ago
5 min read

Updated: 5 days ago

Forget the 30-Day Vacation Test: The Silence Test for Operators Who Already Work a Job

Ryan Deiss has a test he's proud of, and he should be. It's called the 30-Day Vacation Test. Disappear from your business for thirty days. If it keeps running — keeps selling, keeps delivering — you have a business. If it falls apart without you, you don't have a business. You have a job that you own.


That's a fair test, and for the founders he built it for it's the right one: it exposes a business where the founder is load-bearing in every wall. Now let me tell you why it's the wrong instrument for you and me.


You can't fail a test you're already taking every day

The vacation test assumes two things: that your absence is an event, and that you can afford to wait a month for the answer.


If you run a one-person business alongside a job, neither is true. Absence isn't an event. It's Tuesday. You're gone eight, ten, twelve hours a day, plus the hours you're asleep. Your business already lives without you most of the time — the question was never whether it survives your absence. It's what it does during your absence: what keeps moving, what quietly stalls, what waits, politely and expensively, for you to come home.


And a month is too long to wait for the answer: in a business of one, one stalled follow-up can be the whole week's revenue. You need a measurement you can run this week. So I don't take vacations from my business to test it. I go silent.


The Silence Test, in full

The rule is one sentence: for a set period, the business gets zero input from you — and everything it does or fails to do gets written down. Not "mostly no input." Zero. No answering, no nudging, no fixing what you happen to notice. The moment you intervene, you've stopped measuring the system and started being the system again, and the test is over.


It runs in three parts.


Before the silence: write the prediction. On one page, write what should keep moving without you — the actual list: which follow-ups go out, which inquiries get answered, which delivery steps complete, which numbers get recorded. If you can't write the prediction, that's your first result, before the test even starts.


During the silence: the system keeps the log, not you. Every stall gets logged — what was supposed to happen, when it stopped, what it was waiting for. Every genuine need-you moment gets logged too. I call those shoulder taps: a decision only you can make, an approval only you can give, a person owed you specifically. They wait, and they get counted. In my system the desks do this logging while I work my shifts, because the memory lives in the system, not in my head. A notebook and an honest end-of-day reconstruction will do for your first test. The log is the product; the silence is just how you make it true.


The ladder: one workday, then a weekend, then a week. Start with a single workday — which, if you work a job, you're already doing; the only new part is the prediction and the log. Then a weekend, when you're normally around and tempted to tinker. Then, when the first two stop producing surprises, a full week. Each rung asks a different question: does the routine run? Does it run when I'm tempted to rescue it? Does it run when something unusual happens — because in a week, something unusual always happens.


After: every stall gets sorted, and only one pile is allowed to stay

This is where the test pays for itself. Sit down in one sitting — that's how I review mine — and put every stall in exactly one of four piles:


(a) Missing rule. The system didn't know what to do, because you never told it. Nobody decided wrong; there was simply no decision written down. Fix: write the rule. Once.


(b) Missing procedure. The rule existed, but the steps didn't — it knew what should happen and not how, in what order, checked against what. Fix: write the procedure — for this step only, not for everything.


(c) Missing capability. Rule and steps were there, and the business still couldn't do it — the tool, access, or desk for that job doesn't exist yet. Fix: that's a building job, on the list in plain sight instead of hiding as a recurring "I'm just busy" feeling.


(d) Genuinely you. Your judgment, your signature, your relationship, your name on the line. This is the only pile allowed to stay. Everything in (a), (b), and (c) is a loan against your own hours, and the test just showed you the balance.


Notice what this does to the shoulder taps. Sorted honestly, most land in the first three piles: they weren't the business needing you, they were the business needing a rule you hadn't written yet. That's the most useful bad news a solo operator can get, because rules are cheap and hours are not.


The three numbers that matter

Track these across tests, and nothing else at first:

  1. Shoulder taps per test. The headline number. It should trend down — not to zero, because pile (d) is real, but down.

  2. Stalls per test, by pile. You're watching the mix change: fewer (a)s and (b)s as the rules and procedures accumulate.

  3. Longest stretch the business moved alone. Hours or days where the prediction ran as written, no stall, no tap. That stretch is your real vacation capacity — measured, not guessed.

No dashboard. Three numbers, and the trend is the truth.


Why this beats the vacation test for a business of one

Deiss's test gives you a verdict: business, or job you own. The Silence Test gives you a work list. It runs on the schedule your life already imposes — a shift, a weekend, a busy week — and tells you not just that the business depends on you, but where, why, and in which of four fixable ways. And it respects what his test was never designed to see: in a one-person business, some dependence is correct. You are the trust your customers buy. The goal was never a business that needs you never — it's one that needs you only where you actually matter, and can prove it, one silent workday at a time.


Run the first one this week. Then sort what stalled into the four piles above — that shows you which pile your business is probably drowning in. The weekly scorecard gives you somewhere to put the three numbers.


The scorecard runs inside SuccessBrian OS — and it is free

SuccessBrian OS is the system I run my own one-person business on. The weekly scorecard from this article works inside it.


In plain words: once a week, you type in five numbers — new leads, sales talks, work delivered, things shipped, cash in. The system keeps them, shows you which ones hit your target and which ones fell behind, and remembers the plan and the promise you made. You do not have to keep a spreadsheet alive. You do not have to remember anything. The system remembers for you.


It costs nothing. There is no form to fill out and nothing to buy. Download it and use it:



Rather start on paper? The scorecard template is printed in full on this blog, in "The Weekly Scorecard for a One-Person Business." Start there if you like. Just start this week.


SuccessBrian OS is not affiliated with Scalable.co or Ryan Deiss. The 30-Day Vacation Test is described from Scalable's public case study and pages, read in November 2026. If you run a $2M+ business with a team, his test — and his system — may genuinely fit you. This one is for the rest of us.


Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page