Multiplier, Not Bottleneck

At any moment, a senior person is doing one of two things to the people around them: making them more capable, or making them more dependent. The first is a multiplier, the same person makes the whole team better, and the team keeps getting better whether or not that person is in the room. The second is a bottleneck, a reducer, everything routes through them, nothing moves without them, and the team’s ceiling becomes one person’s capacity. The entire job of a leader, and the deepest habit to build in a future leader, is to keep choosing the first.

This is the creed underneath everything in this section. Spotting, equipping, and growing people are all ways of multiplying. Micromanaging, hoarding context, and being the gate on every decision are all ways of reducing. Here are the principles, plainly, because they’re worth living by, not just for a would-be CTO but for anyone senior enough that others depend on them.

The Principles#

1 · Find what depends on you.

Make the actual list. Which decisions wait for your approval? What knowledge only lives in your head? Which tasks does the team assume are yours? What access only you have? Every item is both a bottleneck and a single point of failure. You can't remove a dependency you haven't named.

2 · Remove yourself from the path.

For each dependency, do one of four things: delegate it to someone who can own it, document it so it's not trapped in your head, set a guardrail so others can decide without you, or automate it away. The goal is simple and testable: the work doesn't stall when you're on a plane.

3 · Open capabilities, don't hoard them.

Being the only person who can do X isn't job security, it's a liability you've created. Teach the thing, share the context, grant the access, write the playbook. This is about operational single points of failure, the keys only you hold, the system only you understand, not rare judgment: deep architectural taste or a hard-won domain call is real value that can't be photocopied on demand, and being its main holder for now is fine. The goal there isn't to pretend it away, it's to grow it in others over time.

4 · Push decisions down, don't be the gate.

Every decision that has to climb to you and back is latency you added and judgment you didn't grow in someone else. Set the guardrails, then let people decide inside them. Be the person who makes others able to decide well, not the approval everyone waits on.

5 · Multiply, don't reduce.

Before you act, ask one question: does this make the team more capable or more dependent on me? Doing the hard task yourself reduces; teaching someone to do it multiplies. Fixing the one bug reduces; fixing the pattern multiplies. Default to the move that raises the team, even when doing it yourself would be faster today.

6 · Your absence is the test.

The scoreboard for all of the above: what happens when you step away? If the team slows to a crawl, you were a bottleneck. If it runs fine, you built capability. Aim to be missed mostly for your judgment and direction, the things that genuinely need you, and only rarely for your throughput, on the hard problems where your hands really are the highest-leverage thing.

Delegating Is Not Dumping#

Removing yourself from the path has a failure mode of its own: handing work off and walking away. That’s not multiplying, it’s abandoning, and it burns both the person and the work. When you delegate, you still own the outcome. Guardrails are checkpoints, not absence: you set the outcome and the boundaries, review at the seams (the plan, the milestones, the result), and stay close enough to catch a problem before it lands on a customer. And you calibrate to the stakes, hand someone a reversible, low-blast-radius thing to grow on, not the irreversible or high-risk one in the middle of a crisis. Multiplying is deliberate investment with the safety net still in your hand, not fire-and-forget.

The One-Question Filter#

Most of this collapses into a single habit you can run in real time, dozens of times a day: “Am I multiplying or reducing right now?” Grabbing the keyboard to fix it yourself, reducing. Sitting with the person while they fix it, multiplying. Keeping the context in your head, reducing. Writing it down where anyone can find it, multiplying. Approving each request, reducing. Setting the rule that makes approvals unnecessary, multiplying. The faster version doesn’t matter is a trap: the reducing move is almost always faster today and more expensive every day after. The multiplier pays a little now and compounds forever.

Why It Matters More the Higher You Go#

An individual contributor can afford to be a mild bottleneck; the blast radius is small. A lead is a bottleneck for a team. A CTO who’s a bottleneck is a ceiling on the entire engineering organization, every decision, every capability, every bit of momentum capped at one person’s bandwidth. That’s why this is the make-or-break habit for a future leader: the higher you go, the more people your bottlenecks cost, and the more your multiplying compounds. The best leaders make themselves progressively less necessary for the day-to-day and more valuable for the direction. That’s not working yourself out of a job; it’s the only way the job scales.