The New Org Chart.
Exploring how the five-layer Organisation of the Future resolves into a single legible structure.
The corporate hierarchy was not designed to survive this
It was designed to manage information in a world where information was expensive to move. The seven-to-nine-layer enterprise org chart — the one that defines almost every company of consequence built between 1920 and 2015 — is, at its structural core, a solution to a 1920 problem: how do you get information from the front line to the person who needs to act on it, and instructions back to the front line, without it dissolving into noise along the way?
The answer was layers. Each layer served as a compression function. Front-line workers generated data. First-line supervisors synthesised it into summaries. Middle managers translated those summaries into cross-functional coordination. Senior managers turned coordination into strategy inputs. The C-suite made decisions and sent instructions back down the same chain. The org chart was, in every operational sense, an information routing architecture built from people.
McKinsey’s 2026 “State of Organizations” report found something that might be the most understated finding of the year: two-thirds of leaders say their organisations are overly complex and inefficient, and nearly 40% say that redefining process flows — not restructuring, not headcount reduction — is the single biggest productivity unlock available to them right now. The complexity they are describing is not accidental. It is the residue of an information routing architecture that is no longer needed for the purpose it was designed for.
The AI Stack changes the economics of information relay at every layer. A generative engine synthesises. A predictive engine anticipates. A perceptive engine monitors in real time. An agentic engine routes, escalates, and executes. An optimisation engine continuously improves. The five-layer AI Stack — the subject of the first piece in this series — performs, automatically and at scale, the compression and relay function that occupied most of the coordination middle of the traditional org chart.
The question is not whether the hierarchy will change. Gartner estimates 20% of organisations will eliminate more than half their middle management positions through AI-driven restructuring by 2026. Korn Ferry found that 41% of employees already report their company has trimmed management layers in 2024–25. The question is whether the change is intentional — or just a smaller, more confused version of the same broken architecture.
This is the fifth and final piece in my series on the Organisation of the Future. The first four named the building blocks: the AI Stack (the engines), the Operator (the humans who run them), the Verifier (the humans who ensure the outputs earn trust), the Workflow Designer (the humans who architect the road). This piece draws the org chart they all live on.
How the hierarchy got so tall
To understand why the org chart is changing, it helps to understand why it became what it is.
Frederick Taylor formalised the division of labour in the 1910s. Alfred Sloan built the modern divisional corporation at General Motors in the 1920s — the model that the Fortune 500 spent the next fifty years replicating. The divisional structure needed layers because it was managing scale without computers. A VP of Operations at GM in 1950 had no automated monitoring of production lines across twelve plants. They had reports from plant managers, who had reports from shift supervisors, who had reports from team leads. Each layer existed because someone needed to synthesise, check, and relay what was happening in the layer below.
The corporate computer age, beginning in the 1970s and accelerating through the 1990s, compressed some of this — enterprise resource planning systems made data more visible across layers, and the internet enabled real-time communication that shortened some relay chains. But the fundamental management architecture of the industrial corporation survived into the 2020s largely intact. Most Fortune 500 companies still had seven to nine reporting layers between a frontline worker and the CEO in 2024.
The reason those layers persisted, even as technology improved, is that information synthesis — the judgment call about what matters and what doesn’t, what to escalate and what to absorb — was still fundamentally a human task. An ERP system could show you that SKU 7843 was running 14% under plan. It could not tell you whether that mattered, why it was happening, who needed to know, or what to do about it. That judgment lived in the middle layer. The middle layer persisted because judgment was scarce.
The AI Stack changes the scarcity calculus on judgment at three levels simultaneously. It automates the monitoring (perceptive engines). It synthesises the signal from the noise (predictive engines). It routes the escalation to the right human seat, with the right context packet, at the right time (agentic engines). The judgment that middle management spent 70% of its time preparing for — the ten minutes of actual decision-making that justified the hour of synthesis and the two hours of reporting — can now be delivered pre-synthesised to the person who needs to make it.
What gets lost
Before drawing the new org chart, there is something important to acknowledge about what is structurally lost in the transition.
Middle management is not simply a coordination mechanism. It is also an institutional memory system. The manager who has been in post for six years and knows that the finance-sales handoff has a seventeen-step workaround because of a legacy system migration in 2019 is carrying institutional knowledge that does not live in any process document, any ERP system, or any AI training dataset. That knowledge exists as context in a person. When that person leaves — whether voluntarily as part of a restructuring or involuntarily as part of a headcount reduction — the knowledge leaves with them.
This is not a small problem. Gartner’s May 2026 analysis found that AI-driven restructuring is creating budget room but not delivering the productivity returns companies expected. The mechanism is this: companies cut the coordination layer, expecting the AI Stack to absorb the coordination function, but find that the AI Stack was not trained on the institutional context those people carried. The workflow breaks in subtler ways. The escalation goes to the manager who no longer exists. The synthesis misses the context the predictive engine was never given. The agentic engine routes correctly according to the workflow specification but incorrectly according to the institutional reality.
The Workflow Designer’s primary job — mapping the actual workflow, not the documented workflow — is partly a knowledge transfer mechanism. The Mapper archetype of the Workflow Designer role exists precisely because the gap between the process document and the real process is where institutional knowledge lives. Before you can eliminate the coordination middle, you have to extract what it knows. Most companies doing AI-driven restructuring in 2025–26 are not doing this extraction. They are eliminating the relay runners and hoping the documentation is good enough. It rarely is.
The five-layer architecture
The new org chart has five genuine layers. They are not five reporting levels — they are five functional layers with different relationships to the work, to the AI engines, and to each other. A Verifier may formally report to a Director of Operations, but their functional role is in the Trust Layer regardless of where they sit on a reporting tree. The org chart of the future is a functional map, not just a hierarchy chart.
Layer 1: The Engine Room. The AI Stack runs in the background of every workflow the organisation executes. Generative, predictive, perceptive, agentic, and optimisation engines — the five types named in the first piece in this series — are infrastructure, not personnel. They are the most important layer in the new org because they are the one that changes the economics of everything above them. And they are the one most organisations are building without the other four layers in place. The Engine Room is not empty of humans — it requires engineers, architects, and calibration specialists — but those humans are infrastructure roles, not coordination roles.
Layer 2: The Execution Layer. The Operators — Conductors, Translators, Mechanics, and Surgeons, as named in the second piece — are the humans who run the AI-augmented workflows. They are not managing people. They are managing processes that combine human judgment with AI output at every consequential step. The Execution Layer is also the largest human layer in the new org by headcount. Most of the people who survived the reduction of the coordination middle are now Operators, whether or not their job title says so.
Layer 3: The Trust Layer. The Verifiers — Domain Expert, Critic, Auditor, Red Team, as named in the third piece — are the humans who ensure that outputs from the AI Stack earn organisational trust before they are acted on, communicated, or escalated. The Trust Layer is functionally new. In the old org, trust was built through hierarchy: something was trustworthy because a director had signed off on it. In the new org, the director-as-trust-mechanism is being replaced by a systematic verification function. In regulated domains — finance, healthcare, hiring, content moderation — this layer is now legally load-bearing under the EU AI Act, which reached full enforcement in August 2026.
Layer 4: The Architecture Layer. The Workflow Designers — Mapper, Boundary Setter, Recovery Designer, Composer — are the structural engineers of the new org. They sit between the Direction Layer and the Execution Layer, translating strategic goals into designed workflows. They are the new coordination mechanism: instead of a human relay chain synthesising information in real time, a designed workflow specifies in advance where information flows, where it gets synthesised, where humans make decisions, and what happens when the workflow breaks. The Architecture Layer is the smallest human layer in the new org by headcount but the highest-leverage: a single Composer designing a well-specified workflow can enable fifty Operators to execute reliably at scale.
Layer 5: The Direction Layer. The senior leaders who set goals, make strategic bets, and own accountability. What changes at this layer is not title or authority but operating reality. The Direction Layer in the old org received synthesised information through a relay chain and made decisions based on what the relay produced. In the new org, the relay chain has been replaced by designed workflows and AI synthesis — which means the Direction Layer has direct sight-lines to the actual work, without the compression and distortion that six layers of relay introduced. This is both more powerful and more demanding. A senior leader with direct sight-lines to AI-synthesised workflow data is better informed, faster. They are also being asked to make more consequential decisions with less buffer — because the buffer was the middle.
The deleted layer and the coordination question
The layer that the five-band model has no place for is middle management as a coordination mechanism. Not as a person type — but as a functional role: the human whose primary job is to synthesise information from below, coordinate across functions, and relay upward. That coordination function has been absorbed by three parts of the new architecture: the Workflow Designer’s Architecture Layer (who designs the coordination logic in advance), the AI Stack’s agentic and predictive engines (who execute the coordination logic in real time), and the Operator’s Execution Layer (who own the workflow outcomes and make the in-context judgment calls that the design cannot fully specify in advance).
“Shifting attention from structure to flow — with the biggest productivity payoff lying not in reorganising reporting lines but in radically simplifying and unifying processes across the enterprise.”
— McKinsey, The State of Organizations 2026
What this means for people currently in coordination-heavy middle management roles: the function is not disappearing, but its location in the org is changing. The judgment, escalation, and domain expertise components of middle management roles are being elevated into the Operator and Verifier tiers. The synthesis and relay components are being absorbed by the AI Stack and the Workflow Designer. The transition is not “middle managers are being replaced by AI.” It is “the coordination-heavy version of middle management is being replaced by a combination of designed workflows and AI engines, while the judgment-heavy version is being elevated into named functional roles with higher accountability.” That is a harder story to tell in a restructuring announcement, which is why most companies are not telling it.
Building it deliberately
The difference between a company that captures the productivity gain of the new org and one that is still running pilots in 2028 comes down to one question: did they build all five layers, or just the Engine Room?
McKinsey’s finding that only 21% of companies have redesigned their workflows end-to-end is, read through the lens of this series, a finding about which companies have invested in all five layers. The 21% have Operators, Verifiers, and Workflow Designers in place around their AI Stack. The 79% have engines and hope.
Building deliberately means four specific decisions. First: name the role families explicitly. Operator, Verifier, and Workflow Designer need to exist as intentional job descriptions, not as retrofits onto existing titles. Second: do the knowledge extraction before the restructuring. Map the real workflows — with Mapper-archetype thinking — before you eliminate the people who carry the institutional context those workflows depend on. The order matters enormously. Most companies are getting it backwards. Third: design the Trust Layer for your regulatory context. In high-risk domains, the Trust Layer is now legally required, not just good practice. The companies that treat the Verifier as optional are building legal liability into the org chart. Fourth: widen spans of control intentionally, not accidentally. Span-widening only works if the Workflow Designers have done their job. If the Architecture Layer is under-resourced, wider spans of control at the top become a recipe for chaos.
The closing uncomfortable truth
Gartner’s most quietly important finding of 2026 is this: AI will create more jobs than it eliminates — but not until 2028. Through 2026 and 2027, the net effect on global employment is roughly neutral. We are in the transition window — the period between old org and new org in which both are partially visible.
The companies that build the new shape deliberately during this window will be the ones with the Architecture Layer, the Trust Layer, and the Execution Layer staffed and operational by the time the transition completes. The ones that cut the relay middle without installing the new structure will find themselves in 2028 with AI engines, no coordination architecture, and a growing list of workflows that break in ways nobody can diagnose — because the institutional knowledge left with the people who were made redundant in 2026.
The org chart of 2030 has fewer layers than today’s.
The people who remain carry more judgment, more accountability, and more leverage than anyone in the 2020 version of the same company. The flat org is not a smaller version of the tall org. It is a different shape entirely.
Drawing that shape on purpose is the only version of this that works.
This is the fifth and final piece in my series on the Organisation of the Future. The full series: The AI Stack (May 27) → The Operator (June 3) → The Verifier (June 10) → The Workflow Designer (June 17) → The New Org Chart (June 24). Thanks for reading!