Skip to content

Blog

Agents finished the portal, then it waited in a queue

An agent-built portal was ready to ship and waited on a gateway, a firewall rule, a certificate and QA. A factory shortens the build, and only a self-service platform shortens the wait around it.

Written by

Organization and roles

Published: 19 October 2026 Updated: 1 min read

The software was done. Then it waited on a certificate.

Every release step ran through a queue

From our experience at a client: a portal we had built with agents was ready to ship. Release needed a gateway, a firewall rule and a certificate from the team that runs their cloud, a different supplier. After that, QA had to sign off.

Every one of those steps ran through a request and a queue. The people in it did a good job, and each of them had a long list of other projects.

The interface descriptions the agents needed took longer still. Nobody could say who was responsible for them, so people asked people who asked other people.

The process was built for slow coding

None of that was a people problem. Everybody did their best. It was processes, organizational structure and architecture, all built for a time when coding took longest.

A factory shortens the build. It does nothing for the wait around it. Where a release depends on a ticket in someone else’s queue, the line stops at that ticket.

Ask for a self-service platform, not more effort

So I did not ask for more effort. I asked for the platform under the product to become self-service: a team deploys on its own, inside rules someone set once.

That is an organizational decision before it is a technical one. Someone has to own the platform as a product, and someone has to decide which approvals turn into rules.

Before you speed up the build, walk one finished change to production and write down every queue it waits in.

Further reading

  1. AI makes a feature factory faster, not better Automating the system you already have makes teams more efficient at building things nobody needs. The difference lies in where you invest the time AI saves: validation or more features. 2 min readShort post
  2. When agents write the code, judgment should outrank titles Career ladders reward scope because writing good code at volume used to be scarce. Agents moved the scarcity to judgment, and hiring, leveling, the ladder and pay all need to follow. 2 min readShort post
  3. Double throughput needs a mandate, not another pilot A pilot asks a team to prove agentic engineering works here. A mandate states the outcome and makes the boring blockers somebody's problem, which puts the uncertainty on the organization. 2 min readShort post

All 15 posts on Organization and roles

ClientsCase study: A large DIY retailer in Germany

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check