It's a systems problem: work on your business, not in it

You're working more hours than you were two years ago. Evenings. Weekends. Checking your phone on holiday, just in case. And the business hasn't grown to match it. It isn't calmer. It isn't any less dependent on you than it was back then.

More hours won't fix that, because hours were never the actual constraint. The real constraint is how many things in your business still have to go through you personally before they can happen. Right now that might be approving every quote before it goes out, building the week's schedule yourself, or being the one who has to reply to certain customers personally. Add hours and you can push a few more of those things through in a week. You never change how many things need you specifically.

That's the reframe worth sitting with: this isn't a time problem. It's a systems problem. A "system," stripped of the jargon, is just an answer to one question — who or what handles this without me? Right now, for most of what happens in your business, the honest answer is still "me."

Why handing off beats working harder

Here's the mechanism, plainly. Every task that has to pass through you — you approving it, you doing it, you deciding it — is one thread tying the business's ability to function to you being in the room. It doesn't matter how good you are at the task. The thread exists because you're the only path through it. This is what business owner bottleneck actually means in practice — not a character flaw, a structural one.

The moment one of those threads gets replaced — by a written process, or by a person who can now do it without you — that's not a small convenience. It's one permanent thing your business no longer needs you for. Not this week only. From then on.

Do that once, and your business is very slightly less dependent on you. Do it consistently — one bottleneck at a time — and eventually the business runs whether you're in the room or not. Not because you worked harder in it. Because you systematically stopped being the system.

What this looks like in a real business

Picture a trades business — an electrical or plumbing outfit — where the owner personally builds the week's job schedule every time, because only they know which staff member suits which job, how long each job realistically takes, and which customers need extra care.

Here's the cost, plainly. The owner takes a sick day, or just gets slammed with something else — the schedule doesn't get updated. A technician turns up with the wrong gear for the job. Two jobs get booked into the same slot. A regular customer's appointment quietly slips through the cracks because nobody else knew it needed moving.

Name the real bottleneck precisely, because it's not what it looks like from the outside. It isn't that the owner is bad at scheduling. It isn't that the business needs better software. It's that the scheduling logic — who's good at what, how long things take, who needs priority — only exists in one person's head.

The shift is smaller than it sounds. Write that logic down as a simple rule set: skill-matching, standard job durations, flagged priority customers. Once it exists outside the owner's head, someone else — an admin, a dispatcher, even a simple rules-based system — can build and adjust the schedule day to day. The owner only gets pulled in for the genuinely unusual cases. This is small business systems and processes at its most unglamorous — a spreadsheet, not software you buy.

What actually needs to happen

Don't try to fix everything at once. Pick the one task that currently has to go through you the most often, and ask one question: what would it take for someone or something else to handle this instead? Write down what they'd need to know to do it without you — that list is usually shorter than it feels from inside your own head. If you're not sure which one to start with, this is how to pick it.

The real obstacle is rarely a tooling problem. Most owners already have more software sitting unused than they need. The actual obstacle is that nobody has sat down and turned what's in your head into something someone else can follow.

And the goal was never "work less" for its own sake. It's a business that keeps scheduling jobs, keeps quoting, keeps replying to customers, on a day you're not in it. That's what it actually means to work on your business, not in it — a business that keeps running without you, not one that just runs slower.

This is exactly the work SimpliSolve's monthly coaching program does — one bottleneck identified and handed off at a time, with someone else in the room, until the business genuinely doesn't need you for every decision. No pressure to sign up today. Just worth knowing the work has a name, and it isn't "work harder."

Frequently asked questions

What's the difference between working in your business and working on it?

Working in it means you personally do or approve the things that keep it running day to day — quoting, scheduling, replying to customers. Working on your business, not in it means building the systems and people that do those things instead, so the business runs whether you're there or not.

Why does my business slow down every time I take time off?

Because whatever still requires you personally — the schedule, the quotes, the tricky customer replies — simply waits until you're back. That's not bad luck. It's a precise sign of which tasks are still bottlenecked on you.

How do I stop being the bottleneck in my own business?

Pick the one task that goes through you most often, and write down the logic behind it — who's involved, how long it takes, what the priorities are — so someone else can follow it without asking you. That's what turns a business owner bottleneck into a system someone else can run.

What should I hand off first in a small business?

The task you get pulled into most often, not the one that feels most urgent. A weekly scheduling decision is worth fixing before an annual one, even if the annual one feels more painful when it happens.

Does working more hours actually grow a small business?

Not on its own. More hours let you push a few more of today's tasks through — they don't reduce how many things still need you specifically. Growth comes from shrinking that number, not from being available longer.

What does "small business systems and processes" actually mean day to day?

It's rarely new software. It's writing down the judgment calls that currently only live in your head — like which staff member suits which job, or how a quote gets priced — as a simple rule set someone else can follow. That's small business systems and processes in practice, not in theory.

Do I need to fix everything at once to see a difference?

No — and trying to is usually why these efforts stall. One bottleneck, properly fixed and handed off, changes what your business needs from you permanently. Five half-fixed ones change nothing.