Structure: Your Org Chart Is a Fossil

Why this module exists

Most AI programmes bolt a tool onto the bottom of an unchanged organisation chart and are then surprised that nothing structural improves. Meanwhile the strongest empirical correlate of AI-attributable profit impact, across every large survey, is not model choice or vendor selection. It is fundamental workflow redesign.

That finding is usually read as an implementation lesson. It is a structural one. This module supplies the theory that explains why, and an instrument for acting on it.

9.1 Firms exist because coordination is expensive

Start with a question that earned a Nobel Prize: why does your company exist at all?

Everything it does could in principle be bought from the market — accounting from a firm, sales through agents, production from contract manufacturers. So why keep all those people inside, with salaries and the overhead of managing them?

Ronald Coase answered this in 1937: firms exist because using the market is expensive. For every task you would otherwise have to find a supplier, negotiate, contract and monitor. He called these transaction costs. When they exceed the cost of coordinating the work internally, the firm grows; when the balance flips, it shrinks. The boundary of your company is drawn not by your product but by the price of coordination.

Two earlier figures complete the picture. Frederick Taylor, in 1911, separated the knowledge inside work from the person doing it and wrote it down — making craft knowledge portable and therefore manageable. Max Weber explained why bureaucracy was winning: files, hierarchies and written rules were the only way to process information reliably at scale with the technology available.

Put their shared discovery in current language: management is an information technology. Every layer on your chart is an answer to an information problem. How does the truth on the ground travel up? How does the decision at the top travel down? Who needs to know what, and who must approve what?

Middle management was invented for exactly this: compress information from below and carry it up, unpack decisions from above and distribute them down. We have paid salaries for that for a century, because for a century a human was the only available router.

This has never been static. The telephone made the multi-branch firm possible. ERP systems in the 1990s turned "the person who compiles the inventory report" into a query screen — and produced precisely the delayering debate we are having again now.

The pattern is consistent: as moving information got cheaper, the layers built to move it got thinner. But deciding, taking responsibility and building trust never got cheaper.

9.2 Transport and judgement

That distinction is the instrument. Hold it precisely:

Now bring it down to one person's day. A scene from a distribution business, anonymised but real in outline.

A regional manager sits down at nine on Monday. Three windows are open: the sales export from the ERP, weekend messages from six field representatives, and the weekly report template headquarters expects at three. The next five hours go into moving numbers into the template, distilling a summary out of scattered messages, and calling to verify two lines that do not match last week. At three, the report goes out.

At half past three the real work lands: the region's largest customer wants payment terms extended from sixty days to ninety. That decision requires knowing the customer, knowing the sector's cash position this quarter, and answering "is this customer bluffing or genuinely in trouble?" with instinct built over years. The manager gives it twenty minutes, at the most tired hour of the day.

Which earns the salary — the five hours or the twenty minutes? Everyone knows the answer. But the architecture of the day says the opposite. The salary is paid for judgement; the hours go to transport.

Inside one box on the org chart sit two different jobs, one newly cheap and one newly more valuable, crammed into the same calendar. The promise of AI is not to delete the box. It is to hand the five hours to a machine and move the twenty minutes to the best hour of the day.

9.3 The layer audit

The instrument. For every box in your function, four questions:

Question four is the honesty test. There are legitimate answers — more customer contact, faster decisions, work currently not done at all, capacity for growth without hiring. There is also a legitimate answer that says the role shrinks. What is not legitimate is presenting a headcount reduction as a redesign and being surprised when the organisation resists it. People are extremely good at detecting which one is happening.

9.4 Operating models

Where does AI capability live? Four answers, with honest trade-offs.

The hybrid is the most common right answer, and it only works if you write down which decisions are central and which are local. A defensible split:

• Central: which data may go where, the control set from Module 6, the platform and its traces, vendor gates, the evaluation-set standard.
• Local: which processes to attack, the priority order, the acceptance criteria, and who approves what within their own decision rights.

The failure to specify this is the single most common structural cause of stalled programmes: a centre that believes it owns prioritisation and business units that believe they do.

9.5 Roles, capability and the scarce skill

Module 1 established that AI compresses the gap between novice and expert on tasks inside the frontier. That has a direct consequence for what you should be hiring and developing.

If producing the first draft is cheap, the scarce skill moves to two places:

Specification. The ability to state precisely what good output looks like — the standard, the exceptions, the edge cases. This is what turns a vague ambition into the acceptance criterion of Module 5, and it is rarer than it looks. Most organisations discover, on their first serious deployment, that nobody had ever written down what a good version of the work actually is.

Detection. The ability to notice that fluent output is wrong. This is domain expertise, and its value rises rather than falls — but it is deployed differently, on review rather than production.

Three practical implications:

1. Do not remove the training ground. If juniors historically learned judgement by doing transport work, automating all of it removes the path by which your future seniors are made. Design the replacement deliberately — review rotations, deliberate exposure to hard cases — or you will discover the gap in five years.
2. Promote the specifiers. The people who can articulate the standard are now more valuable than the people who can execute it quickly.
3. Buy the platform, build the knowledge. Module 8's conclusion, applied to people: the durable asset is your process knowledge in usable form, and only your people can produce it.

9.6 Incentives, or why good governance dies

Everything in this course fails if the incentive structure punishes the behaviour it requires.

Module 2 named the asymmetry: failing conventionally is free, and succeeding unconventionally invites suspicion. Inside an organisation this produces a specific pathology — nobody kills their own project. The evaluation is written by the sponsor, the pilot succeeds ambiguously, and the portfolio fills with systems that no one believes in and no one will stop.

Four mechanisms change the payoff, and all four are within a single leader's authority:

Separate the proposer from the measurer. The person who pre-registers the pilot metric should not be the person whose budget depends on the result. This is not distrust; it is the same principle as separating trading from settlement.

Put the no-list in the pack, not the appendix. Make the decisions not to use AI a standing agenda item with named reasons. This converts "I killed my project" from a confession into a deliverable.

Reward falsification explicitly. When someone produces the evidence that stops a project before it burns a year, say so in the forum where promotions are discussed. Once. Everyone will remember.

Make the sentence sayable. The single practical test of an organisation's AI culture is whether a mid-level manager can say "we checked, and it doesn't need a model" in a meeting without their voice rising at the end. If they cannot, your governance is decorative regardless of what the policy says.

Exercise — Run the layer audit

Time: 90 minutes. Produces the artefact for this module.

1. List every role in your function. Roles, not people.
2. For each, estimate the transport/judgement split. Estimates are fine; precision is not the point, and asking the people doing the work produces better numbers than guessing.
3. Answer questions 2, 3 and 4 for each: are decisions recorded, is the loss information or trust, and what happens to reclaimed time.
4. Mark the highest-judgement role and ask whether anything currently captures what it knows. This is usually the most important finding.
5. Choose one transport block to remove this quarter — and check first whether it needs a system at all. Roughly a third of transport work turns out to be producing something nobody uses.
6. Write your operating-model split: three decisions that are central, three that are local.

Self-check

1. Why is "management is an information technology" more useful than "AI automates tasks"?
2. In your own week, which block is transport and which is judgement — and which one gets your best hours?
3. A role scores 65% transport. What are the three legitimate answers to "what happens to the reclaimed time," and which applies?
4. Which role in your function would cost you trust rather than information if it vanished, and what currently captures its knowledge?
5. Could a manager two levels below you say "we checked, and it doesn't need a model" in a meeting without hesitation? What would change that?

Further reading

• Ronald H. Coase, The Nature of the Firm, Economica, 1937.
• Frederick W. Taylor, The Principles of Scientific Management, 1911.
• Erik Brynjolfsson, Danielle Li and Lindsey R. Raymond, Generative AI at Work, NBER, 2023 — on the compression of the novice–expert gap.
• McKinsey, The State of AI — workflow redesign as the strongest correlate of impact.