The agentic org chart is two people deep

Org charts aren't administrative artefacts. They're a theory of work. Every box and line is an assumption about who needs to tell whom what to do. A tall pyramid says execution is expensive, specialised, and hard to coordinate without layers of people translating intent down the chain. That assumption has been true for most of human organisational history.

It's stopping being true right now.

I've spent the last year working with companies building agentic systems, and I keep seeing the same thing. The org structures people are defending were designed for a world where humans performed the bulk of execution work. That world is changing faster than most leadership teams are willing to admit.

What the old shape assumed

The traditional hierarchy exists because coordination is hard. A CEO has a vision but can't personally talk to every engineer, every support rep, every analyst. So you add managers, then managers of managers. Each layer's job is to take intent from above and translate it into specific tasks below. Useful work, when the execution layer is made of people who need direction, context, and feedback to function.

Middle management, in this model, is the translation layer. The person who turns a strategic priority into a sprint backlog. The team lead who turns a support philosophy into a ticket-handling process. The legal coordinator who turns a GC's instincts into a review checklist. Translation work. Real work.

What's shifted is that AI agents translate intent into tasks themselves. Give a well-configured agent system a goal, context, and constraints, and it decomposes the problem, plans the steps, and executes. Not perfectly. Supervision still required. But the supervision is lighter than what it replaces, and it operates at a different altitude. You're not managing tasks. You're managing outcomes.

The shape that's emerging

I'd argue the natural shape of an AI-first organisation is two people deep.

A principal decides what's worth doing. This is a senior role: setting direction, holding context, making judgement calls, owning accountability. Call it founder, executive, or lead strategist depending on your context. The title matters less than the function. This person has to be good.

An operator runs the agent fleet. This person configures, monitors, and improves the systems that do the work. They catch errors. They know when to intervene. They understand what the agents can and can't handle. They're part systems thinker, part quality control, part infrastructure owner. This role is new and genuinely skilled.

Between them? Not much. The translation layer shrinks because agents handle translation.

What this looks like in practice

Take a product team. Twelve people: PM, engineers, designer, researcher, QA, analyst, scrum master, support. Standard mid-size squad. In an agentic setup that's closer to three: a product lead who owns the roadmap, an operator running the agent systems for spec writing, code generation, test coverage and analytics, and maybe a designer doing the work that still genuinely benefits from a human eye. The other nine aren't fired in a weekend. Over a two-year horizon, you're not backfilling them when they leave.

Or take a customer support team of forty. That team exists because each interaction takes human time and volume is high. With a well-built agent fleet, you might run the same volume with five people: an operator managing the systems, two or three specialists handling the complex cases the agents escalate, and a lead who owns the overall customer experience and makes calls on policy. The other thirty-five positions don't get posted again.

Legal review is instructive at the other end. One general counsel with a well-configured agent system can cover a workload that previously kept three or four junior lawyers busy. The GC supplies judgement: what's a real risk, what matters given the situation, when to push back on a clause. The agent handles the reading, the summarisation, the clause comparison, the first-pass flagging. Output per senior person goes up sharply.

None of these examples require AGI. They're possible right now, with current systems, for any company willing to build them.

What the remaining jobs look like

The jobs that persist are senior jobs. The work that remains is more interesting: more judgement, more ambiguity, more real decisions. You're not approving PRs or triaging tickets. You're deciding what to build, who to serve, what risks to carry, when to stop.

The operator role is genuinely new and underappreciated. They write effective agent instructions, design evaluation systems that catch errors before they compound, debug agentic pipelines, and judge when a workflow is trustworthy enough to run with less oversight. That's a real craft. We don't have good names for it yet, and we're not training people for it in business schools.

The jobs that struggle to persist are coordination jobs. Roles that exist to translate someone else's intent into someone else's action. To write status updates, run standups, own the ticket queue, chase approvals. A lot of good people have built careers in exactly these roles, and they'll need to reorient. The honest thing is to name it.

Why companies are slow to redraw the chart

The political reason is obvious. The people who run companies got there by being good at navigating large, complex organisations. Their networks are built into the existing shape. Shrinking the hierarchy shrinks their domain, and often their identity.

The subtler reason is that rebuilding around agentic systems requires making explicit what was previously implicit. A good middle manager carries enormous tacit knowledge about how things get done and which rules are actually enforced. Remove that layer and you have to encode it somewhere, usually in agent instructions and evaluation criteria. Unglamorous work that requires the principal to articulate things they've never had to write down.

Most organisations find it easier to add an AI tool to the existing structure than restructure around it. So they do. They get modest gains and tell themselves they're keeping up. They're not.

The question worth sitting with

The organisations moving fast share one quality: the people at the top understand what agents can actually do, not in the abstract but in detail, and they've built the willingness to act on what that implies.

The ones that are stalling share a different quality. Everyone can see what's happening. The senior people know the translation layer is becoming automatable. The middle managers know their roles are changing. The operators they'd need to hire don't exist yet at scale. Nobody wants to say it out loud.

The question isn't whether agentic systems will flatten your organisation. That's in motion regardless. The question is whether your team already knows, and is quietly hoping no one notices.