Lesson 20: The Bottleneck Problem

Let me paint a picture you might recognize.

You go on vacation. First day, things run fine. Second day, questions start piling up. Third day, things are stalling because decisions aren’t getting made. By day five, your inbox is a disaster and at least one thing has gone sideways because nobody knew what to do without you.

You come back, put out the fires, catch up on the backlog, and think: “See? They can’t function without me.”

But that’s the wrong conclusion. The right conclusion is: “I haven’t built systems that function without me.” That’s not their failure. It’s yours.

The Presence Problem

The bottleneck problem isn’t about your capability. You’re probably very capable. That’s partly why things depend on you — you’ve been the most capable person in the room for a long time.

The problem is required presence. The requirement that YOU specifically must be involved for things to work. When your presence is required, your absence breaks things. And since you can’t be everywhere all the time, your presence-dependency caps the entire system.

Every decision that waits for you is time someone else spent waiting instead of working. Every approval that requires your sign-off is a day of delay that wouldn’t exist if the approval criteria were codified. Every problem that only you can solve is a single point of failure in your operation.

Mapping Your Bottlenecks

Get specific. Vague awareness that “things depend on me” doesn’t help. You need to know exactly WHERE and WHY.

Work that stops. What literally ceases when you’re not available? Not “slows down” — stops. These are your critical bottlenecks. If you disappeared for a month, these would be the things that created real problems.

Decisions that wait. What decisions pile up until you’re available to make them? These reveal where authority hasn’t been distributed. Someone could probably make these decisions — they just don’t have permission or criteria.

Quality that drops. Where does output quality decline without your personal review? This reveals where standards exist only in your head and haven’t been translated into documentation or training.

People who are blocked. Who specifically is waiting for you on a regular basis? Not occasionally — regularly. These are the people whose productivity you’re capping with your bottleneck.

The Honest Question

Here’s the question that cuts through everything: if you were gone for a month, what would continue functioning and what wouldn’t?

The “would continue” list shows where you’ve built genuine systems. The “wouldn’t continue” list shows where you ARE the system.

Most people’s “wouldn’t continue” list is longer than they want to admit. That’s okay. Seeing it clearly is the first step to changing it.

Why Bottlenecks Persist

If bottlenecks limit scale, why don’t people eliminate them? Three reasons:

It feels good to be needed. Being the person everyone depends on is a powerful identity boost. You’re important. You’re central. Without you, things fall apart. That feels like value. But it’s a trap — because the more needed you are, the less scalable your operation becomes.

Distributing authority feels risky. What if they make the wrong call? What if quality drops? What if things go off the rails? These fears are real but manageable. Lesson 14 covered how to delegate with clear frameworks. Those same frameworks address the risk of distributed authority.

Building systems takes time. Documenting your decision criteria, training others, building feedback loops — all of this takes time you don’t have because you’re busy being the bottleneck. It’s a catch-22 that you break by investing time now to save time permanently.

The Alternative

Imagine your operation where:

Decisions get made within clear frameworks, without waiting for you
Quality is maintained through standards and feedback systems, not your personal review
Problems get solved by capable people with appropriate authority
You spend your time improving the system, not running it

That’s not fantasy. That’s what properly designed environments produce. And it starts with identifying exactly where you’re the bottleneck right now.

Today’s Practice

Map your bottlenecks with specifics.

What work stops when you’re unavailable? List every item.
What decisions wait for you? List the recurring ones.
Where do people get blocked by your absence? Name the people and the blockages.
If you were gone for a month, what would survive? List it.
What would NOT survive? List it. For each item, note WHY — is it missing documentation, authority, training, or something else?

This bottleneck map is what you’ll work with for the rest of Unit 2. Each bottleneck is a design opportunity — a chance to create conditions that eliminate the dependency on your personal presence.