I once spent twenty minutes with a CEO’s calendar and found a million and a half dollars.
He ran a fifty-million-dollar professional services firm, and growth had stopped cold. The same number, quarter after quarter. The market was there. His team was experienced and, by every account, good at their jobs. Nothing in the business explained the plateau.
His calendar explained it. Back to back meetings, almost all of them about decisions he should never have had to make. A new client opportunity waiting on his approval. A pricing adjustment that wouldn’t move until he weighed in. A team structure question routed to him because nobody else had the authority to answer it.
He wasn’t out of market. He was out of processing capacity.
One of his executives later ran the numbers. Roughly thirty hours a week making decisions his leadership team could have made without him, sustained for two years. Call it three thousand hours. At his hourly value to the business, close to a million and a half dollars of his own time spent on work that never should have reached his desk.
That’s the Bottleneck Tax, and I’ve written at length about what it costs and why it’s a thinking problem rather than a time problem. This piece is about the other half. Not what it costs you. What you say on Monday to make it stop.
The gap is authority, not ability
Before we built anything, I asked him to state the problem plainly. He said: my team brings me every decision, big and small, constantly.
Then we asked why five times.
Why do they bring every decision to you? Because they don’t know which ones they’re allowed to make on their own.
Why don’t they know? Because we’ve never clarified decision rights.
Why hasn’t that been clarified? Because I assumed it was obvious what they should decide.
Why did you assume that? Because I’ve been making these calls so long I forgot anyone would need to be told the logic.
Why didn’t they ask? Because every time they brought me something, I answered it. Fast, efficient, helpful.
There it is. Not a capability gap. An authority gap, reinforced daily by his own habit of being useful. He had trained an entire team to escalate rather than decide, one helpful moment at a time, and then spent two years absorbing the consequences.
That distinction determines what you build. A capability gap needs training. An authority gap needs language.
Two kinds of decision clarity
There’s a version of this problem you solve with architecture. You inventory every recurring decision in the company, map each one to a role, attach dollar thresholds, and end up with a grid that tells anyone exactly who signs what. That’s a real and worthwhile build — we’ve laid out how to construct one here — and if you’re heading toward an exit or a leadership transition, you’ll eventually want it.
But it takes weeks, it requires organizational stability to be worth documenting, and most leaders reading this are drowning right now.
There’s a smaller version that works by Friday. Not a grid. A vocabulary — four levels of authority you attach to every task you hand off, out loud, in the moment. The grid answers who signs this? The vocabulary answers how much rope do you have on this one? You can adopt the second one this week without ever building the first.
The four levels
Level 1 — ACT. Your call. Make the decision, move forward, no need to report back. Office supplies. Standard client scheduling. Anything where the cost of a wrong answer is smaller than the cost of asking.
Level 2 — ACT AND INFORM. Make the decision and act on it, then tell me what you decided. Resolving a minor client complaint. Small budget shifts. You keep visibility without becoming a checkpoint.
Level 3 — RECOMMEND. Research the options, bring me your recommendation, we’ll decide together. Hiring a vendor. Changing a workflow. Note the wording — a recommendation, not a question. Level 3 is where judgment gets built, because your team has to arrive with a position.
Level 4 — ESCALATE. Bring me the data and the context. I’ll make this call. Strategic pivots. Large capital expenditures. Firing someone.
Four levels. That’s the whole framework. We spent three hours writing down which kinds of decisions lived at each one, and within two weeks, seventy percent of what used to land on his desk stopped arriving there.
His team hadn’t needed more training or more confidence. They needed permission, spelled out clearly enough that they couldn’t talk themselves out of using it. The capable team that could operate without him had been there the whole time, hidden behind the symptom he kept solving for them instead of with them.
Write the first draft badly, then hand it over
Here’s the part that makes it stick, and it’s not the writing.
Sketch your version of the four levels in thirty minutes. It will be wrong. Then take it to your team and ask them what’s missing.
They’ll tell you immediately, because they’ve been sitting on the answer. They know which decisions they’ve been holding because they weren’t sure. They know which ones they’ve quietly been making already without your blessing, hoping nobody noticed. They know the categories you forgot because you haven’t touched that work in six years.
Let their edits stand. The document you write alone is a policy your team has to comply with. The document you write together is one they’ll actually use, and the difference in adoption is not small.
The mistake that undoes all of it
The most common failure isn’t in the framework. It’s in what happens the next time you hand something off.
You delegate the task without delegating the decision. “Can you handle the vendor renewal?” is a task. It says nothing about whether they can sign, whether they should bring you options, or whether you want eyes on the final terms. So they guess. And guessing wrong is expensive, so they guess conservatively — which means they come ask you, which is precisely where you started.
Name the level every time. This is a Level 2 — make the call and let me know where you land. It feels stilted for about a week. Then it becomes the way your organization talks, and you’ll hear your managers using it with their own people, which is the actual goal.
The second failure is quieter. Someone makes a Level 1 or 2 decision you wouldn’t have made, and you reach in and reverse it. Understandable. Also fatal — the whole team watches, correctly concludes the levels are decorative, and goes back to escalating.
If the call was theirs and it was genuinely wrong, the conversation is about their reasoning, not the outcome. Walk me through how you thought about it. You’re calibrating judgment, not overturning a verdict. And if a category keeps producing bad outcomes, that’s real information — move it up a level on purpose, and say why.
What you’re actually building
I know a founder who built a company to fifty million dollars over fifteen years, almost entirely on the strength of his own strategic thinking. Extraordinary business by any measure. When he tried to step back into a chairman role, he couldn’t. Decisions piled up. The business drifted without his input. Every time, he got pulled back into daily operations.
Seven years later he was still running it day to day. Not because he wanted to. Because what he’d built was a very lucrative job, not a business.
That’s the stake, and it’s why this isn’t a time management trick. A company where every decision routes through one brain is an efficient bottleneck with a payroll attached. A company where people know which calls are theirs and are trusted to make them grows at the speed of its team rather than the speed of its founder. It survives your absence. Eventually it might not need you at all — which is either terrifying or the entire point, depending on what you built this for.
So look at your calendar from last week. How many of those decisions genuinely required your judgment, your context, your signature? And how many were on your desk simply because that’s where decisions go around here?
Pick one you’re handing back this week. Name the level out loud. Then let them have it.
If you want a second set of eyes on which decisions belong at which level in your business, book a complimentary strategy session and we will map your last month of escalations together.
The four levels and the source-finding method behind them are both laid out in Think First, along with the assessment that shows you exactly where your own thinking culture is breaking down. Find it at deliberatedirections.com/thinkfirst.
Not sure if you're the bottleneck? Find out in 2 minutes →
