Delegation: How to Hand Over Work So It Actually Holds

How to Stop Being the Bottleneck Your Team Waits On

By Andrew Lee Ward 2 min read Updated 27 Jun 2026

You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.

How to Stop Being the Bottleneck Your Team Waits On

If your team cannot predict your expectations and act without you, you are not leading a system — you are managing tasks, one interruption at a time. That is the bottleneck pattern, and it is the single most common ceiling growing managers and founders hit.

It rarely comes from a lack of effort. It comes from concentration: too many decisions, and too much context, sitting with one person.

The test

The bottleneck test is simple: you are the bottleneck if work stalls when you step away. The tells are familiar: decisions queue up waiting for your sign-off, people ask permission instead of acting from their remit, and you are the only one who holds the context that matters. Everyone can be busy and the work can still be entirely dependent on you.

Three things that unblock you

Unblocking yourself comes down to three structural moves: make expectations predictable, push decision rights down, and invite intent rather than permission. None of them is about working harder; each removes a reason the team has to route through you.

  1. Make your expectations predictable. People wait for you because they can't reliably guess what "good" looks like. A known, shared standard lets them act with confidence instead of checking in.
  2. Push decision rights down — with guardrails. Decide which decisions genuinely need you and which don't, then hand the rest down with clear boundaries. "You can decide anything under £X and inside this scope" frees both of you. A useful sort is the one Amazon's Jeff Bezos made famous in his shareholder letters: reversible "two-way door" decisions should be delegated fast, and only the rare, hard-to-reverse "one-way doors" held back for you.
  3. Invite intent, not permission. Shift the team from "What should I do?" to "I intend to do X unless you object." That one change moves the default from waiting to acting. The phrasing comes from L. David Marquet, the submarine captain whose "I intend to…" practice turned a crew of order-followers into one that acted from its own authority.1

It's a control problem, not a personality one

Being the bottleneck is usually framed as a failure to "let go." More often it is a missing structure: no shared standard, no clear decision rights, no agreed check-ins. Fix the structure and letting go becomes easy, because the work no longer needs you to hold it together.

That structure is exactly what delegating outcomes rather than tasks builds, and what The Control Standard develops into a full practice for leading work that runs without you in the room.


  1. L. David Marquet, "Turn Your Followers into Leaders," Harvard Business Review (2013); see also Turn the Ship Around! (2012).

Frequently asked

How do I know if I'm the bottleneck?
A reliable test: does work stall when you're away for a few days? If decisions pile up waiting for you, if people ask permission rather than acting from their remit, and if you're the only one who holds key context, you're the bottleneck — even if everyone is busy.
What's the fastest way to stop being the bottleneck?
Push the most common decisions down with clear guardrails, so people know what they're allowed to decide without you. Pair that with predictable expectations — a known standard for 'good' — so they can act with confidence rather than waiting to be told.
Why do founders and managers become bottlenecks in the first place?
Rarely from ego — usually from concentration. In the early days one person genuinely holds the context, the standard and the relationships, so routing everything through them is efficient. The habit outlives its usefulness: the team grows but the decisions never get handed down, and the founder becomes the ceiling on capacity.
Isn't it faster to just make the decision myself?
Faster once, slower forever. Every decision you keep trains the team to wait for the next one, so the queue at your desk grows. Handing the decision down with a guardrail costs more the first time and then pays back every time that decision recurs without you.
What decisions should I keep versus push down?
Keep the few that are hard to reverse, cross-cutting, or genuinely need your context — the rest should go down. A simple rule: if a decision is cheap to undo and inside someone's remit, they should be making it. Reserve your attention for the one-way doors.
How is 'invite intent, not permission' different from normal delegation?
It flips the default. Instead of 'What should I do?' (which waits for you), people say 'I intend to do X unless you object' (which moves unless you stop it). The work proceeds by default, you stay informed, and your silence becomes a yes rather than a bottleneck.

Keep reading

Guide

How to Delegate Outcomes, Not Just Tasks

To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.

Term

Decision Rights

Decision rights define who gets to make which decisions, and at what level, without needing sign-off from above. Setting them clearly is how a team stops routing every choice through one person: cheap, reversible decisions are pushed down with guardrails, while the rare, hard-to-reverse ones are deliberately kept for a more senior call.

Term

Bus Factor

The bus factor is the number of people who would have to be lost — "hit by a bus" — before a project stalls because critical knowledge or access went with them. A bus factor of one means a single person is a single point of failure. Raising it is a core goal of good ownership and delegation.

Topic

Delegation: How to Hand Over Work So It Actually Holds

Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.

Term

Routing vs Leading

Routing vs leading is the distinction between processing your team's work one item at a time — answering questions, making small decisions, unblocking people — and acting on the system that produces that work: its standards, decision rights, and handoffs. Routing feels productive; only leading compounds.

Guide

Why Is My Team Busy But Still Missing Deadlines?

Your team misses deadlines while staying busy because activity is not control. The work slips in the gaps between decisions, dependencies and handoffs — places effort never reaches. Everyone is occupied, but uncertainty is not shrinking, so the date moves a day at a time until the slip surfaces as a surprise.