The Bottleneck-to-Bandwidth Blueprint

Your team is capable. Your handoffs are the problem.

You've tried delegating and the work still snaps back to you. The Bottleneck-to-Bandwidth Blueprint™ shows you what's actually breaking: the handoff itself, in five specific places. Part of the Upstream Leadership™️ practice. For founder-led service teams in the $2M to $6M range.

Karen Sergeant

Karen Sergeant is the creator of Upstream Leadership™ and a fractional and advisory COO for owner-led B2B service teams.


You already know you're the bottleneck. What you may not know is why the work keeps routing back to you no matter what you try. In 20 minutes I'll show you the reason, and the five-part handoff that makes delegation finally hold.

Step 1: Name the Level of Work

Start by identifying what it is you want to move off your plate to someone else and then ask: at what level is this handoff? There are four:

  • Task. A scoped, specific action, or a series of them.
  • Project. A defined deliverable you expect someone to break down into tasks themselves.
  • Outcome. A result they own, with real latitude over how they get there.
  • Business goal. A whole piece of the business you hand off and trust someone to run.

The taxonomy matters because when delegation breaks, it breaks differently depending on which level you’re handing off. If you don’t name the level, you can’t diagnose why things keep coming back to you. And once you do, everything else in this framework gets sharper.


Step 2: Match to the Right Person

What gets especially tricky in small-but-scrappy teams is that everyone wears multiple hats, and can often be assigned work that spans almost all three or four of these levels. But they really only truly thrive in one or two. 

Now, here’s why this matters. Delegation fails when there’s a mismatch between:

  • the level of work you’re handing off
  • the person you’re handing it to

Most delegation advice assumes the level and the person are already aligned. They rarely are, and after a decade of this work, that mismatch is the single most common reason handoffs fail.

Want a deep dive on which kind of person thrives at which level is its own framework? Read The Four Worketypes.

Read More: The Four Worketypes →

Step 3: Set the Goalposts

Telling someone what to do without telling them what Done looks like is how you get work that misses the mark.

Delegation means "get to Done without me," so you need to define what Done actually looks like, and to surface the standards and constraints that matter.

It’ll take a few iterations for you to describe goal posts well. Most owners are carrying a web of standards they've never said out loud, and they don't see them until someone misses one. You’ll hand it off, see what comes back, you’ll notice the hidden standard you didn’t say out loud, you tighten the goalposts. It's an iterative process.

The same silent standards are behind most of your performance problems, and The Team Performance Fixer makes the case for getting them out in the open before you can hold anyone accountable.


Step 4: Set the Decision Boundaries

If you’re delegating a project or higher, the person you’re handing it to will be making decisions. (That’s the whole point: you’re asking them to get to Done without you.) So you need to clarify how much decision-latitude they have to handle all of the smaller decisions that will need to get made on the road to Done.

Otherwise, they have two bad options: either they stop and ask you about everything, or they guess.

When decision rights are left muddy, that’s when the “quick questions” crop up. It’s because your team doesn't know where the lines are, so they ask for approval at every turn.

So you need to answer the questions: what can they decide on their own, what should they loop you in on, and what’s still yours alone to decide?

That's your delegation contract, and once it exists alongside the goalposts, the work can finally run without you in the middle of it.


Step 5: Supervise Without Swooping

This is the habit-change step, and it's the hardest, because it lands on you.

You've named the level, matched the person, set the goalposts and the boundaries. Then you see something start to drift, and every instinct says jump in, rewrite it, fix it tonight. It feels efficient. But what it actually does is promote you back to bottleneck and teach the team that ownership is on loan, revocable the second you don't like what you see.

So when that happens, you fix the system: You adjust the goalposts, clarify the decision boundary, correct the level you handed off at, or coach the person on how to use what you gave them.

What you don't do is take the work back.

When you practice this consistently, the handoff will hold, instead of quietly routing everything back to you.


When it Starts Working

When the five steps are in place, the day changes shape:

  • Your week stops being run by quick questions.
  • Work stops boomeranging, and quality gets more predictable without you policing it.
  • Things move faster because nobody's waiting on you to weigh in.
  • And growth stops feeling like a threat, because you're no longer the hub every wheel turns on.

That's the move from bottleneck to bandwidth.


The Catch

Reading the five steps is the easy part.

Running them on your own business is where it gets hard, because the blind spots are yours, and you've stopped being able to see them: the silent standard you've been carrying, the mismatch you've rationalized for six months, the swoop you don't notice you're doing.

You can run every step and still get stuck, because you're inside the system you're trying to read, and you've adapted to your own bottlenecks so long that most of them have gone invisible.

Bottleneck to Bandwidth Blueprint

I've been solving this one problem long enough to spot them before most owners can name them. That's what a second set of eyes is for:

BOTTLENECK RX

Stop doing everyone else's job.
Start doing yours.

Bring me your bottleneck. I'll ask the questions that tell us whether this is a problem I can fix — and if it is, we'll get started. No pitch or pressure. Just a clean diagnosis.

Fire yourself as the Fixer-in-Chief.