Back office
Why does everything in the business have to go through me?
By Paul Meakin6 min read

Why does everything end up waiting for you?
Nobody designs a business this way. It grows into it. In the early days you made every decision because there was nobody else to make it, and you were good at it, which is partly why the business survived. Then people joined. They asked you things, you answered, and the answer stayed in your head rather than anywhere they could find it next time.
A few years on, the pattern is set. The large quote waits for you. The supplier invoice that looks a bit odd waits for you. So do the holiday request, the refund, the new starter's laptop and the wording on a customer letter. Each one takes you a minute. The trouble is the queue, and the fact that it only moves when you are at your desk.
Being needed feels like being useful. They are different things. When you are on holiday, or with a customer all day, the business does not slow down politely. It stops, and the people around you learn that waiting is the safe option.
What do the official figures say about how small firms are run?
The Office for National Statistics measures this. Its Management and Expectations Survey scores firms from 0 to 1 on structured management: whether they respond to problems, track performance and set targets, review how they work, and base promotion on merit. The survey covered firms with 10 or more employees.
Larger firms scored higher: firms with more than 250 employees averaged 0.68, while firms with 10 to 19 employees averaged 0.51. And firms with below median scores were four times more likely to use little to no analysis to support business decisions.
The survey does not measure owner bottlenecks directly, and we are not going to pretend it does. What it shows is that the smallest firms it covers score lowest on structured management, the measure that covers performance tracking, targets and regular review. Where that structure is missing, the process tends to be a person. In a small business, that person is usually you.
Which decisions actually need you?
Fewer than it feels like. Most of what lands on your desk falls into a handful of types, and only one of them really needs the owner.
| What is waiting | Does it need you? | What can replace you |
|---|---|---|
| Routine approvals inside a known limit | No | A written rule with a limit, and a named person who applies it |
| Questions you have answered before | No | The answer written down where people can find it |
| Exceptions that come up now and then | Sometimes | A route: who decides, by when, and what gets passed up to you |
| Sign off that needs a record | Not always | An approval step with a named approver and a due date |
| Pricing, senior hires, anything that risks the business | Yes | Nothing. This part is your job |
The test is simple. If you would make the same call almost every time, it is a rule waiting to be written.
Why do owners get this wrong?
The usual mistake is handing over the task and keeping the rules in your head. Someone else does the work, but they still have to come back and ask, because they cannot see where your limits are. Nothing has moved. The queue has just changed shape.
The opposite mistake costs more. An owner gets fed up, says "just deal with it", and steps away with nothing written down. Decisions drift, something goes wrong, and the owner takes everything back with a firm view that delegation does not work. Nothing was set up for it to work.
There is also a legal reason not to vanish. GOV.UK's guidance on running a limited company says you can hire other people to manage some of your duties day to day, but you are still legally responsible for your company's records, accounts and performance. So the aim is to stay informed while no longer being the only route through which anything happens.
How do you get out of the approval loop without losing control?
Start with a week. Every time something waits for you, write down what it was, who asked, and what you decided. By Friday you have the real list rather than the one you imagine.
Then sort it using the table. For every item you would decide the same way most of the time, write the rule in plain English: the limit, the conditions, and who applies it. Keep it short enough that the person using it will actually read it.
Next, give each rule a route. A rule with no owner is a suggestion. Decide who applies it, what they record, and what happens when something falls outside it. People skip that last part, and it is exactly where things find their way back to your desk.
Where a decision needs a visible sign off, use a proper approval step rather than an email thread. Google Drive has approvals on files: when a document is ready for review you can lock it and ask the recipient to approve the content already drafted. There is a catch. Google's help page says the feature is only available for Enterprise and Google Workspace for Education Plus accounts, and not for personal or standard Workspace accounts. On a standard plan, a shared sheet with a status column, a named approver and a script that sends reminders does a similar job. We build that kind of thing with Google Apps Script as part of our process automation work.
Finally, review the exceptions rather than the routine. Once a month, read what was decided under the rules and what still came to you. If the same exception keeps arriving, it is another rule waiting to be written. You keep control, and you stop being the queue.
When is this not the answer?
When the gap is a person rather than a process. If nobody in the business has the time or the judgement to own decisions, writing rules for them changes nothing. That is a hiring question.
When the decisions really are all judgement calls. Some businesses, especially very young ones, run on the owner's taste and relationships. Writing rules for those is busywork. Wait until the same calls start repeating.
When the real problem is trust in one particular person. Rules and routes help people who are capable but unsure where the lines are. They do not repair a working relationship that has broken down, and no system will.
And when a decision is legal, tax or regulatory, the route should lead to your accountant, solicitor or other professional adviser. We design the process around those decisions. We do not give that advice.
Where do you start?
Keep the log for a week. It costs a notebook, and it tells you more about how the business really runs than any organisation chart. If the list is long and the same items keep turning up, a few written rules and a couple of routes will usually take a good part of it off your desk.
If you want a second pair of eyes on it, tell us what's stuck and we'll map the quickest fix. We will tell you straight whether it needs business analysis and a written process, some automation, or simply permission for someone else to say yes. Time to talk yet?
Common questions
How long should I keep the log for?
A normal working week is usually enough to show the pattern. If your business is seasonal, or the week was unusual, run it again in a busier spell.
Do I need new software to do this?
Not to start. Most of the work is deciding and writing down the rules. Software helps once approvals need a record, reminders or an audit trail, and that can be as simple as a shared sheet with a script behind it.
Can I use Google Drive approvals on a standard Workspace plan?
Google's help page says approvals are only available for Enterprise and Google Workspace for Education Plus accounts, not standard Workspace accounts. A shared sheet with a named approver and automatic reminders can do a similar job.
If I hand decisions over, am I still responsible for them?
For a limited company, yes. GOV.UK says you can hire other people to manage some duties day to day, but as a director you are still legally responsible for the company's records, accounts and performance. That is why the written rules and the record of decisions matter.
Sources
Paul Meakin, Founder
Twenty years of fixing businesses from the inside, eighteen of them in recruitment from consultant to national operations, before building the automation, web applications and compliance systems Staxxd runs today.
More about Paul