Your holiday is one of the clearest tests of how well the business carries on when you’re somewhere else.
You’ve told everyone you’re away. You’ve handed over the jobs you can think of. Then the messages start.
“Sorry to bother you, but do you remember what we agreed with this customer?”
“Can I send this price?”
“Where’s the latest version?”
“Has this job been checked?”
“Do you know what happened with this order?”
“Quick one while you’re away…”
Each question takes a few minutes. That’s why it can seem harmless.
A WhatsApp reply while you’re having breakfast. A quick email before everyone goes out. Ten minutes on the laptop because explaining the answer by phone will take longer.
You can be hundreds of miles from the office and still be helping to run it.
When you’re there every day, the gaps are easy to miss. Someone asks a question and you answer it. You remember the customer history. You know which figure in the spreadsheet needs explaining. You know about the exception nobody has written down.
Your presence fills the gaps.
A holiday removes you from the room, which makes those gaps much easier to see.
Operation Vacation
In Clockwork, Mike Michalowicz calls his four-week test Operation Vacation. The owner takes four weeks away and disconnects from the business.
The test exposes the places where work stalls or comes back to the owner because nobody else has enough information, confidence or authority to keep it moving.
Four weeks is a demanding target. An ordinary family holiday can reveal the same kind of weakness much sooner.
Why did they need you?
The interruptions point in two different directions.
Some questions genuinely need your judgement. A member of staff may need authority to approve a refund, agree a discount or handle an unusual customer situation. That points towards delegation, training or clearer responsibility.
Other questions need information:
- Has this customer approved the quote?
- Which jobs are waiting for parts?
- Has anyone chased this renewal?
- What did we promise this customer?
- Who’s dealing with this?
- Why hasn’t this been invoiced yet?
If the answer is spread across a spreadsheet, email, notes and what you remember, asking you may be the quickest route.
That is the kind of interruption a better working system can remove.
Give the team somewhere else to look
Take one recurring job such as following up enquiries, handing work from sales to delivery, tracking jobs waiting for information or managing renewals.
Someone covering for you should be able to see where the job has reached, who owns the next step, what has been promised and what needs attention.
They shouldn’t have to reconstruct the position from several emails and then check with you that they’ve understood it correctly.
This is one reason handovers become more important as a company grows. We cover that wider question in What systems does a growing business need?
A holiday puts the handover under pressure. If the information survives without you, the work has a better chance of doing the same.
Keep a note of what reaches you
On your next holiday, write down the work interruptions as they happen.
At the end, sort them roughly into three piles: genuine exceptions, decisions that need clearer authority, and questions caused by missing or scattered information.
Then look for a cluster.
If several interruptions come from the same spreadsheet, tracker, inbox or recurring job, you’ve found somewhere worth fixing.
There’s no reason to redesign the whole company around a four-week absence. Choose the piece of work that keeps finding its way back to you.
A renewal list that nobody else can confidently chase. Customer promises that still sit in your inbox. Jobs that can’t be invoiced until you explain what happened. A handover that works only because you remember what sales agreed.
Fixing one of those jobs won’t remove you from the business. It can stop that job requiring your presence every time somebody gets stuck.
If the same spreadsheet, tracker or piece of admin keeps generating questions whenever you’re away, show it to us.
We’ll tell you whether it looks suitable for a Day-1 Build.