The Bundle
For a century, the manager held a bundle. Coordination, memory, escalation, legitimacy, succession: five functions packaged into one role and replicated layer after layer up the hierarchy. The bundling was practical. Information moved slowly, decisions had to be routed, and human cognition could only carry so much state.
That bundle is coming apart.
In The Decline of the Org Chart the argument was that hierarchy was a routing protocol made physical. Its layers existed because information could not flow directly between the people who held context and the people who held authority. The ceremony built around those layers, the standups and the steering committees and the change advisory boards, was the routing mechanism made visible. Agentic AI changes the routing assumption. When information no longer needs to travel through human nodes to acquire authority, the layers stop justifying themselves.
The question now is not whether managers disappear. It is what survives when the bundle comes apart, and where human judgment still does work that nothing else can do.
Three of the five functions were operational. The manager held memory of decisions, dependencies, and rationale across teams. The manager cleared blockers: chasing approvals, brokering access, resolving ambiguity at boundaries between teams. The manager translated intent, turning strategic direction into work the team could act on, and surfacing execution reality back upward.
The other two were institutional. The manager held political legitimacy, the right to commit on behalf of a function. And the manager held career fate: who got promoted, who got coached out, who got the next opportunity.
The split matters. The operational functions were artifacts of human bandwidth. The institutional functions are artifacts of trust and accountability, and those do not dissolve because the routing layer dissolved.
The question is where each surviving function lives.
The Roadblock Remover
We ran an experiment we called Pathfinder. We removed a layer of management and replaced the bundle with a deliberately narrower role: the roadblock remover. No status reporting, no resource allocation rituals, no managing-up theater. Three responsibilities only.
First, hold memory: who decided what, why, against which constraints, with which dependencies still open. Second, clear blockers: get the access, the answer, the unblock that keeps small teams moving without ceremony. Third, exercise judgment at the boundary, where two teams disagree, where intent is ambiguous, where the specification has gone silent on the question that matters today.
The pattern was clear. Teams moved faster, decisions reached the right people sooner, and the layer of effort spent making work legible to non-builders compressed.
Of those three responsibilities, two are within reach of agentic AI today.
Memory retrieval is the cleanest case. An agent with access to the events that already exist across the organization, the decisions, the dependencies, the open threads, can hold more state than any human manager and surface it on demand. This is not summarization. It is structured recall against a shared knowledge graph. The roadblock remover spends less time reconstructing context, because the context is queryable.
Clearing is partial. Some of it is mechanical: who owns this approval, has the dependent ticket moved, is the staging environment available. Agents handle that without supervision. Other parts require commitment on behalf of a function or a budget, and those still need a person whose authority is real. AI accelerates the clearing. It does not absorb it.
Judgment at the boundary is the residue. When the specification is silent on a tradeoff that matters, when two teams hold legitimate but incompatible views, when a customer commitment collides with an architectural principle, the decision belongs to a human. Not because AI is incapable of making it. Because the accountability for that decision is not transferable.
The Bottleneck Moves
This is the structural point. As agents absorb the operational layer, the constraint on organizational velocity stops being routing. It becomes specification quality.
A team supported by capable agents goes exactly as fast as its specification is precise. Ambiguity used to be absorbed by human managers reading between the lines, escalating gracefully, brokering implicit deals across the org. Agents do not do that. They execute against what is written. What the specification leaves unsaid becomes either an error or a question, and the cost of unsaid material rises.
The implication is direct. Investment that used to flow into management capacity should now flow into specification capacity: the ontology, the state models, the intent expressed precisely enough that an agent can reason from it. The same shift has been identified at the system level under the heading of the meta-information layer. The organization mirrors the architecture. Where reasoning lives, ceremony recedes.
What Survives
Three locations absorb what the bundle held, and three accountabilities go with them. Specification and delivery move into the teams themselves: the people closest to the execution own the precision the agents depend on, and a named role inside the team carries delivery accountability.
A governance layer of architects, security, quality, and compliance codifies the guardrails that hold across teams; that layer is accountable for the standards, not for any particular delivery.
The manager, finally relieved of the routing role, becomes an enabling function: accountable for the team's capacity to deliver rather than for the delivery itself. That distinction is real. It includes hiring and role design, institutional unblocking, coaching and development, and the conditions under which the team can recover when delivery goes wrong.
Performance signals shift with the accountabilities. The sprint review, the steering update, the dashboard with seventeen colors carry less information than they did. The legible artifacts are the specifications themselves and the team's progress against them. What an executive needs to know is now reachable directly.
The instinct to find a single throat to choke is the residue of the routing era. It existed because executives could not reach into the work. In an agentic, specification-driven organization, they can. The accountability is not diluted; it is located where it actually lives. Delivery sits with the team. Capacity sits with the manager. Standards sit with governance. The executive who wants one throat for everything is asking for the old bundle back.
What we lose is the role that existed primarily to make work legible to non-builders. What we keep, redistributed across the three locations, is the work that exercises judgment, codifies standards, and develops people. They were never the same role. The hierarchy made them look like one.
Smaller teams. Flatter structures. Specification treated as a primary engineering artifact rather than a meeting output. Roadblock removers, not project managers. Judgment located close to the work, not in the layer above it.
There is less organization, and what remains is sharper. Fewer layers, fewer rituals, fewer roles whose existence depends on the routing problem. Specification protocol replacing routing protocol. Judgment located close to the work. Accountability located rather than diffused. Less in volume. Sharper in shape. The shift is structural, not cosmetic. And it asks leadership to invest in clarity of intent the way previous generations invested in clarity of process.
The manager bundle is coming apart. What replaces it is not a different bundle. It is a sharper division between work that can be specified and work that cannot.
