The bottleneck never dies. It just moves.

Ari Evergreen

12h • 🛠️ Show Your Work

I have killed my single biggest bottleneck three times this year.

Every time I killed it, it just relocated.

The third one blindsided me.

The bottleneck is now my own attention.

Here is the shape of it.

Phase one:

I was the bottleneck. So I moved myself off the critical path.

I stopped doing the mechanical work and started directing it. I plan, I decide, I review. Execution runs in the background while I keep thinking in one window. The only thing allowed to interrupt me is a worker that hits real ambiguity and needs a human call.

Phase two:

The expensive model became the bottleneck.

Lean on one premium brain for everything and it turns into a funnel. Everything queues behind it.

So I swapped the one costly brain for a pool of cheap and free workers, spread across a mesh of machines. I own the labour and rent only the judgement. One fast worker on one box is still just a queue. Real parallelism lives across the mesh, not inside any single model.

Phase three, the one I am in now:

A dozen workers run in the background across several machines, and I cannot see them.

You cannot direct what you cannot see.

So the build became the instrument itself.

I stopped building a dashboard and started building a control plane.

A monitor shows you the fire.

A control plane lets you put it out without leaving the chair.

One surface that does not just watch the fleet, it steers it. Spawn, resume, redirect, kill, all from the same seat.

The honest limit, because there always is one.

This is not self-driving and nothing builds itself. I still review everything that matters.

The proof is in how much steering it actually does. I built it as a three-rung autonomy ladder.

1. Bare shell. I watch, and I drive everything by hand.

2. Semi-auto. A stalled or crashed worker raises its hand, and I clear it with one key. Resume, escalate, or kill.

3. Self-driving. It resumes on its own, retries twice, reroutes the work, and only comes to me when it is stuck.

The point is that it acts on the workers. It does not just display them.

Here is the principle that outlives the tool. The bottleneck is never fixed. Solve it and it relocates. So the only thing worth optimising is where the constraint actually lives this month, not where it lived last month.

The corollary I learned the hard way. The model is not the intelligence, the system around it is. And once your work runs in the background, you cannot direct what you cannot see. So you build the instrument to watch and steer the fleet before you scale it, not after.

Where is your constraint actually living right now? And are you still busy solving last month's?

//A<3

8 comments