My team won't make decisions without me. How do I fix that?

If your team won't make decisions without you, the problem is rarely the team. It usually means the decision was never fully handed over. The criteria live in your head, the limits were never written down, and at some point a call they made got reversed. So they learned the safe move is to ask. The fix is to give each recurring decision an owner, a written standard and a clear limit, then review results afterwards instead of approving everything in advance.

Why does my team keep asking me before they decide?

Most teams ask for one of four reasons.

1. They don't know what good looks like. You know which customer gets an exception and which one doesn't. They don't, because nobody wrote it down.
2. They don't know where their authority ends. Can they refund $50? $500? Can they move a deadline? If the line is unclear, asking is the only safe option.
3. They've been overruled before. One reversed decision teaches a team more than ten speeches about ownership.
4. Being wrong costs them more than waiting. If a mistake gets a lecture and a delay gets nothing, waiting wins every time.

None of these are character problems. They're design problems. And design problems can be fixed without hiring a new team.

Is it my fault the team won't decide?

Often, partly. That's not a judgment. It's just where the leverage is.

I've said this about founders and AI, and it applies to people too: "you're doing yourself a disservice and you're becoming the bottleneck to your success. You are in the way." When every exception routes back to you, you're not only busy. You're the ceiling on how fast the business can move.

The good news is that if you're part of the cause, you're also the fastest part of the fix. You don't need your team to change first. You need to change what you hand them.

For a wider look at this pattern, read My business can't run without me. Where do I start?.

How do I get my team to make decisions on their own?

Start with one decision, not all of them.

1. List the questions that come back to you. For one week, write down every time someone asks you to decide something. Note the topic and how long they waited.
2. Pick the most repeated one. Not the most important. The most repeated. That's where you'll get time back fastest.
3. Write the standard in plain words. What does a good decision look like here? What do you actually check when you decide? Three to five lines is enough.
4. Set the limit. Name the boundary in numbers or examples. "Refunds up to $100, yes. Above that, tell me after." Clear limits make ownership feel safe.
5. Name one owner. Not "the team". One person who owns this decision and is accountable for it.
6. Agree how you'll review. Weekly, look at the decisions that were made, not the ones that are pending. Coach on the pattern, not the single call.
7. Don't reverse a decision inside the limit. If you disagree with a call that was within the standard, change the standard for next time. Don't undo the decision. This is the step most owners skip, and it's the one that matters most.

Then repeat with the next decision.

What decisions should I keep?

Keep the decisions that shape direction or carry real risk. Vision, pricing, key hires, large commitments, anything that would be expensive to reverse.

Hand over the decisions that repeat and follow a pattern. Scheduling changes, small refunds, routine customer exceptions, which task comes first this week. If you could explain how you decide in a few sentences, someone else can make that call.

A useful test: if this decision comes up more than once a week and a wrong call is cheap to fix, it shouldn't need you.

Can AI help my team make decisions without me?

Yes, but only after the standard exists.

AI can hold the written criteria, draft the decision, check it against the limits and flag anything outside them. It can make sure the person deciding has the facts in one place instead of chasing you for context.

What it can't do is invent the standard you never wrote down. If the rules only live in your head, automation just moves the confusion faster.

The way I think about it, the same principle applies to people and agents: "you wanna think of AI and agents specifically like people in a way where you're able to give direction, access, permissions, guardrails, um, to where you're only needed when it's required."

Direction, access, permissions, guardrails. That's the same list a person needs to decide without you. If you want a starting point for where AI fits, see What should a small service business automate first with AI?.

What should I avoid?

• Handing over everything at once. You'll get anxious, step back in, and the team learns ownership was temporary.
• Delegating the task but keeping the decision. "You handle it, but check with me first" isn't delegation.
• Vague limits. "Use your judgment" without a boundary feels like a trap.
• Reviewing before instead of after. Pre-approval keeps you in the loop on every call. Review afterwards keeps you on the pattern.
• Assuming it's always the founder. Sometimes the real block is a missing tool, a broken handoff or unclear information. The founder is not always the bottleneck walks through how to tell.

How do I know it's working?

Watch three simple signals over a month.

• Fewer questions. The number of "can I…?" messages for that decision drops week over week.
• Faster turnaround. The time between a request and a decision gets shorter, because nobody is waiting for you.
• Fewer reversals. Decisions made inside the standard stay made.

If questions drop but mistakes rise, the standard needs work, not the person. Tighten the criteria and keep going.

Where do I start this week?

Write down every decision that comes back to you for the next five working days. Pick the one that showed up most. Write its standard, set its limit, name its owner, and agree a weekly review.

If you'd like help seeing which decisions are holding your business up, you can start your free Flow Audit. It's a short diagnosis of where work stops and waits for you, and sometimes the honest answer is a simpler change than you expected.

One person. One bottleneck. One decision at a time.