How to Stop Being the Bottleneck in Your Own Business
To stop being the bottleneck in your business, understand that your team isn't waiting because they're incapable, they're waiting because nobody has defined where their authority ends. Fix it with two frameworks: a RACI to set who owns each task, and a traffic light system that defines how far people can act before they need you.
Firefighting. As soon as I ask a group of business owners how much time they get pulled into project delivery to fight fires, or to “collaborate” on a deliverable their team should be able to handle, I get nods all around. Founders believe it’s part of the gig. We’re here to dispel that notion.
You have every intention of protecting your time. Then by Monday at 10am you’re interrupted. “Where do I find this?” “What do I do next?” “Am I able to do this?” “Is it okay if…?” Every one of them has landed before you’ve had a chance to start.
That’s what being the bottleneck looks like in practice. Not a dramatic failure, just a slow, daily leak of the hours you needed for the work only you can do.
Here’s the answer: your team isn’t waiting on you because they’re incapable. They’re waiting because nobody has told them where their authority ends. Two things fix it: clarity on who owns what (a RACI), and clarity on how far they can go before they need you (a traffic light system). We’ll walk through both.
This is written for founder-led businesses of roughly ten to forty people, the size where the founder is still the default escalation point for almost everything.
Shouldn’t this be common sense?
If you have a team under your helm, you also know that common sense is a) not common and b) an excuse for poor management. But we don’t blame you.
You didn’t start your business to become a manager. You started it because you saw a gap in the market, or you had a solution to a problem you’d observed. When you grow, most people scale by building a team, and with that come the issues you only find when people are involved. Different dynamics. Different motivators. Keeping people accountable.
Keeping people efficient. Performance management. And so on. The person who founded the business wasn’t born with the skillset to manage people. Nobody hands that to you.
The busier you get, the more people you hire, the more issues arise and the less time you have for the work that genuinely needs you. The slower you get at responding, and the more everything queues behind you.
That’s the mechanism. You’re the bottleneck because the escalation route has become the default, everything comes to you because nothing else has been defined.
Your team are driving tasks, not outcomes. They aren’t leading in their roles. And teams are meant to make you faster, that’s why we have them. They’re meant to bridge the gaps in your own skillset and give more value to your clients. It’s the number one reason we always encourage you not to hire another you.
So what happens instead is that the team learns to chase.
How do we fix it? We give the team authority. They then learn, through the confidence of achieving, to lead.
Step one: get clear on who owns the work (RACI)
Before you can hand over authority, everyone needs to agree on who is actually holding the work. That’s what a RACI does. Four letters against every task or project, and it takes about twenty minutes to map.
Responsible: the person doing the work. Hands on the keyboard.
Accountable: the person who owns the outcome. If it doesn’t happen, or it happens badly, this is who answers for it.
Consulted: the people whose input you need before it’s finished. They shape the work.
Informed: the people who need to know it happened. They don’t shape anything.
Let’s put it against something you’d recognise: a new client onboarding.
Your account manager is Responsible for sending the welcome pack, booking the kick-off, setting the project up in your system. Your operations lead is Accountable, as they own whether that client has a good first thirty days. Your finance person is Consulted, because the contract terms and payment schedule have to be right before anything goes out. And you, the founder, are Informed. You find out it’s done. You don’t approve it.
That last part is where most founders wince. So let’s talk about the three things that make or break this.
One Accountable per task. Non-negotiable. The temptation is to put two names down because two people care about it. What you’ve actually done is remove accountability entirely, because both can reasonably assume the other has it. When something slips, and it will, you want one person to walk it back with. Not a conversation about who thought what.
Consulted is not approval. This is the sneaky one, and it’s usually where founders quietly reinsert themselves. You put your name in the Consulted column because you want visibility, and what your team hears is “don’t move until she’s weighed in.” Suddenly your calendar is full again and you can’t work out why. Being Consulted means your input gets considered. It doesn’t mean the work stops and waits for you.
Informed is a broadcast, not a conversation. A message in the channel. A line in the weekly report. It is not a meeting, and it is not an invitation to reopen the decision after the fact. If you find yourself relitigating things you were only Informed on, your team will stop trusting the map and go back to asking you first.
Here’s the catch, though, and it’s why most founders build a RACI and see nothing change. It tells your team who owns the work. It says nothing about how far they can take it before they need you. So the questions keep landing in your inbox. They just arrive with better attribution.
That’s what the traffic light system is for.
Step two: define how far they can go (the traffic light system)
This is a delegation of authority, and it’s the piece that actually gets your Monday mornings back. You take every decision your team touches and sort it into three colours.
Green. Go. No consult, no check-in, no waiting on you. They make the call and you find out later, if at all.
Amber. They take it to a defined point and then bring you in. The critical word is defined. “Check with me if you’re unsure” is not amber, it’s green with anxiety attached. Amber means: build the proposal, then send it to me before it goes to the client. Draft the response, then run it past me before you hit send. Name the point where they stop.
Red. Nothing happens until the conversation does. These are the decisions with real consequence, financial, legal or reputational and they don’t move without you.
Here’s what it might look like for spend:
Traffic light delegation table showing spending authority tiers for green, amber and red decisions.
Now, the part almost everyone misses.
It looks like a set of guardrails, and for some people it is. But for your good people it does the exact opposite. High performers hedge when they can’t see where the edges are. They’d rather ask an unnecessary question than overstep, because overstepping feels like a career risk and asking only feels like an inconvenience to you. So they ask.
Draw the edges clearly and they stop hedging, because now they know precisely how much room they’ve got. What you’re handing them isn’t a restriction. It’s permission, in writing, that they can point to.
How to actually build one
Don’t start with a blank page and try to imagine every decision your business might face. Start with what’s already happening.
Go back through the last week. Every question that landed on you, every “is it okay if”, every notification that pulled you out of what you were doing, write it down. That list is your first draft. Sort each one into a colour and you’ll have covered most of what actually comes up.
When you’re sorting, set green generously. I know the instinct runs the other way, but in every business I’ve walked into the failure has been under-delegating, not over-delegating. A decision made slightly differently to how you’d have made it costs you far less than a team that can’t move without you.
Green expands with demonstrated judgement, not with tenure. Someone eighteen months in who’s shown you they think it through gets more green than someone who’s been there five years and hasn’t. Say that out loud to your team as it gives the ambitious ones a visible path to more autonomy.
Then review it. Quarterly at minimum, and every single time you hire. A traffic light built for a team of three does not survive a team of six.
If it’s easier to build, do it per role. When I come in to lead a client’s team, I create a traffic light for each role. The newer the role, the less green there is — and as that person builds confidence and time in the business, we should be seeing a lot less red and amber. Reviewing those is also a good way of reading the health of your business, and whether you’re ready to scale with the team you’ve got.
A worked example: the client complaint
This may not land in your inbox often, but it’s the one most founders hesitate over, because of the worst-case scenario. For most of us that’s when things aren’t going well with a client. How could we let our team handle this? Here’s my take.
The RACI
Your account manager is Responsible they respond, have the conversation, sort it out. Your operations lead is Accountable they own whether that client relationship recovers. Your delivery lead is Consulted, because you need to know what actually went wrong before anyone promises anything. You’re Informed.
The traffic light
Green: acknowledging the complaint, booking a call, apologising for the experience, fixing it within the existing scope.
Amber: offering anything outside scope, redoing work at no cost, or extending a deadline. Build the recommendation, then take it to your operations lead. If that’s you, because you don’t have one ( hi, I can help, this is my role) then it comes to you.
Red: discounts, refunds, credits, or anything that touches the contract.
But here’s the real test, and it’s a big part of why so many of my clients hadn’t stepped back or felt able to switch off before we worked together.
It’s 4pm on a Friday. You’re at your daughter’s assembly and your phone is in your bag.
Your account manager reads the email. She acknowledges it within the hour and books a call for Monday morning, because that’s green and she doesn’t need anyone. She talks to your delivery lead, finds out the brief changed halfway through and nobody documented it, and drafts a plan to redo the affected section next week. That’s amber, so it goes to your operations lead, who approves it and if you’re the one wearing that hat, the plan lands with you to review before Monday, so you walk in prepped.
If you have an operations lead, or a fractional general manager, the client has a response, a call in the diary and a plan before you’ve even looked at your phone.
The one thing nobody did was offer money back. That’s red, and red waits until Monday. Which is fine, because nobody asked for it.
That’s the whole point. Not that your team handles everything. That they handle the eighty percent that doesn’t need you, so the twenty percent that does is genuinely worth interrupting your weekend for.
And the reason we keep reiterating that you shouldn’t be sitting in the operations seat is this: as a founder you have three jobs brand, hiring and sales. Operations can be delegated.
Now run your own worst case through it.
The frameworks fail without the behaviour change
You can build both of these beautifully and still have your team in your inbox on Monday, because a framework tells people where the lines are. It doesn’t teach them how to think. That part you have to set as an expectation, and then hold.
Four rules I give every team I work with:
Exhaust every other avenue first. Before it comes to me, you’ve checked the drive, you’ve checked the process doc, you’ve asked the person who did it last time. I’m the last resort, not the first.
Come with three options and a recommendation. Not a problem, anyone can bring me a problem. I want to know what you’d do and which one you’d pick. It also shows me where the knowledge or capability gaps are, so I can help close them.
Tell me your rationale. Not just what you’d choose, but why. This is the bit that actually develops judgement, and it’s how I work out how much green you’re ready for.
Tell me what it costs. How much of your time does this take versus mine? Most people have genuinely never considered it. Once they do, half the questions stop, because they realise they were about to spend forty minutes of my time to save themselves five.
Now the honest counterpart, because this is a two-way street, and it’s where a lot of my clients need support themselves.
None of it holds if you don’t hold up your end. If your team brings you a red and you take three days to answer, you’ve taught them the system doesn’t work. They’ll go straight back to chasing, and they’ll be right to.
When you narrow the number of things that come to you, the deal is that the things that do come get answered fast. Same day, ideally. That’s the trade you’re making, and you don’t get the quiet without it.
For busy founders, which is most, I also set up a daily approvals window, so questions and notifications aren’t infiltrating your whole day. One time set aside, everything batched into it.
What the first month actually feels like
I’d rather tell you this now than have you abandon it in week two. It gets noisier before it gets quieter.
People will test the lines, mostly by bringing you things that are clearly green, because they’re checking whether you meant it. Every time you answer one of those instead of sending it back, you undo a bit of the work. Send it back. Kindly, but send it back.
And some decisions will get made differently to how you’d have made them. Not wrong. Just not yours. This is the actual cost of the trade and there’s no version of this where you avoid it. You have to let most of them stand, because the moment you start overturning green decisions, everything quietly reverts to amber and you’re back where you started.
You might also surprise yourself. Sometimes the team does it better than us, that’s why we hired them, right?
Give it a month before you judge it. Around week four is when the questions drop off and you notice you’ve had a whole morning to yourself.
And if you do all this and they still don’t step up?
Then you have a people issue, not a structural one. That’s a real thing and I’m not going to pretend otherwise.
But here’s the order I work in, and I’d ask you to hold to it: we don’t assume. Frameworks first, always. Because the founder who tells me a team member is disengaged is usually describing someone who has never been told what they own, has never been given room to move, and has been quietly corrected every time they tried. That’s not an attitude problem. That’s a person who’s learned that initiative is expensive.
Give it a proper run. Clear ownership, clear authority, expectations set out loud, and you holding up your end. If someone still isn’t leading in their role after that, you’ll know — and you’ll know it clean, with evidence rather than a feeling. That’s a performance conversation you can actually have, and it’s a very different one to the conversation you’d be having now.
Common questions
My team asks me everything. Where do I even start?
Start with a week of evidence rather than a blank page. Write down every question that lands on you for five working days. Most founders find the same three or four themes repeating, spend, client communication, scope, and “am I allowed to”. Sort that list into green, amber and red, and you’ve built the first version of your traffic light from real data instead of guesswork.
How is this different from just delegating tasks?
Delegating a task hands over the work. Delegating authority hands over the decision. Most founders do the first and skip the second, which is why the work leaves your desk but the questions don’t. The traffic light is what makes the difference.
How much should I put in green to start with?
More than feels comfortable. In practice, under-delegating is the far more common failure, and the cost of a decision made slightly differently to yours is almost always lower than the cost of a team that can’t move without you.
Do I need a full RACI for the whole business?
No. Start with the three or four processes that generate the most questions, usually onboarding, delivery, spend and client escalation. That covers the bulk of what interrupts you.
You didn’t come here for a framework
You came here because you want a week where you can think. Where Monday at 10am belongs to you, and your team is moving without needing a piece of you to do it.
That’s what these two tools buy you.
Start here. I’ve built the traffic light I use with every client, with the categories already mapped so you’re not starting from scratch. Grab it below, spend twenty minutes on it this week, and take it to your team.
And you don’t have to do it alone. If you’d rather talk it through, founder to founder, book a calland I’ll either point you in the right direction or show you how we’d do it together.
