There's a version of "being needed" that feels good, and a version that quietly exhausts you. If your team brings you every small decision — which follow-up to send, how to handle a minor objection, whether it's fine to offer a slightly different discount — you might be experiencing the second one without realising it.
It's easy to read this as your team simply being cautious, or new, or wanting to keep you informed. Sometimes that's true. Often, it's something else entirely: you've unintentionally taught them that deciding without you carries more risk than asking first.
How This Habit Actually Gets Built
Nobody sets out to create a team that can't act without them. It happens gradually, through hundreds of small, well-intentioned moments. Someone asks a question, and you answer it — quickly, helpfully, because you can. Next time, instead of trying to work it out themselves, they ask again. Why wouldn't they? Asking is faster than figuring it out, and you've never once said no.
Every time you answer a question someone could have answered themselves, you're not just solving that one problem. You're reinforcing a pattern: bring it to him, he'll decide. That pattern compounds fast, and it's almost entirely invisible from the inside, because each individual instance feels like good, responsive management.
Why This Feels Good, Which Is Exactly the Problem
Being the person everyone comes to feels genuinely rewarding, especially early in a leadership role when you're still not sure you're adding value in other ways. Answering questions is a fast, visible way to feel useful. That's precisely why it's such an easy trap — it doesn't feel like a mistake while you're making it.
The uncomfortable truth is that a team constantly checking in with you isn't a sign of your importance. It's a sign of their dependence, and dependence is the opposite of what a strong team actually looks like.
How to Actually Fix It
- Answer questions with a question. Before giving your view, ask what they'd do. Often the answer they arrive at is exactly the one they were hoping you'd give them permission for anyway — the only thing missing was the confidence to say it out loud.
- Set a clear boundary for what actually needs you. Decisions with real financial, legal, or relationship risk genuinely might need your input. Most day-to-day judgment calls don't. Be explicit with your team about which is which, rather than leaving it to guesswork that defaults to "ask first, always."
- Let a decision go wrong sometimes. If every decision your team makes without you gets quietly corrected or second-guessed afterward, you've taught them that independent judgment isn't actually welcome, whatever you say out loud. Small, recoverable mistakes are the price of a team that can eventually make bigger calls without you.
- Notice your own relief when you're asked. If part of you enjoys being needed for small things, that's worth being honest with yourself about — because that quiet enjoyment is often what keeps the pattern alive longer than it should.
What This Actually Costs You
A team that can't move without you isn't just inefficient — it's a ceiling on how far you can grow, because your own capacity becomes the limit on everything your team can accomplish. The managers who build genuinely strong teams aren't the ones with the most answers. They're the ones who stopped being the only source of them.
Every promotion requires a new version of you. The version that used to feel valuable for having every answer now has to find value in a quieter, less visible way — in the questions your team learns to answer without you in the room.