The more decisions you make for your team, the fewer decisions your team learns to make without you.
It starts innocently enough. Someone asks you to check a report. Someone else needs approval on a design. A third person wants to know how to handle a client.
You answer because it’s quicker than explaining. You review because you want to get it right. You step in because the deadline is close.
Soon, work that should move on its own starts waiting for you.
You’re helping everyone get the work done. You’re also making yourself a requirement for getting it done.
This happens to managers who care about the work. They want to avoid mistakes, keep projects moving, and make sure the team gets things right. Each decision to step in seems reasonable. But over time, the team learns to bring more decisions to you instead of making them.
Eventually, your calendar becomes part of every project’s timeline.
Signs you’ve become the bottleneck
Your day might look like any other busy manager’s day. Everything seems to be moving because you’re keeping an eye on it. Look more closely, though, and you may notice that work moves only when you’re available.
Work arrives finished except for the last step
A report is complete but needs your sign-off. A design is ready but needs your eyes on it. The team did the work, and what’s left is the one step only you’re allowed to take. So the work never really gets “DONE.”
Decisions get scheduled instead of made
Someone has a question that could be settled in five minutes. Instead, it goes on the agenda for Thursday’s meeting, because that’s when you’ll be in the room. The decision isn’t hard. It just has to wait for you.
Your calendar becomes the project timeline
Ask when a project will be done, and the answer depends on when you’ll have time to review it.
Deadlines stop being about how long the work takes and start being about when you’re free.
People stop arguing with you
This one is quieter than the others, but it’s the one doing the most damage. Early on, people question your decisions and suggest other ways to do things. Over time, they stop pushing back.
They bring you problems to solve instead of options to consider. Even when they have a reasonable answer, they look to you to make the call.
You might take this as a sign that the team trusts your judgment. But if every decision ends up with you, you’re carrying more than your share of the thinking.
Put together, these signs describe a team that can only move as fast as your calendar allows. And it gets harder to undo the longer it goes on. When fewer people make decisions, fewer people get practice making them, so the team gets less capable over time instead of more.
Why everything come on your plate
Nobody sets out to become the bottleneck. It builds up through small choices that make sense at the time.
Usually, three things end up happening.
You hold the decisions
When you first step into the role, signing off on things comes with the job description. You want to understand how the team works and make sure the work meets the right standard.
But the habit can outlast the reason.
Some decisions really do need your approval. Many others end up on your desk because that’s where they’ve always gone.
And when you delay a decision that affects someone else’s work, you’re not just delaying your own task. You’re holding up theirs, too.
One unanswered question can leave several people waiting.
You hold the context
A lot of what the team needs to know lives only in your head.
You know why a particular client gets special treatment. You know what a good first draft looks like. You know which trade-offs are acceptable when a deadline gets tight.
But nobody else knows all of that.
So people ask you. When you’re in meetings or on leave, the questions wait, and so does the work.
You can spot this when two people give different answers to the same question. They may not be careless. They may simply be working with different assumptions.
You hold the work
You probably became a manager because you were good at doing the work yourself. That skill hasn’t disappeared, and stepping in can feel like the quickest way to get something done.
So you rewrite the email, fix the slide, or adjust the report yourself.
The result might be better this time. But if you keep finishing other people’s work, they have less reason to trust their own judgment next time.
Eventually, they may stop treating their work as something they’re responsible for completing. They start treating it as a draft for you to finish.
How it keeps getting worse
These three feed each other.
You hold the decisions, so the team waits. The team waits, so more work piles up with you, leaving you less time to explain what you know or help people develop their judgment.
Hence, everything keeps coming back to you.
So the next question comes to you, too.
It’s tempting to blame the team for not taking initiative. But consider what happens when someone makes a decision without you.
If it goes wrong, they may be blamed for a call they were never encouraged to make. If they wait for your approval, at least the responsibility stays with you.
Given that choice, waiting can seem like the safer option.
The team is responding to the way work gets done. You may not have intended to create that system, but you have a part in maintaining it. And that means you can start changing it, too.
You can’t be the only person holding everything together
A good manager gets a little less necessary every month.
People need enough context to make good calls, enough authority to act, and enough responsibility to see the work through.
Download the Medium App
That means changing how work moves through the team, not just asking people to be more independent.
The team still needs you, but for fewer of the everyday calls, which frees your time for the work only you can do.
Each fix below covers one part of that.
Let people make more decisions
Start with the questions people bring you regularly.
Which can they decide on their own? Which should they decide and tell you about afterward? Which genuinely need your approval?
These recurring questions show you where decisions are getting held up and where people need clearer authority. Use them to define what people can decide, when they should keep you informed, and when they need your approval.
For example, a team member might be able to change a task’s order or resolve a routine client issue without asking you first. A change to the project scope or a commitment that affects the budget might still need your approval.
Make such boundaries clear so people do not have to guess. Start with decisions that are easy to reverse. If someone makes the wrong call, the cost is small, and they learn something for next time.
For decisions that still need your approval, set a reasonable response time. The team should not have to wait a week because you are trying to find the perfect answer.
Get what you know out of your head
Every question only you can answer creates a small queue. The way to clear it is to get the answer out of your head and into a place the team can find it.
You know what a good piece of work looks like, what matters most when priorities compete, how you want clients handled, and where you are willing to make trade-offs. Your team needs to understand these things too.
Write down what you expect, explain why it matters, and share examples of what good work looks like. Put this information somewhere people can refer to while doing the work.
For example, show the team what a finished report should include, explain how you want client requests handled, or describe how to choose between two competing deadlines.
The more of your thinking you make visible, the less people have to rely on assumptions about what you want. They can use that context to make decisions and move work forward with confidence.
Give people responsibility for outcomes
Assigning tasks is easy. Giving someone responsibility for getting something done takes more thought.
When you assign someone a task, their responsibility is usually limited to completing that piece of work. They can finish it and still leave you to figure out what happens next, deal with any problems, or coordinate the remaining work.
Ownership works differently.
Give someone a result to own, not just a list of tasks to finish.
For example, asking someone to prepare a project report gives them a task to complete. Making them responsible for delivering the report to the client by Friday gives them a result to work towards. They have to gather the information, follow up with people, deal with delays, and make sure the report reaches the client on time.
This changes how people approach their work. They start thinking about what needs to happen next, what could get in the way, and what they can do to keep things moving.
If they come to you with a problem, ask what they think should happen next. Give them room to work through it and come back with a proposed solution.
When someone needs help, help them. But do not automatically take the work back just because you could do it faster.
If you keep taking over whenever things get difficult, people will learn to hand problems back to you instead of taking responsibility for resolving them.
Stop checking every step
Regular updates and constant reviews can make you feel in control. But they can also teach people that nothing is finished until you say so.
Before work begins, agree on what a good result looks like. Be clear about deadlines, quality, and any boundaries that matter. Then let people get on with it.
Review the work that genuinely needs your attention. A client contract might need your approval. An internal update probably doesn’t.
You cannot give every piece of work the same level of attention. So stop trying.
People will sometimes do things differently from the way you would. Let them. If the result meets the agreed requirements, it doesn’t need to be redone just because you would have approached it another way.
If the result falls short, talk about what went wrong and what to change next time. That is usually more useful than redoing the work yourself.
The team shouldn’t have to ask you where things stand. They should be able to see the work for themselves.
ProofHub gives teams a shared place to keep tasks, deadlines, discussions, and project updates. That makes it easier for people to find the information they need and see what’s moving, what’s waiting, and what needs attention.
A shared workspace won’t make every decision for the team. But it can make the work and its context easier to find, so fewer routine questions have to come back to you.
Try this with one project
For the next week, pay attention to what waits for you.
Write down the approvals, questions, reviews, and tasks you take back because doing them yourself feels faster.
Look at each one and ask: Does this genuinely need my judgment, or has it ended up with me out of habit?
If it needs your judgment, make the decision promptly.
If someone needs context, give them the information and make it available for next time.
If someone needs authority, agree on what they can decide independently, what they should tell you about afterward, and what still needs your approval.
Then leave the work with them.
You don’t need to change how the whole team operates at once. Start with one decision that no longer needs to wait for you.
Notice what happens. Does the work move faster? Does the person make the next decision without asking? Does the same question come back because the answer still isn’t easy to find?
Use what you learn to make the next change.
Your team shouldn’t have to wait for you
The value of a manager is not limited to the work they personally complete. It also shows up in what other people can accomplish because of their guidance.
Good management should make people better at handling the work in front of them and preparing for the responsibilities ahead. As they gain experience, they should be able to take on more complicated work, make sound judgments, and handle situations they once needed your help with.
Your contribution as a manager shows up in that growth. The more capable your team becomes, the more it can accomplish, and the more room you create for everyone to do their best work.
The best managers leave their teams more capable than they found them.
Originally published at medium.com.
Top comments (0)