You have a team. Good people. Smart, capable, paid to use their judgment.
And yet every decision still ends up on your desk. The price quote. The refund. The schedule change. The vendor question. A thing that should take ninety seconds sits in your inbox for three days because you were the one piece of the puzzle everybody was waiting on.
You tell yourself the team is being cautious. Respectful, even. But if you are honest about it, what you are actually seeing is a business that can only move as fast as you can answer Slack messages.
This is a decision rights problem. It is almost never a people problem.
Why decisions end up with you
A few patterns tend to show up together. Most small businesses I work with have at least three of these running at the same time.
The boundaries were never drawn. Nobody wrote down what the team is allowed to decide on their own. So to be safe, they ask about everything. That is rational behavior inside an unclear system.
You overruled them once. Somebody made a call, you didn't love it, and you changed it after the fact. They got the message. Now they check first. Every time.
There is no written standard for what a good decision looks like. If "use your judgment" is the whole instruction, judgment feels like a trap. They come to you for the criteria.
You are faster than the process. Asking you takes two minutes. Figuring it out from scratch takes twenty. The shortest path goes through you, so the current of the business runs through you.
Being the one who decides feels good. This one is quiet but real. If every question routing through you is the thing that makes you feel essential, you will keep that system in place without meaning to.
What it actually costs
This is not just an efficiency problem. It is a capacity ceiling disguised as a management style.
Customers wait. Not because your team is slow, but because your team is waiting for you, and you are in a meeting. Time-sensitive calls don't get made, or get made too late to matter. Your best people, the ones who have the judgment you actually wanted when you hired them, stop offering it. Smart people hate not being trusted. They either get quieter or they leave.
And nobody is learning to lead. You cannot hand off a business, grow a business, or take two weeks off in a business where the decision-making muscle has only ever been yours.
This is the Deming observation at work. Most problems in an organization are not people failures. They are system failures. When every decision runs through one person, that is not a personality trait. That is a missing system.
The fix is a framework, not a pep talk
Telling your team "just make the call" does nothing. They do not have the information they need to make the call. You have to give them a framework.
Start with three buckets.
Decisions they own. They decide and act. They do not need to tell you before or after unless something goes sideways. Refunds under a set amount. Scheduling changes inside agreed-upon rules. Standard quotes for standard work.
Decisions they recommend. They do the thinking, bring you a proposal, and you say go or no-go. This is where real judgment gets developed. Not "what should we do," but "here's what I think we should do, and here's why."
Decisions you own. Big hires. Major investments. Pricing shifts. Anything strategic or anything that affects the next few years.
Write the three buckets down. Put them somewhere visible. This alone cuts most of the "hey, quick question" traffic out of your week.
If you want a cleaner version of this, the RACI model, who is responsible, accountable, consulted, informed, does the same work with a little more precision. It is not corporate jargon when it is applied to a five-person team. It is just clarity.
How to make it stick
The framework only works if you hold up your side.
Start with low-stakes decisions. Let people own things where a wrong answer is annoying but not catastrophic. Confidence is built in small wins, not big bets.
Back them in public. If they make a decision and a client pushes back, do not throw them under the bus. Support the call in front of the client. Coach them privately afterward if it needed a correction. If you reverse them publicly even once, the framework is dead.
Ask about reasoning, not outcomes. When you do check in, ask how they thought about it, not just what they chose. Judgment is a muscle. It grows with reps.
Let them fail small. Not every call will be the one you would have made. Some of them will be better, actually, because they are closer to the ground than you are. Some will be worse. Protect them from catastrophic mistakes, not from regular ones.
What it looks like when it works
A Santa Cruz business with decision rights in place feels different.
Front-line staff handle the front-line stuff inside the rules you wrote. They escalate when something is genuinely outside the rules, not every time a customer raises an eyebrow.
Your managers make operational calls on schedules, processes, and resources. They keep you informed. They do not wait for approval for things you have already told them they own.
You get to spend your week on the three or four decisions that actually shape the business. Not the fifty that shape the day.
That is what scaling looks like from the inside. It is not more hours. It is fewer decisions landing on your desk, because the system is catching them before they get to you.
Start with one category
You do not have to redesign the whole decision tree this month. Pick one category of decision that keeps hitting your desk. Refunds, maybe. Or simple scheduling conflicts. Or standard client quotes.
Write down who owns it, what the criteria are, and when it should come to you anyway. Share it with the team. Give it four weeks to settle. Then pick the next category.
That is how the bottleneck breaks. One clear boundary at a time.
If the current is running through you and you want an outside eye on where it should be going instead, a Flow Check maps the stuck points and lays out a 90-day path. And if this feels like the deeper delegation problem, the bottleneck is probably you is a good next read.