Why Your Team Waits on You to Approve Everything

The queue with your name on it

Open your messages. Count the ones that are a decision your team is entirely qualified to make, sitting there with a question mark, waiting for a yes. Can I send this? Is this discount okay? Should we push the date? Every one of them is something you'll approve. You approve almost all of them. The approval rate is somewhere north of ninety percent and you've never once considered what that number means.

Meanwhile the work waits. Not for a long time — a day, two days. But it waits on every item, on every project, and the aggregate of all that waiting is the reason your business moves at the speed it does.

And you've said the sentence out loud, probably to your spouse: I wish they'd just decide. Which is where every founder gets it wrong, because you're reading a rational response to your incentives as a personality defect in people you chose.

Run the arithmetic they are running

Here's the mechanism. Put yourself in their seat and do the math they're doing.

Option one: decide. If it's right, nothing happens — nobody thanks you for a correct routine call. If it's wrong, it gets reversed, in a reasonable tone, and it's now a thing that happened. Small downside, no upside.

Option two: ask. Cost to them: zero. They send a message and move to something else. The waiting doesn't land on them at all — it lands on your calendar, on the client's timeline, on the project. They never see it. And the outcome is guaranteed correct, because you decided it.

That's not a close call. Asking dominates deciding on every axis, for every rational person, every time. Your team isn't low-agency. They're doing the arithmetic your business hands them and reaching the right answer.

Then add the reversals. You've reversed a call — maybe twice, maybe five times, always reasonably, always with context they genuinely didn't have. Each one was individually correct. Collectively they priced the downside of deciding, and nothing has ever priced the downside of asking. So the equilibrium isn't fragile. It's stable, and it took you years to build it without noticing.

People don't become low-agency by nature — they become low-agency by design, by being placed in an environment that requires hesitation, not action.

What the queue costs

The first cost is latency, and it's worse than it looks because it's not the two days — it's two days multiplied by every decision, on every project, compounding through a chain. Three sequential approvals in one workflow is a week of calendar for maybe eleven minutes of thought, and the client experiences the week.

The second cost is what it does to the judgment you say you're protecting. Judgment develops by making calls and seeing outcomes. A person who has never made a call has no way to develop it. So the longer the queue exists, the more true it becomes that only you can decide — and you'll point at that as vindication. It isn't evidence about them. It's the output of the design.

The third cost is that it turns your best people into your most frustrated. The hire you were most excited about is doing careful, unremarkable work. High performers don't degrade. Environments do. And the high performers are the ones who feel it soonest, which is why they leave first.

The fourth is what it does to you: you're spending your scarcest resource on the ninety percent of calls that were always going to be yes, which means you're too depleted for the ten percent that genuinely needed you. The queue doesn't protect quality. It buries the decisions where your judgment actually mattered under the ones where it never did.

Price the waiting, name the line

The fix is to change the arithmetic, and it has three parts.

Name the line as a number. Empowerment is not a speech. It isn't telling people you trust them and it isn't saying yes when they ask. It's the pre-negotiated, written, boring specificity of what they can decide without you. What's the refund they can issue on their own? The discount they can approve? The scope change they can accept? If those don't exist as numbers, they're guessing — and a guessing person escalates. Every time.

Then make waiting cost something. Right now the wait is free to them and invisible. Make it visible: an item blocked on approval that's been sitting two days should show up somewhere both of you can see. You're not adding pressure — you're putting the second half of the equation in front of the person doing the math, because they've genuinely never seen it.

Then survive the reps. This is where delegation actually dies — not at the handoff, at the first decision you disagree with. If a call inside their authority produces an outcome you don't love, fix the context or move the line, deliberately and out loud. Never quietly take the decision back. Letting go is one of the most advanced skills a founder can develop, and this is the rep where you develop it.

The pillar, and what we would honestly say

The pain is in Execution — your delivery moves at the speed of your inbox. The mechanism is Enablement: enablement isn't about trusting people first, it's about trusting your systems enough that people can succeed inside them.

And notice the third force, because it's the one that cancels the other two. You can give someone real authority and real knowledge and they'll still stall if the environment makes acting harder than asking. If the information they need is in your inbox, they need you. If the tool requires a click only you have, they need you. Agency isn't a personality trait. It's a function of friction.

Honestly: if you can write your authority line this afternoon, do it. That's free and it's most of the win. What we see more often is that the approval queue is one visible edge of a business where the standard was never externalized anywhere — which means the authority line can't be written yet, because you'd be authorizing people to guess at a target that only exists in your head.

The OPERATE Report is a $1,997 diagnostic across all seven pillars, for the founder who can see the queue and can't see why it refills. The highest form of leadership isn't doing everything yourself. It's creating the conditions that let other people do their best work.