The Manager Who Was Always Busy—and Always Behind

By Ty Sutherland

There’s a particular kind of exhausted manager who responds to every email within minutes, attends every meeting, reviews every piece of work before it goes out, and still can’t figure out why their team keeps missing deadlines. The work piles up on their desk. People wait. Projects stall. And somehow the manager ends up staying late to fix things that should have been finished days ago.

If this sounds familiar, there’s a good chance you’re the bottleneck on your own team.

This isn’t a character flaw. Most managers become bottlenecks for understandable reasons—they were promoted because they were good at the work, they care about quality, and they’ve learned through experience that things go wrong when no one’s watching. But what protected quality as an individual contributor actively harms performance as a manager. When everything has to go through you, your capacity becomes your team’s ceiling.

The good news is this is fixable. Here’s how to diagnose the problem and systematically get out of your own team’s way.

How to Tell If You’re the Bottleneck

Before you can fix the problem, you need to see it clearly. Bottleneck managers often don’t realize what’s happening because they’re too busy to step back and look at the pattern.

Ask yourself these questions honestly:

• Do team members regularly have to wait for your input, approval, or feedback before they can move forward?
• Are there tasks only you can do, not because they require special skill, but because no one else has been trained or given authority to do them?
• Do people ask you questions that you’ve answered before—and that you’ve never written down or formalized anywhere?
• When you’re out of the office, does work slow down or stop?
• Do you find yourself redoing work your team has already submitted?

If you answered yes to two or more of these, you have a bottleneck problem. The question now is where it’s coming from.

Why Managers Become Bottlenecks

Understanding the root cause matters because the fix is different depending on what’s driving the behavior.

You haven’t delegated because you don’t trust the output

This is the most common cause. You’ve seen your team produce work that wasn’t quite right, and you’ve learned that reviewing and editing everything is faster than dealing with the fallout of something going out wrong. The problem is this creates a self-fulfilling cycle: your team never gets the practice and feedback they need to improve, so they keep producing work that needs heavy editing, so you keep editing everything.

You haven’t built the systems that would make delegation safe

Delegation doesn’t work if your team doesn’t have clear standards, examples of what good looks like, or enough context to make good decisions. Many managers skip the infrastructure work—the documented processes, the decision frameworks, the clear briefs—and then wonder why things go sideways when they hand work off. Delegation without infrastructure is just hoping for the best.

Your approval is required for things it doesn’t need to be required for

Some managers are bottlenecks not because they’re doing the work, but because they’ve inserted themselves as a required checkpoint at too many stages. Every expense needs sign-off. Every email to a stakeholder needs review. Every minor scope change needs a conversation. This might feel like oversight, but it’s actually a tax on your team’s speed—and it signals that you don’t trust them to use their judgment.

You’re holding onto work that energizes you

This one’s harder to admit. Sometimes managers hold onto tasks—the interesting client relationship, the creative brief, the presentation design—not because they have to, but because they enjoy them. The role of manager can feel abstract and unglamorous compared to the concrete satisfaction of making something. If you’re doing individual contributor work because you want to, you’re taking that work away from someone on your team who could be growing into it.

The Fix: A Practical Four-Part Approach

1. Audit where your time actually goes

For one week, track every task you do and every decision you make. Don’t rely on memory—write it down in real time. At the end of the week, sort your tasks into three buckets:

• Only I can do this — decisions or work that genuinely require your authority, relationships, or expertise
• Someone on my team could do this with the right support — tasks that could be delegated if you invested time in training or documentation
• Someone on my team should already be doing this — work that has drifted back to you because it’s easier, faster, or more comfortable to do it yourself

Most managers find that the first bucket is smaller than they expected, and the third bucket is much larger. That third bucket is your delegation backlog.

2. Build the infrastructure for delegation

Before you hand work off, make sure the person receiving it has what they need to succeed. This means being specific about three things:

• The standard: What does a good outcome look like? Be concrete. If possible, show an example of work that hit the mark.
• The authority: What decisions can they make without checking with you? Where do they need to loop you in? Spell this out explicitly—people default to asking permission when boundaries aren’t clear.
• The feedback loop: How will you know if something is going off track before it becomes a problem? Set a lightweight check-in cadence, not because you don’t trust them, but because catching issues early is faster than fixing them late.

If you’ve been the only person who knows how something gets done, write down the process before you hand it off. Even a rough one-page summary is better than nothing. This also has the benefit of forcing you to examine whether the process is actually as complex as you thought—often it isn’t.

3. Shrink your approval footprint

Go through the list of things that require your sign-off and ask a simple question: what’s the worst realistic outcome if this decision goes wrong without my involvement? If the answer is “we send an email with a slightly different tone than I’d have chosen” or “we spend $200 on something that wasn’t ideal,” those decisions don’t need to go through you.

Create a clear decision authority matrix with your team. It doesn’t have to be complicated. Something like:

• Team member decides independently: anything within their domain under a certain cost or risk threshold
• Team member decides and informs me afterward: mid-range decisions that I should be aware of but don’t need to approve
• We decide together: decisions with significant strategic, financial, or reputational stakes
• I decide: things that only I have the authority or context to decide

Once you make this explicit, most teams are surprised by how much they’re capable of handling independently—and managers are surprised by how much mental bandwidth they get back.

4. Change how you give feedback

One of the most subtle ways managers become bottlenecks is through their feedback style. If your feedback is consistently “here’s what’s wrong, I’ll fix it,” your team learns to bring you rough work and wait for you to do the final pass. If your feedback is “here’s what’s working, here’s what needs more thought, here you go,” your team learns to do a better first pass and develops their own judgment over time.

This shift is harder than it sounds, especially when you’re pressed for time and it feels faster to just fix it yourself. But every time you fix something instead of coaching someone through fixing it, you’ve made a short-term time gain and a long-term time loss. The team member didn’t learn anything. They’ll bring you the same issue again next week.

Try asking questions before giving answers: “What do you think needs to change here?” “What were you trying to achieve with this section?” “What would you do differently if you had another hour?” This takes more time in the moment, but it accelerates their development and reduces your dependency over time.

What to Do When You’re Afraid to Let Go

Most bottleneck behavior is, at its core, fear-based. Fear that quality will drop. Fear that something will go wrong and you’ll be held responsible. Fear that if you’re not doing the work, you don’t add value anymore.

These fears are understandable, but they need to be examined rather than indulged.

On quality: quality might dip temporarily as your team takes on new responsibilities. This is normal and expected. The question isn’t whether the first few attempts will be perfect—they won’t be. The question is whether you have a feedback system in place to help the team improve. If you do, quality will climb over time and exceed what you could produce alone.

On accountability: being responsible for outcomes doesn’t mean doing all the work yourself. It means building the conditions—the standards, the training, the oversight—that make good outcomes likely. A manager who does everything alone is not more accountable; they’re more fragile, because everything depends on them personally never dropping the ball.

On adding value: your value as a manager isn’t in the tasks you complete—it’s in the capacity you build, the obstacles you remove, and the performance you enable. A team that runs well when you’re not watching is a far greater achievement than a pile of work you did yourself.

A Note on Urgency

Some managers justify their bottleneck behavior by pointing to the pace of the work. “I’d love to delegate more, but things move too fast to train someone right now.” This reasoning almost always reverses the actual situation. The reason things feel so urgent and chaotic is often because everything is going through one person. Slowing down to build delegation capacity is what creates the breathing room that currently feels impossible.

You don’t have to fix everything at once. Pick one task from your delegation backlog this week. Write down the standard, clarify the authority, and hand it off. See what happens. Adjust. Then do it again next week. Over time, this compounds.

The Team on the Other Side of This

It’s easy to think of bottleneck behavior as a manager problem. But it’s also a team problem, and a morale problem. When people can’t move forward without your input, they feel stalled. When their work is constantly being revised, they stop investing in the first draft. When they’re never trusted with real responsibility, they stop developing and start looking for roles where they will be.

The managers people remember as great are almost never the ones who did the most themselves. They’re the ones who created the conditions for their teams to do their best work—who made people feel capable, trusted, and stretched in the right ways.

Getting out of your team’s way isn’t about stepping back from your role. It’s about stepping into the most important part of it.