When the factory dispatches the work, the manager runs the line
When the factory handles assignment and status, the engineering manager's job moves from dispatcher to line operator. Five responsibilities now define the role.
Written by
-
Benedikt Stemmildt Founder & Co-CEO
Published: 4 June 2026 Updated: 2 min read
A senior engineering manager asked me a quiet question after a workshop. “If the line assigns the work and the board tracks the status, what is left for me?”
The old job shrank, the new one is bigger
It is a fair question. A lot of what an engineering manager did all day was move information and unblock people. Assign the ticket, chase the status, ping the reviewer, escalate the stuck thing. The factory does most of that now. So the old job did shrink. The new job is bigger, and it is the most interesting management job I have seen in years.
The manager runs the line. Literally, as an operational role. Here is what that job contains, concretely.
You design the gates
Every point where work has to pass a check before it moves on is a decision. What does an agent’s output have to clear before it reaches a human? What does a human-reviewed change have to clear before it merges? The gates are the quality of the factory, and someone has to own them. That is now you.
You watch the gauges
A factory you cannot read is a factory you cannot run. Four gauges cover most of it: the DORA metrics, rework rate, use of what ships, cost per change. Your morning is reading those, not reading a status update. A gauge moving the wrong way is the work.
You set the blast radius
Not every change has the same risk. A copy tweak and a change to the payments path are not the same, and they should not pass through the same gates. You decide which paths auto-merge on green and which stop for a human every time. That single decision is most of how a fast line stays a safe line.
You staff the line for what does not compress
The agent handles the routine. The judgment, the taste, the gnarly cross-team alignment: those still need people, and they need the right people pointed at them. Putting your strongest engineer on a queue an agent could clear is now a management error.
You keep the upstream honest
The line runs as well as the ticket that feeds it. A vague ticket produces a vague pull request, faster. So part of running the line is making sure the work arrives well-scoped. The bottleneck moved upstream, and the manager moved with it.
From dispatcher to line operator
Look at those five jobs. Every one is design, not status-chasing. The job went from dispatcher to line operator, and the line operator decides whether the factory is fast and safe and getting better, or just fast.
If you manage engineers, here is the honest test. Block out your last week and sort it: how much was moving information that the board now moves on its own, and how much was designing the line? The first number is the job that is leaving. The second is the job that is arriving.
What share of your week is still spent being a status router?
Further reading
Written by
-
Benedikt Stemmildt · Founder & Co-CEO
More on Organization and roles
- Your org chart is the context architecture An agent asking a question routes through the same knowledge layers a new hire would. Federated context follows the org chart, with a neutral mediator for the deadlocks.
- Delegate, review, own: the operating model of AI-native teams A model lab's playbook for AI-native engineering teams repeats one pattern across seven SDLC phases. The hard part is the review, where the engineer decides which agent findings matter.
- Moving faster with AI only happens when it is a goal A software factory gives you output speed. Outcome speed needs the organization to change around it, and a change that isn't a goal loses to every change that is.
Scaling needs named owners
Coding agents scale across teams when named people own the platform, the team practice, the guardrails, and the measurement. Rollout & scale is where that ownership is built and handed to internal owners, in your stack.
Training on this topic: Agentic Engineering for Engineering and Product LeadersWant to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check