I can't take two weeks off
Two weeks is the point at which a business stops coping and starts revealing what it cannot do without you. A long weekend proves nothing, because anything urgent waits. Two weeks forces a decision you normally make, and whatever breaks is the decision nobody else was ever given.
Written for founders of businesses between £500k and £15M. Treat the fortnight as a diagnostic rather than a reward, and it hands back a list you can act on.
What the fortnight actually measures
Every business absorbs a few days. At around day eight the queue of held decisions gets long enough that someone has to choose between guessing, waiting or calling you. Which of the three they choose, and about what, is the finding.
Nothing happens
Work in flight continues. Anything contentious gets parked for your return. This is the stretch most founders mistake for evidence that the business is fine.
The queue forms
A client wants a variation priced. A supplier wants an order approved. Someone wants to know whether to start a job. Each is small; together they are the shape of your week.
Someone breaks
A person makes the call without you, or the queue reaches the client. Both are useful. The first shows you who is ready. The second shows you what it costs to wait.
The workaround sets
Your team invents a route round the gap. Sometimes it is better than your process. Sometimes it is a discount nobody approved. Either way you now know where the design is thin.
Run it as a test, not a gamble
Before you go, write down the decisions you expect to arrive and who will make each one, with a value limit. Keep a shared log. On your return, compare what you predicted with what happened. The gap between those two lists is the work.
Name a deputy for each area
Sales, delivery, money, people. One name each, told in advance, told in front of everyone. Four names beats a single stand-in who becomes a bottleneck of their own.
Write the limits down
What each deputy may approve and up to what value. Set them higher than feels comfortable. A limit that is too low sends the decision to your phone, which defeats the test.
Agree what constitutes a real emergency
Two or three named events. Anything not on that list waits or gets decided. Say it out loud before you leave, or your team will apply their own definition, which will be broader than yours.
Log every held decision
One shared page: what came up, who decided, what they chose, what it cost. This log is the output of the test and the agenda for the month after it.
Founders who run it this way come back with a list of four to six decisions that have no owner. That list is more useful than any operational audit, and it costs a fortnight you were owed anyway.
What the common breakages mean
| What broke | What it tells you | Where to fix it |
|---|---|---|
| A client waited a week for an answer. | No one holds authority over the commercial relationship. | Account ownership and a pricing limit. |
| A job started late because nobody would commit resource. | Resourcing has no single owner. | A named owner for capacity, with authority to move dates. |
| Someone discounted to close a deal. | A limit existed in your head and nowhere else. | A written discount threshold by deal size. |
| Nothing broke, but nothing progressed either. | Your team can operate but cannot decide. | Decision rights, not more process. |
| Everything ran, and you felt uneasy. | The structure holds. The habit is yours to break. | Your own calendar. |
What it looks like when it holds
One construction founder ran this test, then spent six months closing the gaps it exposed.
Going away does not fix anything. It shows you the list. Most founders already suspect what is on it and have never seen it written down.David Schofield
Common questions
What if I genuinely cannot leave for two weeks right now?
Run a one-week version with the same preparation: named deputies, written limits, a decision log. You will see the queue form even if you do not see it break. Then schedule the fortnight for a quarter ahead and treat the date as fixed, because a test that keeps moving never runs.
Should I stay contactable?
Be reachable for the two or three events you named as emergencies, and unreachable for everything else. Staying half-available is the worst of both: your team escalates rather than deciding, and you get neither the rest nor the diagnostic.
Everything ran fine while I was away. Does that mean I am not needed?
It means the structure holds for two weeks, which is a good result, not a redundancy notice. The next question is whether it holds under a decision that matters: a lost client, a bad month, a resignation. Those are the tests that show whether authority is real or borrowed.
My team says they are happy to wait for me. Is that a problem?
Yes. A team that is comfortable waiting has learned that deciding carries more risk than delay. That is a rational response to an environment where decisions get overturned, so the fix is yours: set limits, then back the calls made inside them even when you would have chosen differently.
Related reading: Making the business run without you · My team can't manage without me · Threshold-based authority maps · How to step back from your business
Read the list it gives you
If you have already been away and watched something break, bring what happened. We can sort the incidents into habits and structural gaps on one call. The two need different fixes.
Book an Operational Clarity Call →