The Two-Week Test

Founders ask me how to tell whether their operations are good enough. The metrics people reach for — headcount, revenue per employee, how many processes are documented — all measure the wrong thing. Here is the only test that matters.

Go away for two weeks. Not a working holiday. Properly away: phone off, laptop shut, nobody expecting a reply. Then come back and look at what happened while you were gone.

What the answers tell you

There are roughly three outcomes, and each one points at a different problem.

• Everything stopped. Not slowed — stopped. Decisions queued up waiting for you. This is not a team problem; it is an authority problem. Nobody has been given the right to decide anything.
• Everything kept moving, badly. Work continued but quality fell off, customers got inconsistent answers, two people did the same thing differently. This is a standards problem. The knowledge exists but only in your head.
• Everything kept moving, well. Congratulations, you have a company. Most people reading this will not be here yet.

The useful thing about the test is that it is diagnostic rather than judgemental. A company that stops without you is not badly run. It is just young, and run by somebody who has not yet handed anything over.

Why founders fail this test for years

Because handing over is slower than doing. Every single time. Explaining a task takes four times longer than performing it, and the first three attempts by somebody else come back worse than yours. There is a stretch of weeks where delegating costs more than it saves, and almost everybody quits inside that stretch.

The second reason is subtler. Being the bottleneck feels like being important. When every thread runs through you, the company clearly needs you. That feeling is pleasant and it is also the precise shape of a ceiling.

What actually fixes it

Three things, in this order, and the order matters.

• Write down the twenty things. Not everything — the twenty recurring tasks that currently only you can do. Each one gets a one-page procedure, written the way you would explain it to a competent person who has never done it.
• Put a name on each one. Not a team, a person. Shared ownership is no ownership. The person who owns it decides how it runs, and you stop being asked.
• Set a rhythm, then shut up. A weekly review where owners report on their own work. Your job in that meeting is to listen and unblock, not to re-decide.

The rhythm is the part people skip, and it is the part that makes the other two stick. Documents without a cadence rot inside a month. A cadence without documents is just a meeting where everybody improvises. You need both.

Start smaller than you think

Do not try to document the company. Pick the three tasks that interrupted you most last week, write those down, give them away, and see what breaks. Fix what breaks. Then do the next three.

Six weeks of that and the two-week test stops being frightening. Which is, in the end, the whole point of building a company rather than buying yourself a job.