The premise
The org chart is obsolete
The hierarchy of people was built for a specific set of conditions. Coordination was expensive. Communication was slow. Institutional memory lived in heads. The only operational unit available was a human being. Every structural assumption in modern organisational design traces back to those four constraints. None of them holds anymore. And yet the map we use to draw companies still assumes all four.
Every company has the same five operational layers underneath its org chart. The layers do not change. What changes is who, or what, operates each of them.
Staffed by humans
Every layer operated by people. The people carried the knowledge, ran the processes, made the decisions, and coordinated the work. Scale meant headcount. Capability meant hiring.
Operated by capabilities
Each layer becomes a capability: agents doing the work, knowledge feeding them context, workflows connecting them, evaluations measuring the output. Humans build, manage, and teach the capabilities. They stop staffing the layers and start governing them.
The diagnostic question. If you were designing your organisation from scratch today, knowing what agent infrastructure can currently do and the rate at which it is improving, would you draw the same org chart? Almost certainly not. The five layers below are the structure of the organisation that replaces it.
Section II
The five layers
These are not functions. Not departments. Not process areas. They are the underlying architecture of every organisation. A function sits inside a layer. A department spans parts of several. A process runs across them. Click each layer to expand the full detail: what it contains, how it is currently operated, what a capability looks like, the failure mode, and the question to ask about your own company.
What it contains
- Strategic rhythm and board cadence
- Cross-functional decisioning
- Feedback loops and environmental reading
- The capacity to adjust as conditions change
- Decision logs: what was decided, why, and what happened
What a capability looks like now
Ground truth becomes achievable. Every signal, every action, every decision: visible, queryable, real. Advisor agents synthesise what is happening continuously. Scenario analysis runs before decisions are made. The quality of information reaching decision-makers improves dramatically. The decision log compounds over time into an asset no competitor can replicate.
The failure mode
Leaders use the capability as a dashboard and nothing more. They read the outputs but do not change how they decide. The meetings look the same. The politics still shape what surfaces. The advisor agents get ignored when their analysis is inconvenient. The capability provides ground truth but the organisation does not yet know how to act on it.
The question for your company
What percentage of the decisions your executive team made last quarter were made on the information you actually needed, versus the information that happened to reach you?
The old operating pattern
Each function was a team plus tools. The team carried the knowledge. The tools supported the execution. Marketing was a marketing team running marketing software. Sales was a sales team running a CRM. The function was indistinguishable from the people inside it.
What a capability looks like now
A function is no longer a team with tools. It is a capability: task agents executing, operator agents holding standing responsibility, advisor agents handling strategic questions, domain knowledge feeding all of them. One person managing this capability replaces the operational capacity of a team many times their size. Not because they are heroic. Because the capability is doing the work.
Example: marketing capability
- Task agents: campaign execution, content generation, performance reporting
- Operator agents: content operator, campaign operator, analytics operator
- Advisor agents: brand decisions, unusual campaigns, strategic questions
- Knowledge: canonical brand, market context, customer segments, domain playbooks
- Evaluations: scoring outputs against defined standards of good
The same pattern applies to
- Sales: pipeline agents, outreach operators, deal advisor agents
- Customer success: support agents, escalation operators, retention advisors
- Operations: process agents, compliance operators, optimisation advisors
- People: candidate agents, onboarding operators, culture advisors
- Partnerships: prospecting agents, relationship operators, negotiation advisors
The failure mode
Companies deploy agents on top of the existing functional shape without redesigning the function. The marketing team adds an AI assistant. The sales team adds a prospecting bot. Each one is useful and none of them changes the shape of the function. Productivity improves at the margin. The cost structure does not. This is the single biggest waste of the current moment and it is happening at scale right now.
The question for your company
If you were designing your marketing function from scratch today, would you start with a team and add tools? Or start with a capability and assign humans to build, manage, and teach it?
What it contains
- Banking, accounting, and financial reporting
- Tax obligations across every jurisdiction the company operates in
- Contracts: drafting, negotiation, execution, monitoring
- Data protection and regulatory compliance
- Payroll, benefits, and statutory obligations
What a capability looks like now
Books reconcile in real time. Tax obligations surface the moment they become relevant. Contracts generate from templates, get drafted, negotiated within defined parameters, and surface for human review only when they step outside those parameters. Compliance runs as monitoring rather than panic. The layer moves from periodic human intervention to continuous background process.
The failure mode
Companies treat infrastructure as the thing to automate first because it feels the most mechanical. They deploy agents before they have written down what good looks like. An agent that files a return incorrectly at speed is worse than a human who files it correctly slowly. Infrastructure is the layer where evaluations must exist before the automation does. Companies that skip this sequence end up with a mess harder to fix than the original inefficiency.
The question for your company
Which parts of your infrastructure layer are you still treating as periodic human intervention when they could run as continuous background capability? And do you have the evaluation discipline in place to automate them safely?
Four kinds of knowledge
- Canonical: what the company is, who the customers are, how it is structured — stable bedrock
- Operational: live state, what is in the pipeline, what changed overnight
- Domain: how things get done — the playbooks, patterns, reusable intellectual capital
- Experiential: decisions and outcomes, edge cases, failures and what they taught
How the old model failed
It lived in people's heads. Some of it got written down, usually in documents nobody updated. Most of it moved through conversation and quiet transfer. When people left, they took the knowledge with them. Every organisation I have worked inside at scale was fundamentally leaking knowledge all the time. It was the cost of doing business.
What a capability looks like now
- Canonical knowledge in structured, versioned markdown files
- Operational knowledge in live systems reading state in real time
- Domain knowledge in playbooks agents can reference as context
- Experiential knowledge in a growing archive of decisions and lessons
- Operator agents maintaining the knowledge continuously
- The knowledge compounds every week without additional training
Why this is the moat
You cannot buy this layer. You can only build it over time. Every engagement adds to it. Every decision encoded deepens it. The competitors who start building six months from now will be six months behind on the only asset in this architecture that does not commoditise. Competitors can access the same models. They cannot access your knowledge.
The failure mode
Companies confuse storage with organisation. They dump documents into a shared drive and call it a knowledge layer. What they have is a landfill. Agents cannot find what they need. Context arrives stale. The experiential layer never gets captured because there is no routine practice for writing down what was learned. The capability looks like it exists but it does not compound.
The question for your company
If your best people left tomorrow, what percentage of what they know would survive? And if you had to get an agent productive in your business this week, could you hand it a knowledge base and trust what it read?
What it contains
- Entity formation and legal structure
- Equity structure and cap table
- Governance: board, decision rights, accountability
- Intellectual property: registration, ownership, defence
- Positioning: the story the company tells the market
What a capability looks like now
Templates for every standard entity type in every standard jurisdiction. Equity structures drawn from proven patterns with tax, vesting, and founder-protection implications already modelled. Governance frameworks installed with standing agendas and decision rights. IP registration and monitoring running as a continuous background process. Positioning refined against live market signal, not set once and forgotten.
The failure mode
Founders treat foundation as sunk cost and stop paying attention. The articles do not match the current reality. The cap table has undocumented side letters. Governance is a calendar invite that never quite lands. Then something happens, a raise, an acquisition offer, a dispute, and the foundation layer turns out to be weaker than anyone realised.
The question for your company
What would it take to turn your foundation layer from a one-time setup into a living capability that maintains itself and surfaces issues before they become crises?
The org chart draws reporting lines across layer four only. The company map shows all five. The companies redesigning around this shape are the ones thinking in all five dimensions at once.
Section III
The connective tissue
Four disciplines run through every layer. A capability built without any of the four is incomplete. Most organisations are underinvested in at least two of them and do not know it.
Context engineering
The discipline of deciding what agents see, what they remember, how knowledge is structured, and how it flows between layers. Not prompt engineering. Information architecture for agents. The companies furthest along treat this as a dedicated practice. The companies that skip it produce agents that are technically capable and contextually useless.
Evaluation infrastructure
The scoring, regression testing, and feedback loops that tell you whether capabilities are working. Without evaluation, capabilities drift. Memory that is not measured decays. You are not running a capability. You are hoping. This is the discipline with the highest return in the new stack and the one most companies skip entirely.
Orchestration
How capabilities coordinate across layers. The sales capability needing brand context from marketing. The support capability needing product data from operations. The leadership capability pulling ground truth from every layer at once. Orchestration is what turns five separate capabilities into a coherent organisation rather than five expensive silos.
Governance
The policies, permissions, and safeguards that determine what capabilities are allowed to do on their own, what requires human review, and what is off-limits entirely. Governance done well is invisible. Governance done badly is the story that ends up on the front page. The layer most companies are underinvested in and the one regulators are about to look at hardest.
These four run through every layer. If any one of them is missing or weak, the layer built on top of it cannot hold. The companies redesigning around the new shape are thinking in both dimensions at once: five layers and four disciplines. Eleven cells on the map. Most companies have work to do in at least seven of them.
Section IV
Where is your company on the map?
For each of the five layers, how would you honestly describe where your company currently sits? Select the description that is closest to your current reality. No right answers. The output is a starting point.
Choose your current state across all five layers
Layer 01 · Foundation
Set and forgotten
Legal structure exists. Nobody has looked at it since incorporation. Governance is informal at best.
Maintained reactively
Revisited when something breaks. Generally current but not actively managed or monitored.
Living capability
Continuously maintained. Issues surface before they become crises. Governance runs on a defined cadence.
Layer 02 · Knowledge
Lives in heads
Knowledge is in people. Fragmented in email and chat. Would leave with the team if they left.
Stored but not structured
Documents exist. Wikis exist. Most of it is out of date and hard for agents to use directly.
Structured and compounding
Plain text files. Maintained by agents. Grows with every engagement. Portable across models.
Layer 03 · Infrastructure
Periodic and manual
Finance closes monthly. Compliance reviewed annually. Legal brought in when needed. All reactive.
Tools in place
Accounting software, contract management, compliance tools deployed. Still requires significant human time.
Continuous capability
Books reconcile in real time. Obligations surface automatically. Contracts generate and monitor themselves.
Layer 04 · Functions
Teams with tools
Functions are people plus software. AI assists individuals but the function shape has not changed.
Partial capabilities
Some workflows are agent-run. Humans still own most execution. Hybrid and slightly uncomfortable.
Capability-led
Functions redesigned around agents. Humans build, manage, and teach. One person does what a team once did.
Layer 05 · Leadership
Working on filtered information
Decisions made on what reaches the table. Ground truth rarely makes it up without distortion.
Better dashboards
More data available. Still making sense of it manually. Decisions improved but not transformed.
Ground truth accessible
Advisor capabilities synthesise what is happening. Scenario analysis runs before decisions. Decision log compounds.
Your map
What next
The map is not the terrain
Drawing the map is where the redesign starts. The companies that do this exercise honestly in the next six months will be operating in the new shape before the companies still arguing about reporting lines even notice the ground has moved.