Elvin Garcia · ORGANISMIC
For more than a century, the org chart has pretended to be business architecture. It is not. It is a map of human limitation.
We divided companies into departments because human beings could not hold the whole business in mind. No one person could continuously detect every market signal, remember every customer interaction, make every judgment call, coordinate every dependency, execute every task, transact with every counterparty, enforce every boundary, and learn from every failure. So we broke the firm into boxes. Marketing would look outward. Sales would convert interest into revenue. Operations would make the machine run. Finance would count and constrain. HR would manage the human substrate. Legal would guard the perimeter. Support would absorb the pain coming in from the outside world.
This was not foolish. It was necessary. The modern organization chart emerged in response to a real information problem: how to coordinate activity at a scale no individual operator could directly supervise. Daniel McCallum’s famous 1850s railroad chart was not originally a vanity diagram. It was a way to route operational information through a complex system of tracks, stations, managers, workers, and schedules.[1] As the railroad grew, the difficulty was not simply doing the work. The difficulty was making the right information available to the right authority at the right time. The org chart was an answer to that problem.[2]
But every architecture carries the assumptions of the constraints that produced it. The department was a solution to the age of human scarcity: scarce attention, scarce memory, scarce parallelism, scarce trust, and scarce coordination bandwidth. The manager became a router. The meeting became a synchronization ritual. The memo became a memory patch. The dashboard became an attempt to give leaders the illusion of systemic awareness.
Now businesses are attempting to run artificial intelligence through this inherited anatomy. They install a marketing agent, a sales assistant, a finance copilot, a customer-support bot, and an operations workflow. Then they wonder why the promised transformation feels strangely small. The answer is simple: they have not built an AI-first firm. They have merely accelerated the old silos.
AI does not naturally think in departments. It does not care whether a task belongs to Marketing, Sales, Operations, Finance, HR, Legal, Product, or Support. Those are human institutional categories. AI operates on a different substrate: context, memory, goals, tools, permissions, constraints, feedback, and execution. If you give AI the old department map, it will inherit the old bottlenecks. It may move faster inside each box, but the business itself will remain fragmented.
The real transformation is not that AI replaces employees. The real transformation is that AI exposes the deeper anatomy of the firm. Beneath every department is a smaller set of universal business functions. These functions are not job titles. They are not teams. They are not software modules. They are the recurring necessities every business must perform in order to survive contact with reality.
A business must Sense. It must Remember. It must Decide. It must Coordinate. It must Execute. It must Exchange. It must Govern. It must Adapt.
This is the anatomy underneath the org chart.
Departments are groups of people with similar responsibilities. is really functions are necessities the business must perform continuously.. AI should be organized around what the business must do, not around where humans used to sit.
Managers route information across boxes. is really coordination becomes a designed operating layer.. The firm no longer depends on human middleware for every handoff.
Knowledge lives in people, tools, and departmental memory. is really memory becomes a shared substrate.. The business can compound learning instead of repeatedly rediscovering itself.
Governance lives in specialized departments. is really governance runs through every function.. Autonomy becomes safe only when boundaries are systemic, not advisory.
Failure becomes blame, escalation, or institutional amnesia. is really failure becomes adaptation.. The firm can metabolize error into durable improvement.
The org chart was a patch for human scarcity
The first mistake in criticizing the org chart is to treat it as stupid. It was not stupid. It was one of the great managerial technologies of the industrial age. It made scale possible. It allowed large firms to divide responsibility, specialize labor, clarify reporting lines, and convert human effort into repeatable output.
The problem is that the org chart was built around a particular kind of organism: a company made primarily of human minds. Human minds are extraordinary, but they are narrow-bandwidth. They attend to a few things at a time. They forget. They distort memory through politics, incentive, fear, and emotion. They get tired. They protect turf. They experience coordination as friction. They need ritual, trust, incentive, and hierarchy to work together at scale.
Departments emerged because specialization was the only practical way to increase throughput. If one group learned the market, another group managed the ledger, another group ran production, and another group handled customers, the whole system could do more than any individual could do alone. But this specialization created a new problem: the business became divided against its own knowledge.
The customer knew the company as one entity. The market punished the company as one entity. Cash flowed through the company as one entity. Reputation accrued to the company as one entity. But internally, the company experienced itself as many partial perspectives, each with its own language, incentives, metrics, tools, and memory.
This is why businesses have always required so much routing. The sales team learns something the product team needs to know. The support team hears a pattern the marketing team should understand. The finance team sees a constraint the operations team should anticipate. The legal team knows a risk the growth team is about to create. The founder carries a thesis that has not yet been translated into the daily behavior of the company.
The org chart is the visible diagram of this fragmentation. It is not merely a reporting structure. It is a map of where context goes to die.
This was tolerable when all businesses were slow. It becomes pathological when the environment accelerates. As information flows increase, the cost of departmental handoffs rises. McCallum’s railroad problem was already a data problem: scale produced more information than existing managerial structures could use effectively.[1] Today the same problem has returned at machine speed. There is more signal, more software, more customer feedback, more operational data, more regulatory complexity, more market volatility, and more internal communication than any department-first architecture can metabolize.
Departmental AI is not AI-first
Most companies will make their first major AI mistake by installing intelligence into the existing boxes. They will ask what AI can do for Marketing. Then what AI can do for Sales. Then what AI can do for HR. Then what AI can do for Finance. This approach feels practical because it maps onto the budget lines and executive ownership structures the company already understands.
But this is exactly why it fails to transform the business.
When AI is deployed department by department, it inherits the assumptions, permissions, data access, incentives, and blind spots of each department. A marketing agent may generate campaigns without seeing the customer-support patterns that should change the message. A sales assistant may draft follow-ups without understanding operational capacity. A finance copilot may analyze spend without seeing the strategic experiments that justify temporary inefficiency. A support bot may resolve tickets without feeding product intelligence back into the system.
The result is not an organism. It is a department store with faster cash registers.
One qualification, and it is the load-bearing one. Nothing here says the org chart is dead, or that every firm must abandon it. The claim is conditional and should be read as such: if the goal is to leverage AI at the core of the business rather than at its edges, then the departmental structure has to give way to the functional one. A firm that wants AI at the edges — faster drafting, better search, a support deflection rate — can keep its chart and will be fine. The argument that follows applies to firms that want the other thing, and it is an argument a reader can escape only by rejecting that premise rather than by disputing the reasoning.
The deeper issue is that department names are not native computational objects. They are social compromises. They describe how humans historically clustered work, not how intelligence should reason through a business. An AI system needs to know the goal, the available context, the memory of prior action, the tools it may use, the permissions that constrain it, the risks that require escalation, and the definition of done. It does not need to know whether the task “belongs” to a legacy department unless that boundary encodes a genuine governance constraint.
This distinction matters because AI amplifies architecture. If the architecture is coherent, AI can accelerate coherence. If the architecture is fragmented, AI accelerates fragmentation. A company with poor memory gets faster amnesia. A company with weak governance gets faster risk. A company with unclear ownership gets faster confusion. A company with siloed data gets faster local optimization at the expense of systemic performance.
This is why AI-first transformation cannot be reduced to tools. Tools are instruments. Agents are actors. Workflows are pathways. But none of them, by themselves, answer the primary question: what is the business becoming?
The answer cannot be “a more automated version of the old org chart.” The answer must be a new anatomy.
The business beneath the departments
Strip away the titles, the software subscriptions, the reporting lines, and the inherited names, and every business performs the same underlying functions. A solo consultant, a restaurant group, a private clinic, a software company, a manufacturer, a law firm, and a logistics network look different at the surface. Underneath, they must solve the same survival problems.
They must detect what is happening. They must retain what matters. They must judge what to do. They must coordinate action. They must produce work. They must exchange value with the outside world. They must enforce constraints. They must improve from experience.
These are not optional capabilities. If a company cannot sense, it is blind. If it cannot remember, it repeats itself. If it cannot decide, it stalls. If it cannot coordinate, it fragments. If it cannot execute, it is imaginary. If it cannot exchange, it has no market. If it cannot govern, it becomes dangerous. If it cannot adapt, it dies.
That is why the AI-first firm should be organized around eight universal functions rather than inherited departments.
Sense — the firm’s receptors. Detect signal from the environment and the internal system.
What is changing, and how do we know?
Remember — the firm’s memory substrate. Preserve context, decisions, outcomes, and lessons.
What has happened, and what should never be lost?
Decide — the firm’s judgment engine. Select a course of action under uncertainty.
What should be done, by whom or what, under which constraints?
Coordinate — the firm’s nervous routing. Align actors, tools, dependencies, and timing.
What needs to move together?
Execute — the firm’s muscle tissue. Produce work in the world.
What output must be completed to a defined standard?
Exchange — the firm’s boundary membrane. Transact value across the firm’s perimeter.
What leaves or enters the business, and under what authority?
Govern — the firm’s nerve and immune system. Enforce rules, permissions, standards, and accountability.
What must be allowed, blocked, escalated, or audited?
Adapt — the firm’s metabolism and healing. Convert experience and failure into improved structure.
What did we learn, and how does the system change?
The table is simple, but the implication is radical. If these are the real functions, then departments are no longer the fundamental units of business design. They are historical containers. Some may remain useful. Some may disappear. Some may be recomposed. But they are no longer sacred.
The AI-first firm does not ask, “How do we add AI to Marketing?” It asks, “How does this business sense the market?” It does not ask, “How do we automate Support?” It asks, “How does pain at the boundary become memory, decision, coordination, execution, governance, and adaptation?” It does not ask, “How do we make Finance more efficient?” It asks, “How does the business govern value, risk, allocation, and exchange?”
Once the firm is seen this way, the org chart begins to look like an old anatomical drawing that mislabeled the body. It named the clothes, not the organs.
Why the organism language is not decoration
The language of anatomy can sound metaphorical until one looks closely at what any autonomous system must do to survive. Once a system must perceive its environment, preserve memory, coordinate specialized components, act through boundaries, reject unsafe action, and improve after failure, it begins to converge on the logic of living systems. This is not because biology is poetic. It is because survival under complexity imposes recurring design constraints.
A business that cannot distinguish signal from noise is blind. A business that cannot preserve context has no memory. A business that cannot constrain action has no immune system. A business that cannot convert failure into future behavior has no metabolism. A business that cannot coordinate differentiated capabilities has no nervous system. These are not decorative comparisons. They are functional requirements.
The department was the industrial answer to specialization. The organ is the AI-first answer to governed capability. The organism is what appears when those organs coordinate through shared memory, boundary rules, feedback, and purpose.
A reader who knows the cybernetics literature will hear an echo here, and it is better named than discovered. Stafford Beer’s Viable System Model, developed from the early 1970s, makes a structurally similar claim: that a viable system is composed of viable systems, each carrying the same regulatory apparatus — operations, coordination, control, intelligence, policy. The eight functions were arrived at independently, from the question of what an AI system needs in order to act inside a business at all, and they are cut differently. But the convergence is real and it supports the argument rather than embarrassing it: constraints old enough to have produced a similar answer in a different medium fifty years ago are precisely the constraints this essay claims are structural rather than fashionable.
Where this departs from Beer is at the top. His policy function asks how does this system remain viable? The question here is what is this system for, and what is it answerable for? Viability is a survival criterion. A thesis is a purpose criterion, and it is falsifiable in a way viability is not.
Membrane → Clear boundary between internal cognition and external action.
Failure mode when missing: The firm acts outside its authority or leaks trust at the perimeter.
Memory → Durable operating context and retained institutional knowledge.
Failure mode when missing: The firm repeats mistakes and cannot compound learning.
Nervous system → Routing, coordination, escalation, and state awareness.
Failure mode when missing: Work stalls, fragments, or depends on human middleware.
Muscle → Execution capacity tied to standards and validation.
Failure mode when missing: The firm produces output without reliable progress.
Immune system → Governance, refusal, audit, and risk containment.
Failure mode when missing: Autonomy turns into exposure.
Metabolism → Conversion of outcomes and failures into improved behavior.
Failure mode when missing: The firm experiences pain without healing.
This is the deeper reason the org chart is insufficient. The org chart can show reporting lines. It cannot tell the firm how to live.
Sense: the firm must perceive reality
Every business begins with sensing. Before strategy, execution, or governance, there is contact with reality. Customers behave. Competitors move. Costs shift. Regulations change. Employees notice patterns. Products break. Prospects ask questions. Complaints cluster. Opportunities appear before they are legible.
In a department-first company, sensing is uneven and fragile. It depends on whoever happens to notice the signal and whether that person has the authority, incentive, vocabulary, and channel to move the signal elsewhere. Sales hears objections that product never sees. Support hears frustration that marketing never reads. Finance sees margin compression after operations has already normalized the behavior that caused it. The founder senses market drift but lacks a structured way to distribute that intuition into the operating system.
An AI-first company cannot afford casual sensing. It needs a deliberate sensory layer. It needs to know where signals originate, how they are classified, which signals deserve attention, which are noise, and what downstream functions should receive them.
Sensing is not merely data collection. A company can collect enormous volumes of data and still perceive very little. Perception requires discrimination. It requires knowing which changes matter. It requires routing. It requires thresholds. It requires a way to turn a weak signal into a structured object that memory, decision, coordination, and execution can use.
This is the first reason departments are insufficient. A department sees the world through its own needs. A sensing function sees the world on behalf of the organism.
Remember: the firm must stop losing itself
Most businesses do not have memory. They have storage.
They have emails, Slack threads, meeting notes, CRM entries, spreadsheets, recordings, dashboards, documents, and the private recollections of people who may or may not still work there. These artifacts contain information, but they do not automatically constitute memory. Memory is not the existence of records. Memory is the ability to retrieve relevant context at the moment it is needed and apply it to present action.
Corporate amnesia is one of the great hidden costs of the department model. A lesson learned in one team does not become available to another. A decision made six months ago loses its rationale. A customer promise survives in one account manager’s mind but not in the operating record. A failed experiment is repeated because its failure never became structured knowledge. A founder explains the company’s principles over and over because the business has no durable way to remember them.
AI makes this problem more urgent. An AI system without shared memory is condemned to behave like a brilliant intern with no past. It may produce impressive local outputs, but it cannot compound. It cannot reliably understand why the company does things the way it does. It cannot distinguish between a new situation and a recurring pattern. It cannot preserve judgment across time.
The AI-first firm therefore requires a memory substrate: a governed, queryable, durable layer in which decisions, outcomes, rationales, standards, failures, assets, constraints, and operating truths can live beyond any individual person or tool. This memory must be structured enough for machines to use and legible enough for humans to trust.
When memory works, the company begins to accumulate itself. Every action becomes a potential lesson. Every failure becomes a future guardrail. Every customer interaction becomes part of the firm’s model of reality. The business no longer scales only by hiring people. It scales by increasing the density and usability of its own memory.
Decide: the firm must make bounded judgments
Decision is where intelligence becomes responsibility.
A business does not merely need recommendations. It needs judgments that account for context, trade-offs, values, constraints, timing, and risk. In the human-limited firm, judgment is distributed through titles and hierarchy. The manager decides this. The director decides that. The executive committee decides what is too consequential for anyone else to decide.
This structure worked because authority had to attach to human accountability. But in an AI-first environment, decision rights must become more explicit. A system cannot be allowed to “decide” simply because it can generate a plausible answer. It must know what kind of decision it is making, what evidence it has, what constraints apply, what level of confidence is required, what consequences may follow, and when a human must be pulled back into the loop.
This is why the decision function is not the same as “having an AI model.” The model may reason, but the business must govern the conditions under which reasoning becomes action. Agentic AI in enterprise settings raises precisely this problem: autonomy must be balanced with ownership, oversight, access controls, auditability, and intervention rights.[3]
A healthy decision function therefore has boundaries. Some decisions can be automated. Some can be proposed but not executed. Some can be made only within thresholds. Some require dual approval. Some must be refused outright. Some must trigger escalation because the system has reached the edge of its authority.
The old org chart hid many of these rules inside people. The AI-first firm must make them explicit. Judgment can become faster, but only if it also becomes more bounded, observable, and accountable.
Coordinate: the firm must move as one system
Coordination is the invisible tax on the modern company.
Much of what managers do is not strategy. It is routing. They move information from one place to another. They clarify who owns what. They remind one team what another team needs. They translate between vocabularies. They chase status. They reconcile calendars. They turn confusion into temporary alignment.
This work is necessary because departmental companies are not naturally synchronized. Each unit has its own priorities, timelines, tools, and definitions of success. Coordination becomes a human overlay placed on top of structural fragmentation.
In an AI-first firm, coordination should become a designed system function. Work should move through defined pathways. Outputs from one capability should become usable inputs for another. Dependencies should be visible. State should be updated. Responsibility should be clear. When something stalls, the system should know where and why. When a decision changes, the affected work should be identified automatically.
This does not mean the future company has no managers. It means management changes shape. The manager is no longer primarily a human packet-switching protocol. The manager becomes an architect of coordination standards, escalation rules, feedback loops, and operating cadence.
Coordination is where the organism metaphor becomes more than decoration. A body does not send a calendar invite from the eye to the hand. Perception, judgment, and action are linked through nervous routing. The business equivalent is not chaos or flatness. It is disciplined interconnection.
Execute: the firm must produce work
Execution is the function most people notice first because it produces visible output. The proposal is drafted. The campaign is launched. The code is written. The invoice is prepared. The report is generated. The product is shipped. The customer receives a response.
This is also why execution is the easiest function to overvalue. Many companies look at AI and see a cheaper output machine. They ask it to write more copy, summarize more documents, answer more tickets, generate more reports, and process more tasks. These are useful gains, but execution without the other functions is blind muscle.
A business can execute quickly and still execute the wrong thing. It can produce beautiful assets from stale memory. It can respond to customers without learning from them. It can automate a broken process. It can multiply work that should have been stopped by governance. It can generate motion without progress.
The AI-first firm must therefore define execution as more than output. Execution requires a definition of done. It requires context. It requires standards. It requires validation. It requires a record of what was attempted, what was completed, what failed, and what should happen next.
This is one of the central shifts from department thinking to function thinking. A department may celebrate throughput. A function must ask whether the work advanced the organism.
Exchange: the firm must cross its boundary safely
Every business has a boundary between itself and the world. Across that boundary move money, promises, products, contracts, data, messages, obligations, and trust. This is the exchange function.
Exchange is more dangerous than internal execution because it touches the outside environment. A draft can be revised internally. A sent contract creates an obligation. A generated recommendation can be debated internally. A published claim can create reputational exposure. A proposed refund can be analyzed internally. An issued refund moves value. A private analysis can be wrong quietly. A customer-facing action can be wrong publicly.
Departmental companies often scatter exchange authority across many teams. Sales can promise. Marketing can publish. Finance can pay. Support can compensate. Legal can approve. Operations can ship. Each department controls part of the boundary, but the customer and the market experience the boundary as one surface.
AI makes the boundary problem sharper. Once systems can act, not merely advise, the firm must know exactly which actions are permitted at the perimeter. What can be sent? What can be signed? What can be refunded? What can be changed in a system of record? What can be said to a customer? What can be purchased? What can be published? What must be reviewed by a human first?
The exchange function is therefore where trust becomes operational. It is not enough for AI to be capable. It must be authorized. The firm must distinguish between internal cognition and external action. It must treat boundary-crossing as a governed event.
Govern: the firm must have a nervous system
Governance is often misunderstood as bureaucracy. In many companies, that misunderstanding is earned. Governance becomes a department of “no,” a compliance ritual, a legal review bottleneck, or an after-the-fact audit.
But governance in an AI-first firm cannot be an external restraint placed on action after the fact. It must be the nervous system running through the organism.
Governance defines what the business is allowed to do, what it refuses to do, who or what has authority, how risk is classified, how exceptions are handled, how decisions are logged, how actions are audited, and how the system responds when uncertainty exceeds its mandate. It is not separate from execution. It is what makes safe execution possible.
The more autonomous a business becomes, the more important governance becomes. This is counterintuitive to those who imagine autonomy as freedom from control. In reality, autonomy without governance is merely unbounded action. The firms that succeed with AI will not be those that remove constraints fastest. They will be those that encode the right constraints deeply enough that more action can be trusted.
This is why the phrase “human in the loop” is not sufficient by itself. The real question is: which loop, at what moment, under what condition, with what authority, and with what record? A human vaguely near the process is not governance. Governance requires designed intervention points, clear escalation, observable reasoning, and enforceable boundaries.
The old company governed primarily through hierarchy. The AI-first company must govern through architecture.
Adapt: the firm must metabolize failure
Every business fails. The difference is what happens next.
In a department-first company, failure often becomes blame, politics, delay, or amnesia. The team explains what happened. A manager promises improvement. A process document may be updated. A meeting is held. Then the organization moves on, often without converting the failure into a durable change in how the system behaves.
This is not because people are careless. It is because the company lacks a metabolic function. It can experience pain without healing. It can identify an error without converting that error into structure.
An AI-first firm must adapt differently. When something fails, the system should ask what signal was missed, what memory was absent, what decision rule was weak, what coordination pathway broke, what execution standard was unclear, what boundary was crossed improperly, or what governance constraint failed to fire. The failure should not merely be recorded. It should become a test, a rule, a routing change, a new memory, a refined threshold, or a stronger refusal condition.
This is what it means for a business to learn. Learning is not the existence of a postmortem. Learning is a change in future behavior.
Adaptation is the function that turns a company from a machine into an organism. A machine can be repaired. An organism heals. A machine can be restarted. An organism remembers injury and grows around it. A machine can be optimized from outside. An organism adjusts from within.
The AI-first company should not aspire merely to run faster. It should aspire to become harder to fool, harder to fragment, harder to destabilize, and harder to make repeat the same mistake.
From boxes to organs
The death of the org chart does not mean the death of structure. This is a crucial point. Many people hear criticism of hierarchy and imagine a future of fluid networks, temporary teams, and total decentralization. That is not the argument.
The AI-first firm needs more structure, not less. But it needs a different kind of structure.
Departments are boxes around people. Organs are governed capabilities. A department is defined by who reports to whom. An organ is defined by what function it performs, what inputs it accepts, what outputs it produces, what memory it can access, what authority it holds, what boundaries constrain it, how its work is validated, and how it coordinates with the rest of the organism.
This distinction is the bridge from metaphor to architecture.
Organized around human roles and reporting lines. becomes Organized around a necessary business function.
Stores knowledge in people, documents, and tools. becomes Operates through shared memory and structured context.
Coordinates through meetings, managers, and status updates. becomes Coordinates through designed pathways and state changes.
Governs through hierarchy and after-the-fact review. becomes Governs through permissions, thresholds, escalation, and auditability.
Improves through training, process updates, and managerial correction. becomes Improves by converting outcomes and failures into revised operating behavior.
This is why the future company will not simply have an “AI Marketing Department” or an “AI Finance Department.” It will have sensing capabilities that understand the market, memory capabilities that preserve context, decision capabilities that evaluate trade-offs, coordination capabilities that route work, execution capabilities that produce outputs, exchange capabilities that cross boundaries, governance capabilities that constrain authority, and adaptation capabilities that improve the whole system.
Some humans will still belong to teams. Some departments may still exist as legal, cultural, or managerial conveniences. But they will no longer be the deepest architecture of the business. They will be human-facing surfaces on top of a functional organism.
The sovereign shift
If the firm becomes an organism, leadership changes.
The leader of a department-first company spends much of their life compensating for fragmentation. They ask for updates. They reconcile stories. They repeat context. They resolve conflicts between local incentives. They force alignment through meetings. They carry the company’s memory in their own head because the system cannot carry it for them.
The leader of an AI-first company must do something different. They must become the sovereign operator of a governed anatomy.
That means setting the principles by which the business acts. It means defining the risk boundaries. It means deciding which forms of autonomy are allowed and which are forbidden. It means ensuring that memory is faithful, governance is real, sensing is broad, execution is validated, and adaptation is continuous. It means designing a company whose intelligence does not depend on any one person being awake, informed, and available at the right moment.
This does not make leadership less human. It makes leadership more consequential. The more a company can execute through systems, the more important it becomes to decide what those systems are for. The leader is no longer merely the person at the top of the chart. The leader becomes the source of coherence.
The sovereign shift is the movement from managing boxes to governing functions. It is the movement from being the router of last resort to being the architect of the firm’s operating anatomy.
The company after the org chart
The org chart will not disappear all at once. It is too useful as a legal, managerial, and social artifact. People will still need managers. Teams will still need names. Accountability will still require structure. The point is not that every rectangle on every chart will vanish.
The point is that the org chart will stop being the primary imagination of the company.
The firms that understand this first will build a different kind of advantage. They will not merely automate tasks. They will reduce context loss. They will remember more. They will coordinate faster. They will govern more precisely. They will learn from failure more durably. They will scale through reusable capability rather than only through headcount. They will be able to reorganize around reality faster than competitors organized around inherited boxes.
A ten-person company with shared memory, governed autonomy, clear boundaries, and closed learning loops may outperform a thousand-person company that bleeds context at every departmental handoff. This is not because the smaller company has more tools. It is because it has a better anatomy.
The industrial firm was built around the limits of human coordination. The AI-first firm must be built around the possibilities and dangers of autonomous coordination. That shift requires more than software. It requires a new theory of what a business is.
One last thing the eight functions do not contain, and should not.
They describe how a firm operates. They are deliberately silent on what for — that silence is what makes them general, and what lets the same eight appear in a manufacturer, a clinic, and a charity. But a regulated system needs something to regulate toward, and a control loop with no setpoint is not a loop. It is motion. The firm’s objective sits above the functions rather than among them, as the thing against which every one of them is judged.
Which produces a condition worth naming, because it is common and rarely noticed: a firm can be highly legible about how it operates and entirely illegible about what it is optimising for. Everyone assumes a shared objective. Nobody has written it precisely enough to arbitrate a real trade-off. Ask three executives what the firm is maximising, over what horizon, against what constraints, and the answers diverge — not from confusion, but because the question has never had to be answered explicitly. AI makes it have to be, because a system reasoning inside the firm cannot infer the objective from the culture the way a twenty-year employee can.
A business is not its org chart. A business is a living pattern of sensing, memory, judgment, coordination, execution, exchange, governance, and adaptation — arranged toward something it has been willing to state.
For 150 years, we mistook the boxes for the body.
The next company will not be managed by an org chart. It will be governed by an anatomy.
Notes
[1] McCallum’s 1855 New York & Erie chart, and the information problem it was built to solve — McKinsey Quarterly, Big data in the age of the telegraph.
[2] On the chart as a designed artifact rather than a reporting diagram — WIRED, The First Org Chart Ever Made Is a Masterpiece of Data Design.
[3] On autonomy requiring ownership, oversight, access control, auditability, and intervention rights — Boston Consulting Group, How Agentic AI Is Transforming Enterprise Platforms.
This essay is the anatomical half of a pair. Its companion, The AI Operability Doctrine, names the property a firm must have before AI can be leveraged at its core, and depends on the eight functions set out here.
Elvin Garcia is the founder of ORGANISMIC, a publisher of owned, legible AI capability. He writes about the recovery of wholeness — in people and in firms.