You walk into the shop. A staff member stops you. Quick question. You answer it in twenty seconds. An hour later another team member catches you. Another quick question. You answer. By the end of the day you have handled forty micro-decisions, and most of them were things the team already knew how to handle.
They are not incompetent. They are not trying to pass the buck. They are doing what the structure has taught them to do: check with you first, because checking is safer than deciding.
That is not a people problem. That is a decision rights problem, and it is one of the most common friction points in a small business.
Why the asking happens
The team is making a completely rational calculation. If the rules are not written down, any decision they make is a gamble. The upside of a good call is small, the downside of a wrong call is worse, and the easy out, ask the owner, is right there. A team that asks about everything is not a weak team. It is a team operating under ambiguous rules, and asking is the lowest-risk move inside ambiguity.
A few underlying patterns tend to set this up.
The boundaries were never drawn. Nobody ever wrote down what the team is allowed to decide on their own, what they should bring you a recommendation on, and what is strictly yours. Without those lines, the default is "assume it's yours unless told otherwise."
You overrode a decision in the past. Maybe once, maybe three times, maybe years ago. Somebody made a call, you disagreed, you flipped it. They remember. They are not going to take that risk again without your blessing, even if the kind of call they are making today is well inside what you would want them to own.
There is no written standard for what a good call looks like. Judgment is risky without reference points. Ask a new hire to "use your judgment" on a pricing question, and they are being asked to invent the rubric in real time. Easier to just ask.
Asking you is faster than figuring it out. You can give an answer in thirty seconds. Thinking it through from scratch takes five minutes. Multiply across a week and asking is the better trade in any single moment, even though it is the worse trade over a year.
The culture rewards checking. When the owner responds warmly to being consulted, the team learns that consulting is the right move. When the owner gets mildly frustrated at an unconsulted decision, the team doubles down on asking. Over time, checking becomes the unspoken norm.
The cost, said plainly
Every unnecessary check is a small tax on the business. Individually tiny, collectively enormous.
Your week is shaped around being interrupted. You cannot plan deep work. You cannot think strategically. You are running the business by staying within twenty feet of a radio, and the radio is your team asking what to do.
Your team's judgment does not develop. Judgment is a muscle. It grows through reps. If they never get to make the call, they never get the reps. You end up with a team that is technically skilled but operationally dependent, which is the exact thing that caps how big your business can get.
Customers wait. Not for the work itself, but for a decision about the work, because the person with the customer cannot move without you, and you are in a meeting. Small delays pile up into a customer experience that feels slower than it should.
Good people get frustrated. The best hires want to take ownership. If ownership is not an option, they will either check out or move on. A team that is forced to ask about everything tends to bleed its best talent first.
And the whole thing caps at your capacity. The business cannot move faster than you can respond. That is the ceiling. It is lower than you think, and it is harder to raise than you think, because every time you hire someone new, they enter the same "ask first" system and add to the load.
How to draw the lines
You do not fix this by telling the team to make more decisions. They cannot, because the boundaries have not been defined. The work is on your side first.
Name three buckets. Decisions they own, decisions they recommend, decisions you own. Write them down. The RACI model, who is responsible, accountable, consulted, informed, is a more formal version of the same idea. Pick whichever one you will actually use.
Start with a small, real example. Instead of trying to map the whole business on day one, pick one category that keeps hitting your desk. Refunds under a certain size. Standard client questions. Ordinary scheduling adjustments. Write down clearly what the team owns in that category and what still comes to you. Put it somewhere visible.
Give them a standard, not just freedom. "Use your judgment" without a reference is not delegation, it is abandonment. Add a short description of what a good call looks like for that kind of decision. Length of the paragraph, not a manual. This is where the Andon-cord logic applies. Front-line people can act on their own, but the rules of when to act and when to signal are explicit.
Back their calls in public. This is the emotional part, and it matters more than the framework. If they make a call and a customer pushes back, do not flip their decision in front of the customer. Back the call, then coach privately later if you need to. One public reversal will undo six months of structural work.
Do not reward the ask. When they come to you with something that was clearly in the "decisions they own" bucket, do not just answer it. Redirect them, gently. "You can make that call. Here's how I'd think about it, but you own it." This feels slightly awkward at first. It is how the pattern actually changes.
What "good" sounds like inside the business
A team with real decision rights sounds different from a team without them.
Instead of "hey, quick question, do you want me to refund this?" you hear "heads up, I refunded that, the situation was X, let me know if you want me to do it differently next time."
Instead of "what do you think we should do about Y?" you hear "here is what I am going to do about Y unless you object."
Your job shifts from being the person who decides to being the person who notices when the decisions are off. You get to review patterns instead of transactions. That is a completely different kind of leadership load, and it is sustainable.
The team, meanwhile, gets sharper. Every decision they make is a rep. They develop instincts you used to have to supply. Over a year, the difference is dramatic. You are not just less interrupted. You are running a better business, because the judgment is distributed across five or eight people instead of sitting in one.
The Monday action
Pick one category of question that keeps hitting you. The most common one. Write a short description of what the team is now allowed to decide without you in that category, what the rule is, and when something should still come to you.
Share it. Not in a big meeting. Just send it. Be clear that this is the new default, not a suggestion.
For the next two weeks, when that category of question comes to you, redirect instead of answering. "You can make that call, here is the doc." Expect some initial awkwardness. People do not change their asking reflex in a day.
Then pick the next category. Then the next. In a quarter, a meaningful fraction of what used to be "hey, quick question" is happening on its own, and you have got the time back that those micro-decisions used to eat.
If you want an outside read on which decisions are most expensively sitting in your queue right now, a Flow Check is the simplest place to start. And if the broader pattern is the thing you are trying to solve, the bottleneck is probably you is a natural next read.