She used to think the problem was her leadership.
Not in a dramatic way…just a low hum underneath everything. The kind of thought that shows up at 11:00 PM when you’re re-reading a Slack message someone sent asking if it was okay to send the proposal. She’d built a nine-person agency. She’d hired well. She’d trained carefully, sat in on calls, and written the onboarding docs herself. And her team still asked. Every time. About things that, on paper, were exactly what she’d hired them to handle.
There’s a different version of this, where a team makes the call without asking and gets it wrong. That’s a standards gap rather than an ownership gap, and it’s a separate conversation. This is about the other one: capable people who ask, every time, because nobody ever told them where their judgment stops and hers begins.
She started keeping a mental tally. Not of the decisions themselves because those blurred together. I’m referring to the feeling each one left behind. A small, private disappointment. Maybe she wasn’t the kind of leader who made people feel trusted. Maybe she talked a good game about ownership and then flinched every time someone tried to take it.
If you’ve asked yourself, “why does my team keep asking for approval” on things you were sure you’d delegated, the honest answer usually isn’t about trust at all. It’s rarely about confidence, hers or theirs. It’s about a gap nobody built a bridge across, and until someone names it, it looks exactly like a leadership failure from the inside.
Here’s what her actual week looked like:
For the people on the other end of those messages, every unanswered question carried its own quiet risk. Guess wrong and hear about it later, or ask and slow everyone down. Neither felt safe.
Every person on that list was capable and confident. What they had in common was that not one of them had ever been told, in a way specific enough to act on, which decisions were theirs.
She’d told her team “you own this” in a kickoff meeting once. That sentence doesn’t survive contact with a real deadline. It’s a feeling, not a boundary. Nobody can act on a feeling when the actual cost of guessing wrong is a client relationship or a missed deadline with her name on the contract.
So they did the rational thing…they asked.
And every time she answered instead of redirecting the question back to whoever should have owned it, she confirmed the unspoken rule: this still comes through me. She did not want to, but answering felt faster than the conversation required to hand the decision off, and faster always wins in the moment, even when it compounds every time.
It took a near miss to make her ask the question out loud. A scope change nobody had clear authority to approve went out anyway, and the client noticed before she did.
The turn came from a conversation with a colleague, another agency owner, who asked her something that sounded simple and wasn’t: for the last 10 decisions that came back to you, how many of them had a clear answer to “who owns this” before the question ever reached your inbox?
She counted. The honest answer was closer to zero than she expected.
No one, including her, had ever written down where judgment was supposed to live. Scope changes under a certain dollar threshold. Deliverable approval once a second team member had reviewed it. Client-facing language on anything routine. All of it had an obvious owner in her head. None of it had ever been said out loud in a form her team could act on without her.
The question underneath all of it was still. “Why does my team keep asking for approval when nothing about their competence has changed?” Growth doesn’t create that gap. It exposes one that was already there. The busier the agency got, the more decisions queued up at the one desk where all of them had always technically landed.
She didn’t hire anyone new. She didn’t buy a piece of software. She sat down and answered, in writing, one question from a short list of recurring decisions: whose call is this, and under what conditions does it need a second set of eyes?
She didn’t get every threshold right on the first try. Two of them moved within a month, once she saw where the real risk lived. That’s part of the process, not a sign it failed.
The list was short. Shorter than she expected. And once it existed, something she hadn’t predicted happened. Her project manager stopped messaging before scope conversations, because the threshold was written down and she was under it. Her strategist started shipping deliverables the same day they were finished instead of the day she got around to opening them. The question they used to bring to her now had an answer that didn’t require her.
None of this meant the asking stopped. Some decisions still come to her, the ones with real exposure attached. The point was never fewer questions. It was fewer wasted ones. Once ownership existed, the answer to why does my team keep asking for approval simply changed shape.
The Thursday that used to disappear into approvals started looking like a Thursday again.
She still makes plenty of decisions. The ones that are really hers. What stopped was the quiet tax on everything that never needed to be. And what she’d spent a year privately reading as a leadership shortcoming turned out to be the most ordinary kind of gap: a business that had grown past the point where one person’s judgment could be the only judgment in the room, with nobody having said so yet.
That was never an issue with confidence or trust. Trust wasn’t withheld. It just never had anywhere specific to land.
If you’ve been asking yourself why your team keeps asking for approvals, it might be worth an afternoon to see where the leak is in your own business through a straight look at what’s costing you and where.
It’s Handled™ | Operational architecture for founders who built the business, and are ready to stop being the infrastructure.
September 16, 2026
Be the first to comment