You Don't Have A Systems Problem. You Are The System.

If you've been running a venue for a few years, someone has already told you that you need better systems. A consultant, a supplier rep, a bloke on LinkedIn. And every time you hear it you think the same thing, which is that you've got systems. You've got a rota system. You've got an ordering system. You've got a stock system. The place turns over seven figures. It didn't get there by accident.

So the advice bounces off, and it should, because it misses the actual problem.

The problem isn't that you don't have systems. It's that you are one. You're the bit in the middle that all the other bits pass through. The rota system works because you check it. The ordering system works because you know what a normal week looks like. The standards hold because you're on the floor to hold them. Take you out and it isn't that the systems fail. It's that there was never really a system there, just you moving quickly.

That's not a criticism, and it isn't a character flaw. It's the logical result of how you came into ownership. Money was tight in year one and year two and probably year five, and you learned that saving money means doing it yourself. That logic built the business. It's now the thing keeping you inside it.

I spent ten years doing exactly that, and I won awards while I was doing it, which is what made it so hard to see.

What follows is the four pieces of work that move a founder out of the middle. They're in a specific order, and the order does most of the work.

One. Look Inward

You can't hand anything over until you can see clearly what you're holding. And almost no founder can, because it's never been written down. It's just the shape of your week, and you're too far inside it to see the shape.

Ask a hospitality founder how many hours they work and they'll say fifty. What they've counted is the shifts they're rostered on. They haven't counted the Monday that's supposed to be a day off, which is when the ordering gets done and the rota gets written and the invoices get paid. The real number is usually sixty five to seventy five.

So the first job is a two week time audit. Set a timer every fifteen minutes and write down what you actually did in that block. Not from memory at the end of the day, because memory tidies it up and turns forty minutes of scrolling into "admin". Two weeks, not one, because one week isn't enough variety to show you the real rhythm.

Then go through it twice. Once with two colours, green for anything that gives you energy and red for anything that drains it. Two tasks can take the same forty minutes and leave you in completely different states, and until you see it written down you'll be guessing.

Then again, rating every task one to four by what it would cost to have someone else do it. A one is basic admin almost anyone could be shown. A four is work where you'd effectively be paying someone to do your job as the owner.

Everything that came out red and rated a one or a two is your bucket. Most founders find eight to fifteen hours a week sitting in there. That's a working day and a half, every week, going on things that drain them and that somebody else could do for a fraction of what their time is worth.

One thing that surprises people. Most founders assume the audit will prove they need to hire. Often it proves they're leaking serious time before they get anywhere near needing another wage.

Alongside it, once a month, write down seven things. Hours worked. Days properly off. Nights on the floor. Times you got called on a day off. Your latest finish. Weeks since a holiday. And one line on how the month felt. You track the business obsessively and yourself not at all, which means you're relying on a feeling, and feelings in this industry are unreliable because everyone around you is tired too, so tired reads as normal.

Two. Establish Rhythm

Your week isn't designed. It's defaulted to. And what costs you isn't the interruption, it's waiting for it. A twenty minute phone call takes the whole day, because the four hours before it were spent half braced for it and the three hours after were spent getting back.

Rebuild the week in three layers, in this order.

The operational layer. Write down every recurring task in the business, who owns it now, and who should own it. That second column is the exercise. Most founders find their name against fifteen things where it has no business being, not because they chose it, but because in year two there was nobody else and nobody ever went back and changed it.

The personal layer, and this goes in before the operational week, not after. Everybody puts these in last, in whatever's left, which means they get nothing. Don't frame them as balance, because that framing collapses the first time you're short staffed. Frame them as the conditions under which you're any good at your job.

The energy layer. Look at the week you've built and work out where the pressure will land before it lands. Most of what wrecks a founder's week isn't unforeseeable. It's foreseeable and unplanned for, which are different things.

Then build a rhythm the business runs on rather than one that runs on you being interrupted. A fifteen minute daily where each person says what they did, what they're doing and what they're stuck on, and where your only job is clearing the stuck list. A weekly focused on how the week actually went. A quarterly for planning. And then, critically, run the plan rather than re-deciding it every morning.

Last, defend what you get back. You'll free up hours in the first fortnight and the business will fill them within a month. Protected blocks need a name and a purpose, and the team needs to be briefed to defend them, because if the only person defending your time is you, you'll lose.

And decide what fills it before you have it. Because if reclaimed time doesn't have a job, it becomes shifts.

Three. Align Your Energy

At some point, without deciding to, most founders start measuring their worth by how much can't happen without them. Being needed becomes the proof that they built something. Which means every structure that makes them less necessary registers, somewhere underneath, as a threat.

That's why founders install good systems and then quietly undermine them. It isn't laziness. It's that stepping back costs them something they can't name.

The shift, and it is the whole shift, is from "I'm needed" to "I've built something that holds".

Practically, that means checking your own tank once a week rather than only checking the diary, because a founder at four out of ten makes a Friday night decision that a founder at eight would never make. It means tracking where energy leaks rather than just where time goes. It means being able to answer the question of when you last did something that had nothing to do with the business and everything to do with just being you, because when the business is your whole identity, delegating a piece of it feels like delegating a piece of yourself.

And it means putting reclaimed energy somewhere that compounds. Into habits worth changing. Into beliefs worth testing, because "the team can't handle a Saturday without me" might be true, and might also be four years untested. Into acting like the owner you're becoming before it shows up in the numbers.

Here's my proof for this one, and it isn't a nice one. When Ojo Rojo closed, it closed on somebody else's terms with six weeks notice. I read that email and stayed calm. Nothing collapsed. The version of me from four years earlier would have come apart entirely, and I know that because much smaller things had already taken him apart.

The business ended. The foundation held.

Four. Direct With Clarity

This is where stepping back becomes permanent, and where decisions and standards move off you and into other people.

Stop taking problems and start taking recommendations. When someone brings you something, they bring the problem clearly stated, three options they've considered, and the one they'd go with. The first few times they'll say they don't know, which is why they came to you, and you ask how long they'd need to work it out. Almost always they come back with something good. The founder who complains their team can't think for themselves has usually trained them not to, one quick answer at a time.

Set a decision ladder so everyone knows what they can decide and spend without asking. Anyone on the floor can resolve a guest problem up to a set amount. A supervisor higher. A manager higher again. The numbers matter less than the fact that they exist. Without a ladder, every judgement call defaults upwards, and then you're frustrated at being interrupted over a decision you never gave anyone the authority to make.

Hand work over in a way that survives. For repeatable work, record yourself doing the task and talking through why, then have the person write the procedure from the recording. What they write back tells you whether they understood it, which is a better test than asking if they have questions. For anything judgement led, split it. You take the first ten percent to agree what good looks like, they take the middle eighty as the author, you come back for the last ten to refine.

Write playbooks for the handful of things that have to go the same way every time. Opening. Closing. A complaint. A supplier failing on a Saturday. Same principle as a recipe on the section. The reason standards drop when you're not there isn't that the team don't care. It's that the standard only ever existed in your head.

Give ownership rather than task lists. Give someone a checklist and they'll do the checklist and watch a problem develop next to it, because the problem wasn't on the list.

And this is the part of the whole framework that does most for staff retention. People don't leave venues because the work is hard. They know it's hard, they chose it. They leave because they've stopped growing, and nothing stops someone growing faster than working for a founder who owns every decision in the building. Your best people feel that first, which is why they're the ones who go.

Then test it. Pick a period, tell the team in advance, and go properly unavailable. You find out where the gaps are, and you get the only evidence that ever really shifts the belief.

Why the order is the point

Most founders start with the fourth pillar, because it's the obvious one. Delegate more. Give the team authority. Write the procedures. It's the advice everybody gives, and it fails constantly. Founders hand over a chunk of the business, watch it wobble, take it back, and conclude the team can't be trusted.

It fails because it was fourth work done first. You can't hand over what you haven't seen. You can't protect the space a handover needs while your week is still defaulted to. And you'll quietly undo all of it if being needed is still the thing telling you you built something worth building.

You can't talk a founder into believing the place doesn't need them. I've tried it on myself and it doesn't take. What works is the other way round. You put structures in, you watch them hold through a bad week, and the belief arrives behind the evidence rather than in front of it.

What it actually buys

Not a lighter workload. I'd be selling you something if I said that.

A day off that's actually a day off. A business that holds when you step away. A weight that's shared rather than carried alone at three in the morning. And the one that makes the others stick, which is that you become the owner again rather than the most expensive employee and the only one who can't call in sick.

And then the part founders underestimate. The most capable, most invested, most experienced person in the building stops spending their week on twelve pound decisions and starts spending it on the things only they can do. Where the money is actually going. What's quietly leaking margin. Where the next bit of revenue comes from. Which of your people is ready for more and needs to hear it this month rather than next year.

That's how a place gets more profitable, runs more efficiently and keeps hold of its good people. Not by the owner working harder. By the owner finally being available to do the owner's job.

Start with two weeks of tracking. Everything else follows from knowing what's actually in your week.

The full video is on The Lead Well Channel on YouTube.