top of page
Waggle Dance Ltd Company Logo

The Bottleneck Map: Why You’re Always the Problem

7 days ago
8 min read

It’s 4.40 on a Thursday. You’ve spent most of the day answering questions, checking quotes and calming down a client who wasn’t happy with a delivery date. The proposal you meant to finish before lunch is still open on your laptop, roughly where you left it at ten.


Then someone appears at your desk with “just a quick one”.


You hired people so the business wouldn’t rest entirely on your shoulders. So why does so much of it still need to pass through you?

founder bottleneck

What is a founder bottleneck?

A founder bottleneck happens when routine work cannot move without the owner’s knowledge, approval or involvement. The team may be capable and busy, yet decisions queue behind one person, slowing delivery, sales and growth.


If that person is you, it doesn’t make you a control freak or a nightmare to work for. More often, the business has simply learnt to lean on you in ways that made sense five years ago and quietly stopped making sense since.


How being useful turns into being in the way

In the early days, answering everything was the only option. You knew the customers, did the work and paid the bills, and there wasn’t anyone else to ask anyway.


Hiring changed the headcount. It didn’t always change where the knowledge lived.


So now someone prepares the quote, and you approve it. Someone runs the project, but you decide which deadline really matters. Someone looks after the customer, though only you know what was agreed on the phone last Tuesday. The work has been handed over in pieces, with you still sitting in the middle of each one.


What it looks like in an ordinary agency

Take a small web design agency. (This is an illustrative example rather than a client case study.)


The project manager has a proposal ready to go but needs the founder to check the price. A designer is waiting to find out whether an extra page counts as a revision or new work. Meanwhile, a client wants a launch date, and nobody will commit to one without looking at the founder’s diary first.


Three sensible questions, all waiting on one person who happens to be in a meeting until three.


Nobody here is short on effort. What’s missing is clarity on pricing rules, scope and capacity, written down somewhere the team can actually use. Hire another person into that setup, and you’ve mostly added another person who needs to ask.


Why you keep taking back the work you meant to hand over

“Just let go” is easy advice to give when you’re not the one covering payroll or fielding the angry phone call.


Your caution usually has a backstory. Maybe someone made an expensive mistake once. Maybe you passed something on without much explanation and spent a Saturday fixing it. Taking the work back felt like the responsible thing to do, and at the time it probably was.


The trouble is what the team learns from it. Every rescue reinforces the same habit, which is that anything tricky goes to the founder.


The thirty-second answer that keeps coming back

On a busy afternoon, explaining a pricing decision takes ten minutes. Making it yourself takes thirty seconds. Most people pick the thirty seconds, and honestly, who could blame them.


Then the same question turns up next week, and the week after. You saved a few minutes once and signed up for the dependency indefinitely.


Then there’s the sneakier version. You tell someone to use their judgement. They do, and it’s fine, honestly, but it’s not how you’d have done it, so you tweak it. Maybe you rewrite the email; maybe you nudge the price up a bit. You probably don’t even think of it as overruling anyone. They do, though. After the second or third time, most people decide it’s easier to just check with you first.


Sometimes the person genuinely needs more training. Other times the issue is a greeting in an email that you’d have phrased differently, which, irritating as it may be, doesn’t really need the managing director’s attention.


Software won’t untangle this on its own, either. A shared platform can hold customer history, deadlines and next actions, but it can’t decide who’s allowed to change a price until you’ve agreed that between yourselves.


The head chef at the pass

Picture a busy restaurant kitchen. Every plate goes to the pass, where the head chef checks it before it reaches a table. With twenty covers on a quiet Tuesday, that works nicely, and the standards stay high.


Book in a hundred and twenty on a Saturday, and the same arrangement starts to creak. Plates go cold under the lights. Servers hover. The chef is still doing a good job of checking, which is rather the problem, because the checking has become the thing holding up dinner.


Good kitchens deal with this by training section chefs to the same standard and letting them send out what they’re confident in. The head chef doesn’t vanish. They just stop being the only door out of the kitchen.

How to build your bottleneck map

None of this needs an away day. A sheet of paper, a pen and a week of honest noticing will get you most of the way.


1. Trace a real job from start to finish

Sketch the journey of one ordinary piece of work: enquiry, quote, booking, delivery, invoice, follow-up. Adjust the stages to suit your business.


Then pick a recent job and follow what actually happened, rather than the tidy version you’d put in a process document. Mark every point where the work couldn’t move until you responded. Being involved isn’t the same as being a blockage, so be strict about it.


For the next working week, jot down interruptions as they happen. “Checked quote” won’t tell you much later. Something like “approved a standard renewal because nobody knew if last year’s rate still applied” gives you a problem you can actually fix.


It’s worth asking the team what they regularly wait on you for, too. Try not to explain why each answer is unavoidable. You asked for a map, not a defence.


2. Work out what’s actually missing

A question that keeps coming back usually points to something more specific than “poor delegation”.


If only you know what the customer agreed to, that would be an information gap. If everyone knows the situation but nobody feels authorised to act, that’s an authority gap. Someone might have permission but not yet the skill to make a sound call, or they might have both and still hold back because they’ve been corrected before.


Each of those needs a different fix. A written process won’t help someone who’s worried about being second-guessed, and a pep talk won’t teach anyone to do a complicated job.


Some decisions should stay with you, particularly where financial, legal, safety or professional obligations are involved. Mark those clearly so they don’t get lumped in with the ones that are just habits.


3. Start with the queue that costs the most

The interruption that annoys you most isn’t necessarily the one to tackle first. Look instead at what does the most damage when it waits.


A proposal sitting in your inbox may be holding up revenue. A delayed delivery decision could leave a customer let down. A social post waiting for your preferred adjective is, on balance, probably fine for another day.


Consider how often each delay happens, how long things sit and what’s affected. Then choose one, and resist redesigning the whole business over a bank holiday weekend.


4. Put your judgement into words, then hand it over properly

Quote approval is a good place to practise. Rather than “send everything to me”, agree which standard jobs a trained colleague can quote on their own, which pricing rules apply and which exceptions still come to you.


Go through a handful of recent examples together. Talk about why a rush job is priced differently, why an odd scope needs a second look and why a long-standing customer doesn’t automatically get a discount. Write the reasoning down somewhere easy to find. A two-page guide people actually open is worth far more than a polished manual that lives in a folder nobody visits.


For regulated or safety-critical work, keep the sign-offs you need. You’re cutting unnecessary waiting here; there's no necessary oversight.


5. Review the work without taking it back

Start with a manageable trial and agree on a time to look through a sample of the work together.


If something goes wrong, find out why before reaching for the reins. Was the rule unclear? Was information missing? Did they need more practice, or did they step outside an agreed boundary? One wobble isn’t proof that delegation doesn’t work.


Check their capacity as well. Handing someone a responsibility when their diary’s already full just moves the queue to a different desk.


After a fortnight, look at the work itself. Are standard quotes going out sooner? Are fewer jobs waiting for approval? Are errors and complaints within a level you’re comfortable with? A drop in questions alone doesn’t tell you much, since people sometimes stop asking while the work stays stuck. A suspiciously quiet office deserves a closer look.

Today's Deep Dive

What to do next

Being needed can feel reassuring, right up until you try to take a Friday off. The aim isn’t to make yourself irrelevant. It’s to spend your attention where it adds the most, and the right support depends on what your map turns up.


If customer details and follow-ups mostly live in your inbox, Waggle Dance CRM gives the team one shared place to manage customer work. It’s built on GoHighLevel, set up for UK service businesses, and costs £149/month + VAT.


Already got a CRM, and mostly happy with it? Then we’d probably look at tidying up what you’ve got before suggesting anything new. Most of the time the issue isn’t missing features anyway. It’s that nobody’s quite sure who owns which customer or what’s meant to happen after the first call.


Where the sticking point is delegation, priorities or keeping new habits going, the £499/month +VAT coaching bundle includes the CRM plus fortnightly business coaching. Why We Use CoachAccountable for Business Coaching (And You Get It Too) explains how the work between sessions stays visible.


And if you’d like a concentrated look at strategy and systems together, a Dark Room Strategy Day is another option. The Dark Room Method: How We Help Founders See What They Can’t covers why familiar habits are so hard to spot from inside your own business.


FAQs

How do I know if I’m the bottleneck in my business?

Look for routine work that regularly waits for your approval, knowledge or input. If a couple of days away leaves capable colleagues unable to move, those dependencies are worth examining. Some approvals are necessary, while others survive simply because nobody has questioned them.

It can help with missing information, unclear next steps and patchy follow-up. It won’t resolve authority, skill or trust problems on its own, so agree how decisions should be made before expecting software to sort them out.

It’s a CRM built on GoHighLevel for UK service businesses, priced at £149/month +VAT. The coaching bundle is £499/month +VAT and includes the CRM plus fortnightly business coaching.

Yes. Waggle Dance offers CRM optimisation, systems and process design, strategy and business coaching. There’s no need to replace a platform that’s working in order to fix the decisions and habits around it.

If your name turns up at every junction on the map, book a free Clarity Call. Bring one example of work that keeps waiting for you, and we’ll start there.

 
 
bottom of page