The Founder Bottleneck Test

Why so many decisions end up with the founder, and how to stop being the default answer.

Founders often worry that they are too involved in the business. Too many decisions, too many questions, too many things waiting for their approval.

The obvious conclusion is:

I need to delegate more.

Sometimes that is true.

But delegation is often treating the symptom.

The issue is usually that too many decisions don’t have an obvious home. When ownership, boundaries, or context are unclear, decisions tend to travel upwards.

And eventually, they land with the founder.

Why everything ends up with you

Imagine a team trying to make a fairly ordinary decision.

A customer wants an exception. A supplier asks for something slightly unusual. Someone wants to change a process. A project needs a decision that sits between two teams.

Nobody is completely sure what the right answer is, so someone asks the founder.

The founder gives an answer.

Problem solved.

Except the same thing happens again next time.

Slowly, asking the founder becomes the safest route whenever the answer isn’t obvious. Not because the founder wants control, and not because the team is incapable.

It happens because getting the founder involved has become the easiest way to get the decision made.

The Founder Bottleneck Test

Look at the decisions that reached you over the last week.

For each one, ask two questions.

1. Did this genuinely need me?

Was it:

• strategic?

• high-risk?

• difficult to reverse?

• something only I could decide?

If yes, fine.

2. If it didn’t need me, why did it reach me?

Usually the answer falls into one of four buckets:

Clarity
Nobody knew who owned the decision.

Confidence
Someone probably knew the answer but didn’t feel comfortable making the call.

Context
The information needed to decide wasn’t available to the person making it.

Constraint
A rule, approval step or process forced the decision upwards.

Those are four very different problems.

“Delegate more” doesn’t solve all of them.

Count the decisions that shouldn’t reach you

Most founders don’t count the decisions they make.

They just feel the weight of them:

• the questions

• the approvals

• the messages that start with “quick one”

• the things that seem to need their view before they can move

Instead of trying to measure all of that, ask one simpler question:

How many decisions reached me that shouldn’t have?

Every unnecessary escalation tells you something about how the company is operating.

Five questions about pricing might mean your pricing rules aren’t clear.

Three hiring approvals might mean managers don’t know their boundaries.

A constant stream of customer exceptions might mean the policy itself is wrong.

Repeated project escalations might mean nobody has clear decision rights.

The question isn’t:

How do I answer these faster?

It is:

Why did this have to come to me at all?

Fix the route, not the founder

When you spot a recurring escalation, don’t simply tell people to stop asking you.

Remove the reason they need to.

• If the problem is clarity, name the owner.

• If it is confidence, make the decision boundary explicit.

• If it is context, give people access to the information.

• If it is constraint, remove the approval step.

The goal isn’t to make yourself unavailable.

It is to make fewer everyday decisions depend on you.

Try this for one week

Keep a simple note called:

Decisions that shouldn’t have reached me

Whenever one lands with you, capture:

• What was the decision?

• Who brought it to you?

• Why do you think it needed your involvement?

Don’t overthink it.

At the end of the week, look for repetition.

You are not trying to create a perfect delegation framework. You are trying to find the places where ordinary decisions keep travelling upwards.

Pick the most common one.

Fix the cause.

A common mistake

Founders sometimes respond to this problem by disappearing.

“Don’t ask me. You decide.”

That sounds empowering.

But if people still don’t know the rules, context or boundaries, all you’ve done is remove the safety net.

Good autonomy isn’t the absence of leadership.

It is clarity without escalation.

The check

Ask yourself:

If I disappeared for two weeks, which decisions would stop moving?

Not the big strategic ones.

The ordinary, repeatable decisions.

Those are your bottlenecks.

Done looks like this

The business doesn’t stop asking you questions.

It stops asking you the same kinds of questions.

That’s the sign that decisions are starting to happen in the right place, without needing you in the middle of everything.

COO in a Box

Run a better business. One operating idea at a time.

Written anonymously by an experienced COO, co-founder and operator.

Growing businesses have a habit of fixing problems where they appear.

A customer waits too long, so we add another person to customer service. A project slips, so we add another status meeting. A team keeps making mistakes, so we add another check. Someone can’t make a decision, so the founder gets pulled back in.

Sometimes that works.

Quite often, though, we’ve just added more process around the real problem.

Because the place where friction appears isn’t necessarily the place where it starts.

The problem you can see isn’t always the problem you have

Imagine customers are waiting three days for answers to fairly simple questions.

The obvious conclusion is that customer service is too slow.

So you improve the acknowledgement email. Set a tighter response target. Maybe add another person to the team.

All perfectly reasonable.

But none of that tells you why the answer takes three days.

Look a little deeper and you might find something else going on.

The customer team receives the question but can’t answer it themselves. They send it to Marketing. Marketing sends it to Sales. Sales needs something from Finance. Eventually, somebody asks the founder.

Three days later, the customer gets their answer.

The customer sees slow service.

Inside the business, the work is bouncing between teams.

Underneath that, nobody clearly owns the decision.

That is the Friction Map.

The visible problem is often the end of the chain, not the beginning.

Three places friction hides

Most recurring friction sits in one of three places.

01 - CUSTOMER FRICTION

This is what the customer feels.

Waiting too long. Not knowing what happens next. Having to chase. Repeating information they’ve already given you. Finding something harder to buy, use or get help with than it needs to be.

Customer friction is usually the easiest to spot because customers tell you about it.

But it isn’t always where the problem starts.

02 - OPERATIONAL FRICTION

This is how the work behaves inside the business.

Work sits in queues. It changes hands unnecessarily. The same information gets entered twice. People create workarounds because the normal process doesn’t quite work. Things need checking, correcting or chasing.

This is often where the customer problem is actually being created.

03 - ORGANISATIONAL FRICTION

This is why the work behaves that way.

Nobody clearly owns the outcome. Two teams are working to different priorities. People need permission for decisions they should be able to make themselves. Important knowledge sits in one person’s head.

This is where a surprising amount of everyday friction begins.

The three categories are useful to understand but the more important thing is the relationship between them. Friction travels downstream. Diagnosis should travel upstream.

Start with a different question

When something keeps going wrong, the natural reaction is: How do we fix this?

Before answering that, ask: Where does this actually start?

That small shift changes how you look at the problem. If you fix friction too far downstream, you can end up making the symptom easier to live with without removing the cause.

A better customer email might make a three-day wait feel more professional. It still doesn’t make the answer arrive any faster.

A new workflow might move a request neatly between five people. It still doesn’t explain why five people need to be involved.

I’ve seen businesses build surprisingly sophisticated processes around problems that could have been stopped somewhere else.

YOU WILL NEED

• One recurring annoyance in your business

• 15 minutes

• Ideally, someone who actually does the work

Don’t try to map the whole company.

Pick one thing that keeps happening and annoys you every time it does.

STEP 01 - Start with the symptom

Write down what is actually happening, without jumping straight to the solution.

Maybe:

• Customers keep chasing us.

• Quotes take too long.

• Projects get stuck before launch.

• Refunds always need senior approval.

• People keep asking me the same question.

Be specific.

“Communication needs improving” tells you almost nothing.

“Every project needs three messages before anyone knows whether it has been approved” gives you something you can actually investigate.

STEP 02 - Trace it upstream

Now follow the problem backwards through the three layers.

Start with the customer or visible symptom.

Where is someone waiting, guessing, chasing, repeating themselves or doing work they shouldn’t need to do?

Then look at the operation.

What is happening inside the business to create that experience? Where is work waiting, changing hands, being entered twice, corrected or worked around?

Then look underneath that.

Who owns the outcome? Who is allowed to make the decision? Are two teams working to different priorities? Does someone need permission they shouldn’t need? Does critical knowledge live with one person?

Keep tracing until you reach something that, if changed, would remove some of the friction further down the chain.

That’s usually where things get interesting.

STEP 03 - Fix the highest useful cause

You don’t automatically need to fix all three layers.

And you don’t need to keep digging just because you can.

Sometimes confusing checkout copy is simply confusing checkout copy. Fix it.

Sometimes somebody is manually copying information between two systems. Fix the workflow.

Sometimes six people are involved because nobody is quite sure who is allowed to say yes.

That’s usually the point where I’d stop mapping.

The aim is to find the highest useful cause: the earliest sensible point in the chain where one change removes friction below it.

COMMON MISTAKE

Mapping the whole business.

Resist the temptation.

This does not need to turn into a transformation programme, a wall covered in Post-it notes or three weeks spent documenting every process in the company.

Take one recurring problem.

Trace it. Fix it. Then take another.

CHECK

Ask:

If we fix this cause, should the friction below it disappear without creating more effort somewhere else?

If the answer is yes, you’ve probably found the right place to intervene.

If not, keep tracing.

DONE

You should eventually be able to describe the problem in one short chain:

Customers wait for answers
because work keeps changing hands
because nobody clearly owns the decision.

Once you can see the chain, deciding what to fix becomes much easier.

Growing businesses naturally accumulate friction.

More people create more handoffs. More products create more exceptions. More teams create more dependencies.

You won’t remove all of it.

But you can stop building solutions around symptoms.

Next time something keeps going wrong, don’t ask where the problem is visible. Ask where the friction starts.

COO in a Box

Run a better business. One operating idea at a time.

Written anonymously by an experienced COO, co-founder and operator.