Workflow

The bottleneck moved, and nobody updated the org chart

The Reticle team · June 18, 2026 · 2 min read

There's a loop every team building with AI agents now lives inside. An agent researches the problem. An agent writes the code. Then a person opens the app, clicks around, checks the network tab, reads the logs, and decides whether it actually works. Then the feedback goes back to the agent.

Three of those four steps got an order of magnitude faster in the last two years. One didn't.

The human became the slow step

When code took days to write, a few hours of manual verification was rounding error. Now the code arrives in minutes and the verification still takes hours, so the math has flipped: the person checking the work is the bottleneck. Not because they're slow, because they're doing by hand what the rest of the loop does at machine speed.

And it's not just slow, it's the worst kind of work. Re-running the same flows, eyeballing the same screens, trying to remember what "correct" looked like last time. It's the task most likely to get rushed, and rushing verification is exactly how a false green slips through.

You can't close a loop at machine speed if one quarter of it runs at human speed.

Faster agents make it worse, not better

The intuitive fix is "make the agent better." But a better agent ships more changes, more often, which means more to verify, not less. Improving the fast steps widens the gap at the slow one. The bottleneck doesn't move on its own; it just gets more expensive to ignore.

The only way to actually close the loop is to make verification run at the same speed as everything else, automatic, on every change, with a verdict the agent can read and act on without a human in the path.

What that looks like

The agent makes a change. Verification runs against the real app, real interactions, real network calls, real state, and returns a verdict pointed at the exact line if something broke. The agent fixes it and re-verifies. The human reviews the result, not every intermediate step.

That's not removing people from the loop. It's removing people from the part of the loop that never needed a person, and giving them back the time to do the part that does.

The org chart still says a human signs off on quality. That part's fine. The part that needs updating is the assumption that signing off means doing the checking by hand.