Skip to content

Owner problems

Could your business survive you taking two weeks off?

Last updated 5 July 2026 · Reviewed by Nick Thorpe

The short answer

Most owner-led businesses would struggle. The test is simple: imagine two weeks fully offline, no calls, no email, and ask what breaks. Four honest results: it stops dead, it limps, it runs with fires, or it runs fine. Each level points to a specific gap in delegation, systems or team ownership, and a specific first fix.

Most owners have never run this test, usually because they already suspect the answer. That is exactly why it is worth ten honest minutes. It costs nothing, needs no spreadsheet, and it tells you more about the state of your business than most management reports.

How do you run the two-week holiday test?

Pick two real weeks in the calendar, assume you are completely unreachable, and walk through a normal fortnight of trading item by item. The rules are strict, because the moment you allow “they could always ring me”, the test collapses.

  1. Choose two specific weeks a few months out, so the exercise feels real rather than hypothetical.
  2. Set the condition: no phone, no email, no messages, no checking in. Fully offline.
  3. List what a normal fortnight throws at the business: new enquiries, quotes to send, work to deliver, invoices to raise and chase, a complaint, a staff issue, a supplier letting you down, payroll.
  4. For each item, name the person who handles it without you, and how they know what a good outcome looks like.
  5. Score the result honestly: stops dead, limps, runs with fires, or runs fine.

If any answer is “they would ask me”, mark that item as a fail. The test measures the business, and asking you is the business admitting it has no other mechanism.

What do the four results mean?

Each result maps to a stage of delegation, systems and team ownership, running from owning a job through to owning a business.

ResultWhat actually happensWhat it tells you
Stops deadSales stop, decisions queue, some work cannot physically happenYou are the product, the manager and the system. Delegation has not started.
LimpsExisting work gets delivered, nothing new starts, decisions stack up for your returnTasks are delegated, authority is not. Your team can do, they cannot decide.
Runs with firesThe fortnight passes, then you spend a week untangling what went sidewaysSystems exist but are thin, and ownership is partial. People decide, inconsistently.
Runs fineYou come back to a business in the same shape you left it, or betterDelegation, systems and ownership all work. You have a business, and also a holiday.

Most owner-led businesses sit somewhere between the first two rows. That is normal, and it is fixable. It only becomes a problem when the owner treats it as permanent.

What should you fix first at each level?

Fix the level you are actually at, with one deliberate move, before reaching for anything cleverer.

If it stops dead: the first fix is separation. Write down everything only you can currently do, pick the item that eats most of your week, and hand it to a named person with a written standard for what good looks like. One function, handed over properly, breaks the seal.

If it limps: the first fix is authority. Your people can already do the work, so give them decision rights with clear boundaries: a spending limit, a discount limit, a rule for when to escalate. Decisions stack up in your inbox because nobody has been told they are allowed to make them.

If it runs with fires: the first fix is systems. Take the three things that caught fire last time you were away and write the playbook for each: the trigger, the steps, the standard, the owner. Thin systems fail quietly until you leave the room.

If it runs fine: the first fix is ambition. The business no longer needs you daily, so decide what you want from it next: scale it, step back, or make it sellable. Working on the business is now your actual job.

Why do most businesses fail the test?

Because doing the work yourself is faster today, and being needed feels good. Both are traps. Doing it yourself saves an hour this week and costs you the fortnight, every fortnight, for years. Being needed feels like being valuable, so owners quietly build businesses that cannot cope without them and call it dedication.

There is a practical reason too: nobody sets a date. A vague intention to delegate more rarely survives a busy Tuesday. A booked fortnight forces the issue, which is why the best version of this test ends with real flights.

Is this the same question the CoreOS Scorecard asks?

Yes. The Time question in the CoreOS Scorecard asks exactly this: could the business survive two weeks without you? The Scorecard is twelve tap-through questions, takes a few minutes, and gives you an instant score, with the option of an AI-generated twelve-month plan. Free, no sales call attached.

If you already know your answer is “stops dead” or “limps” and want a structured way out, that is the work I do with owners inside Momentum: a monthly strategy session, accountability between sessions, and the CoreOS framework applied to your business. If you are weighing up whether coaching is the right kind of help at all, start with how Core compares with other options. Either way, run the test first. Ten minutes, no spreadsheet, and you will know exactly where you stand.

NT

Nick Thorpe

16 years a British Army officer, then a decade building his own companies. Coaches business owners on the CoreOS framework. The story.

Frequently asked questions

What counts as fully offline for the test?

No phone, no email, no messages, no checking in. If the business can reach you, the test is measuring your availability rather than the business. In real life a pre-agreed route for genuine emergencies is sensible, but for the thought experiment assume even that stays silent.

My business is just me. Does the test still apply?

Yes, and the result will be stops dead, which is useful to admit. A one-person business fails the test by definition, so the question becomes whether you want it to stay that way. If you do, plan your finances around unpaid holidays. If you do not, your first hire or first outsourced function is your version of the fix.

Should I actually book the two weeks, or just imagine them?

Imagine first, then book. The thought experiment shows you the gaps; the booked holiday forces you to close them. A real date in the calendar does more for delegation than any amount of good intent. Start with a long weekend if a fortnight feels reckless, then extend.

How long does it take to get from stops dead to runs fine?

It depends on the size of the team and how much of the business currently lives in your head, so treat any fixed timescale with suspicion. Expect deliberate work over months per level rather than a quick fix. The order matters more than the speed: separation first, then authority, then systems, then ownership.

Find out what is actually holding your business back.

The CoreOS Scorecard: three minutes, your score, and the one thing to fix first.

Apply for a 30-minute call