Walk through your office on a Wednesday afternoon and count the number of things that are paused waiting for a decision from you.

Not big things. Small ones. An email that needs an approval. A vendor invoice that needs a signoff. A client question that needs a yes or no. A team member who is not sure whether to book the travel or hold off. A proposal sitting in a draft folder because you said you would give it a final read yesterday.

If you can find four pending items in ten minutes of walking around, you are the bottleneck. Your team is not slow. Your team is waiting. And every hour they spend waiting is an hour they are not producing, which is a cost that does not show up in any financial report but shows up in every revenue number.

The Real Problem

You have trained the business to need you.

This is not a criticism. It is a description. In the first few years of running the company, you had to be involved in everything. There was no one else. Every decision went through you because every decision had to. Then the team grew. Then the company grew. But the habit of every decision going through you stayed, because nobody explicitly renegotiated it.

The team operates under a rule that was never written down: when in doubt, ask the owner. So they ask. Dozens of times a day. Each ask is small. Each ask is reasonable. Each ask is also a tax on your calendar, and in aggregate, the tax is what is keeping you from doing the work only you can do. The bottleneck is not a failure of leadership. It is the natural result of leadership that never got upgraded as the team grew.

Why This Happens

The bottleneck persists because it feels productive. Answering twenty team questions in a day feels like leading. You are being responsive. You are being helpful. You are giving the team what they need to keep moving. Every individual answer is useful. The aggregate effect is that you are doing a kind of work that fills the day without producing anything the business will remember in six months.

Worse, answering the questions reinforces the pattern. The team learns that asking is faster than deciding, which means asking gets easier, which means more asking, which means more answering. It compounds in the wrong direction. Nobody in the system is doing anything wrong. The system itself is badly designed, and only the owner can redesign it, because only the owner is at the top of the asking tree.

Four Moves That Unwind The Bottleneck

1. Name the decisions that keep landing on your desk. For one week, track every decision a team member asks you to make. At the end of the week, categorize them. Most will sort into four or five recurring buckets (pricing exceptions, scheduling conflicts, client escalations, vendor approvals, and so on).
2. For each bucket, define the authority level and pass it down. "Under three hundred dollars, approve without asking. Over three hundred, confirm with me. Over two thousand, we discuss." Simple thresholds. Written down. Shared with the team.
3. Run a weekly fifteen-minute decision review with the team instead of a hundred individual asks. Monday. Everyone brings the decisions they made the previous week in the "confirm with me" category. You confirm or correct. Everyone learns from everyone else's judgment. The forty individual asks become one block of time.
4. Hold the line when the team tries to ask outside the system. "That is a decision you can make. If you want to talk through it, bring it to Monday." Say this kindly, say it consistently, for about six weeks. The team will adapt. They always do. Usually faster than the owner expected.

What This Looks Like Lived

A services firm owner ran this process. Her first week of tracking, she logged fifty-eight team asks. The next week, she installed thresholds and the Monday review. Three weeks in, asks were down to twelve per week, almost all legitimate decisions that should have involved her. Six weeks in, she took a four-day trip, and nothing escalated. The business ran.

The less obvious outcome was how her team felt. She had expected them to resent the new structure. They did the opposite. They liked knowing what they could decide. They liked that Monday review made the judgment calls easier. They started making better decisions, because they had ownership of the outcome, which they had never had before. The bottleneck was not just slowing the business. It had been holding the team back from growing, in a way that was invisible until it dissolved.

Answering twenty team questions feels like leading. It is mostly a kind of work that produces nothing the business will remember in six months.

What To Do This Week

Starting tomorrow, for one week, track every decision a team member brings to you. Write down what they asked, what you answered, and roughly what category it fell into. At the end of the week, read the list. The list is your decision authority plan. Build the thresholds next week. By week three, the bottleneck starts to dissolve.

The CEO Intensive includes a full decision-authority mapping session, with the thresholds worked out for your specific business, plus the weekly review template. Four hours, one-on-one, and most owners leave with a decision structure that holds for the next two years.

Next Week

On Tuesday, we look at the ninety-day clarity reset for agency owners. How to step fully out of the week for two hours every quarter and come back with a different plan than the one you walked in with.