# I Learned This on an Assembly Line

_The first thing I ever built was an assembly line, and it taught me the thing I've spent twenty-five years relearning. You don't fix the bottleneck, you fix a bottleneck, and the next one steps up. AI didn't change that, it just moved the constraint faster, toward the one part no vendor sells you._

June 30, 2026

First published on LinkedIn: https://www.linkedin.com/pulse/i-learned-assembly-line-ben-feely-7eq6f/

![Ink-and-wash illustration of a worker at an assembly line who has just fixed his own station, wiping his hands, looking up to see the machine downstream jammed and overflowing with parts. The jammed station glows amber. Captioned "Chasing Bottlenecks."](/writing/assembly-line/cover.png)

The first real thing I ever built was an assembly line. I was still in college, running a small manufacturing operation, and one station had to lay down a precise amount of a granular material on every part that came through. So I built the dispenser for it out of eBay parts and scrap: a little rig that sensed when it had let out exactly enough, snapped shut, and reset for the next one.

I got that station humming and felt like a genius for about four seconds. Then I looked up and the line was already backing up somewhere else. The thing I'd just fixed wasn't the slow part anymore. Something downstream was, and it had been the whole time, hiding behind the station I'd been obsessing over.

That's the day I learned the thing I've spent twenty-five years relearning: **you don't fix the bottleneck. You fix *a* bottleneck, and the next one steps up to take its place.** It never feels finished, because it isn't. The chase is the work.

I'm doing the exact same thing right now, except the line is the way my teams build software, and what's speeding up the stations is AI. The part that surprised me isn't that AI is fast. **It's that it didn't change the game at all.** It just moved the bottleneck quicker, and it moved it somewhere I didn't expect.

Under all the noise, here's what's actually happening. AI doesn't lift a whole process at once. It cheapens one step at a time: code first, then the planning around it, then parts that were never about code. And every time one step gets cheap, the work doesn't shrink. It slides to the next step nobody's touched yet. **Relieve the tightest point and you expose the one behind it.** That's the oldest rule in operations, and AI just made it run faster.

The catch is *where* the bottleneck is sliding to. The model is rented, and it keeps getting better on someone else's schedule. The tools that drive it are rented too. What's left, the part no vendor sells you, is whether the agent can see your world and act in it: **the context only you have, and the autonomy only you can grant.** So the constraint keeps sliding toward us. That sounds like bad news.

![Ink-and-wash illustration: an engineer holds two amber keys labeled "Context" and "Autonomy" in front of a locked iron gate, while the rented model and tools sit faded and tagged "rented" behind him.](/writing/assembly-line/context-autonomy.png)

> It's the best news there is, because it's the part we can actually change.

That's the whole thing I care about, and it's why I think *enabling AI* and *empowering you* are the same sentence. Both are one move: **find the constraint and take it out, in the system and in the person.** And it never ends, because the constraint never stops moving.

So here's what I'm going to do in my articles here... I'll take the real processes we all live in (the way software actually ships, the way an incident gets communicated, the way a quarter gets planned) and walk the bottleneck as it slides. What AI just made cheap. What that exposed. And what it takes to open the next tight point. Every piece, the same picture: a *flow*, with its constraints, turning green one step at a time.

![Ink-and-wash infographic titled "Find the Bottleneck." The software lifecycle is laid out as stations from Requirements to Production, each staffed by robot and human figures showing how much AI does the step. Integration Tests is buried in an amber overflow and marked the bottleneck. Three panels below read "One Step at a Time," "The Bottleneck Moves," and "The Chase."](/writing/assembly-line/find-the-bottleneck.png)

I still remember the feeling on that assembly line: the four seconds of pride, then the next slow station lighting up. I used to think the goal was to make it stop. It wasn't. The goal was to get good at the chase, because the chase is the job. It always was.

So before I break down the first flow, do the thing the assembly line taught me. Pick a process you run, and find the one step everything else waits on. That's your bottleneck. I'm genuinely curious where you're all seeing it: **what's the step everything in your world is waiting on right now - AND - can AI help with that step?**