Lloyd TaylorEvery conversation about AI in the firm is framed as a question of adoption. How fast, how much, which use cases, which risks. The frame is tool adoption — a historically familiar problem with well-developed methodology.
That frame is wrong.
What is happening in competitive knowledge-work domains is not adoption. It is structural transformation of the productive unit — a term this piece will define precisely in a moment. The difference is not semantic. Tool adoption leaves the firm intact and adds capability to it. Structural transformation of the productive unit changes what the firm is.
The Compound Entity
The productive unit of the firm is the entity whose output the firm exists to generate, measure, and manage. For most of the history of the modern firm, that entity was the human individual. The knowledge worker. The skilled practitioner. The answer to “what produces value here?” was: the person. Everything else — tools, processes, systems, capital — was infrastructure serving that unit.
That was the formal account. The actual account of how production happened has always been richer and less visible. Work runs through relationships, informal judgment, workarounds, the person who knows who to call when something is stuck. Much of what makes a process actually function is different from what makes it officially function, and that difference lives in none of the formal documentation. The individual was the unit around which management systems were organized. It was not always the unit through which value was actually produced.
The integration the earlier piece in this series, Endgame, described is not the individual acquiring a tool. It is the emergence of a new productive unit. Call it the compound entity: human cognition and AI-generated output functioning together to produce results that neither could achieve alone. That much is a definition. What makes it a threshold, and not just a description, is the direction the relationship runs. Over time, the human practitioner does not simply absorb the AI component into an existing workflow. The practitioner’s cognitive workflow reorganizes itself around the compound instead.
The compound entity is not defined by its components. It is defined by the threshold it has crossed. Below the threshold, the individual practitioner uses AI as an instrument — the way a surgeon uses a scalpel, the way a lawyer uses a database. Above it, the firm’s training, practice structure, performance expectations, and competitive benchmarks have all reorganized around what the compound produces. The practitioner who tries to operate without the AI component is not just working differently. That practitioner is structurally disadvantaged, and the disadvantage compounds over time.
Frequency of use is not the threshold. Neither is capability. A practitioner can rely heavily on AI and remain the productive unit, so long as the work, the training, the accountability, and the performance standard still assume that the practitioner must be independently capable of producing the relevant output. The compound begins where removing the AI component does not merely reduce efficiency but dismantles the productive architecture the institution has built around the work.
The clearest early indicator of threshold crossing is training program architecture. Below the threshold, the training program develops the independent practitioner who subsequently learns to operate with AI tools. Above it, the program assumes the compound from the first day — teaching practitioners how to function within the compound rather than how to be good practitioners who also happen to use AI. When that redesign happens, the institution is acknowledging something it rarely states outright: that the compound, not the individual, is now the productive unit.
The threshold is becoming visible in parts of diagnostic radiology, where AI-assisted workflows are increasingly embedded in clinical practice. Evidence of the same pattern is emerging in high-volume contract review, discovery-phase litigation, and specific sub-specialties of financial risk modeling, though formal accountability in those domains continues to attach to human practitioners. It is approaching in parts of drug discovery, scientific research, and management consulting. The common feature across these domains is not how much AI gets used. It is institutional dependence on compound performance — the work has begun to be organized around output that the independent practitioner is no longer expected to reproduce alone.
Put plainly, here is what the firm has not yet absorbed: if the compound entity has become the productive unit, then everything the firm uses to manage people — job descriptions, performance reviews, capability development, compensation structures, accountability frameworks, succession planning — was calibrated for a different kind of entity, one that is no longer the unit doing the work. The firm is running instruments built to measure and manage individuals against a new kind of entity those instruments were never designed to see.
The Accountability Gap
The accountability structure of the modern firm, and of the professions that supply it, was built for the individual as the unit of responsible action. Professional licensing certifies the individual’s competence. Malpractice liability attaches to the individual practitioner. Fiduciary duty is borne by named persons. Negligence requires a human agent who made, or failed to make, a decision. When something goes wrong, the accountability structure looks for the individual whose judgment produced the failure.
The compound entity has no address in this structure.
This is not a theoretical gap. It is active — generating institutional policy disputes and unresolved questions right now, in medicine, law, and financial services. A compound entity produces a wrong diagnosis, a flawed contract, an incorrect risk assessment. The accountability question that follows — who is responsible? — runs into a structure the existing frameworks were never designed to navigate.
Play the exchange out. The practitioner says: the AI component generated an output I reviewed, interpreted, and acted on. I am accountable for my judgment. My judgment was that the output was correct. The output was incorrect in ways not visible to review. The infrastructure provider says: the system performed within its specified parameters. The firm says: the practitioner is the licensed professional; the accountability attaches there. The practitioner says: accountable for what, exactly? I approved an output generated by a process I cannot audit. It arrived through reasoning I cannot inspect, drawn from training data whose provenance I do not know.
This is not a bad-faith argument. It is a genuine structural description of what the compound entity is. The practitioner’s contribution and the AI component’s contribution are not cleanly separable in the compound’s output. The output is compound. The accountability structure demands a separable unit. That mismatch is being resolved right now, but not through a comprehensive framework built in advance. It is being resolved incrementally — case by case, through enforcement actions, professional standards, and contract terms. Each resolution recalibrates around what already happened, rather than working out ahead of time what the structure should be.
The gap will close. But how it closes determines the distribution of power and liability in the compound economy. One possible trajectory is expanded organizational responsibility for AI-enabled workflows, analogous in some respects to enterprise-liability doctrines. That shift, if it occurs, would represent a significant change in professional liability and corporate accountability — one that would substantially alter the risk architecture of the firm and its relationship to the professions it employs.
What attribution cannot provide is a return to the prior structure. The compound entity cannot be unmade by attribution. It exists and it produces. The question is only who answers for it.
The Cognitive Supply Chain
Every firm operating compound entities is dependent on infrastructure it does not control. The AI component of the compound runs on computational substrate owned by a small number of providers. Those providers rely on models developed by an even smaller number of organizations. Firms reach all of this through application layers they typically cannot audit and cannot easily replace.
The structural difference is not that the firm now depends on an external technology provider. Firms have always done that. It is that the dependency now enters the productive unit itself. Below the compound threshold, changing infrastructure means changing a tool. Above it, changing infrastructure means changing part of the entity around which the firm’s work has been organized.
AI infrastructure is concentrated across three layers: cloud compute, advanced chips, and frontier-model development. In cloud compute alone, the largest providers account for a substantial majority of global market share. That concentration emerged within a single decade — faster than the regulatory frameworks meant to address it could be built. Put the layers together — compute, cloud, foundation models, application layers — and the result is a distinctive form of productive dependency, one that reaches into the compound entity itself rather than remaining external to it.
In the early twentieth century, firms moved away from generating their own power — on-site steam engines, self-contained generation — toward dependence on the electrical grid. The transition looked like an efficiency gain, and in many respects it was. The structural consequence arrived over time: the firm became dependent on infrastructure it did not control, could not inspect, and could not easily replicate.
AI infrastructure dependency carries higher switching costs, because the infrastructure is not a power source external to the firm’s operations. It is embedded in the cognitive workflow of the compound entities the firm runs. For deeply integrated deployments, switching providers can require rebuilding substantial portions of the workflow, the evaluation stack, the governance artifacts, and the accumulated operational practice built up around the compound. The productivity embedded in the prior integration is hostage to continuing the relationship.
The cognitive infrastructure provider ends up with leverage over the firm at the level of the firm’s productive architecture — a depth of leverage that ordinary supplier dependency does not capture. The firm can replace its legal services provider, its financial services provider, its logistics partner. It cannot easily replace the cognitive infrastructure on which its productive units run, because the cost of switching is not a supplier-relationship cost. It is a rebuild of the firm’s fundamental productive architecture.
The firm’s strategic frameworks were not built to analyze this kind of dependency. In practical terms: the competitive position of the compound-era firm is now a function of two things, not one — what its compound entities can produce, and the terms of its relationship with whoever supplies the infrastructure those entities run on. That second relationship has no standard model yet.
The Plasticity Split
Once the productive unit changes, firms differ in how costly that change is to absorb. Plasticity is not a second mechanism of the transition. It is the variable that determines how much of the prior organization must be dismantled before the firm can operate coherently around the new productive unit.
The earlier piece in this series, Endgame, borrowed a term from biology: phenotypic plasticity. It means the capacity to reorganize rapidly within a single lifetime, without losing functional coherence, when conditions change faster than ordinary adaptive mechanisms can keep up with. Endgame identified this as the survival trait under exactly that kind of perturbation. The translation to business is direct, and the evidence for it is becoming structural rather than anecdotal.
High-plasticity firms share several features. Each one, judged by the standards of the prior optimum, looks like inefficiency.
Decision authority sits close to the point of contact with the environment — with the practitioner, the team, the engagement — rather than concentrated up in the hierarchy.
Outcomes get specified, not procedures. The procedure that produced value before the perturbation may now be precisely wrong for the current environment, so locking in the procedure would lock in the wrong answer.
Redundancy is maintained on purpose: overlapping capabilities, parallel approaches, generalist capacity sitting alongside specialist depth.
Internal inconsistency is tolerated at a level that more refined organizations have long since eliminated. Consistency assumes that what worked before will keep working — and that is exactly the assumption the perturbation is violating.
Some professional partnerships, before bureaucratization sets in, exhibit this structure. So do platform architectures that route human judgment through distributed networks rather than encoding judgment into fixed process. So do scientific research organizations, where the productive unit has always been the compound of human and instrument, and reorganizing around a new instrument is part of the operational expectation rather than a disruption to it. These look different from each other on the surface, but they share the same underlying features: authority at the edge, outcome over procedure, maintained redundancy, tolerance for inconsistency.
The forms facing the highest reorganization cost are those whose operating models are most tightly interwoven with regulation, credentialing, legacy systems, and formal accountability. Large financial institutions with multi-year approval cycles for operational change. Healthcare systems with credentialing architectures designed for a world in which the practitioner was the unit. Legal firms with partnership structures and precedent-based practice models that make rapid reorganization structurally costly. Educational institutions whose accreditation requirements were built for the independent-practitioner curriculum. These are not unprepared organizations. They are exquisitely functional organizations, built for conditions that are reorganizing around them.
The biological evidence is uncomfortable here, because it offers no prescription.
The organism that survives rapid perturbation is not the one best adapted to the prior environment. It is the one with the highest capacity for reorganization.
The most precisely calibrated organism carries its calibration as a liability when conditions change.
There is no correction available that does not begin by dismantling the optimization. The firm that built its advantage through decades of process refinement is running into that same structure now.
The Management Problem
Management theory rests on a foundational assumption that has not been seriously questioned since the scientific management movement of the early twentieth century: the productive unit is observable. You can watch the practitioner work. You can audit the process. You can attribute output to identifiable decisions and identifiable actors. The entire edifice of performance management rests on this assumption — measurement, evaluation, diagnosis, improvement, all of it.
The compound entity has a component whose causal operation is only partially observable in this sense.
The AI component generally does not produce an auditable account of the reasoning that generated its output. Firms can observe inputs, outputs, traces, and operational logs, but they cannot usually reconstruct the causal process by which a model arrived at a specific result. When the compound entity performs well, what combination of human judgment and AI generation produced the result? When it performs badly, where in the process did the failure occur? The compound entity’s outputs are compound in origin. Management frameworks demand separable attribution. The mismatch is not a data problem. It will not be solved by more metrics or better dashboards. It is architectural.
The specific management functions that break in the compound organization can be named one at a time.
Performance evaluation breaks first. Assessing compound output as if it were individual performance does two kinds of damage at once. It over-credits the practitioner when the AI component is carrying most of the cognitive load. And it under-credits the practitioner when the real skill is knowing how to operate the compound well — a skill that is real, demanding, and invisible to any measurement based on output alone.
Capability development breaks next. Training a practitioner to function well within the compound requires a theory of exactly what the human component specifically contributes. Building that theory requires being able to see the compound’s internal operation — and that visibility is precisely what the compound structurally withholds.
Failure diagnosis breaks the same way. When the compound produces an error, preventing it from recurring requires locating where in the process the failure occurred. That requires auditing a process that can only be partially reconstructed.
Succession breaks last, and least visibly. When an experienced compound practitioner departs, individual expertise walks out the door, certainly. But so does something harder to name: the practitioner’s trained relationship with specific AI systems, the workflow patterns built up through years of compound operation, the judgment calibration developed through sustained engagement with AI outputs. None of it transfers through conventional succession mechanisms, because none of it was ever written down anywhere a successor could read it.
What has not yet cohered is a management framework that begins with the human-AI compound itself as the productive unit. The literature on AI in the firm is largely about tool adoption: change management, displacement, retraining, accountability frameworks. These are real and useful contributions. None of them addresses the management of an entity whose productive unit is a compound of human cognition and AI generation. That entity’s performance cannot be fully explained by either component alone. And the instrument management would need, in order to measure that entity, cannot fully inspect what it is measuring.
The craft-to-industrial transition offers a useful analogy. That transformation required an entirely new management theory, because the entity being managed had become structurally new. The old craft-shop frameworks had to be abandoned before the new ones could be built. The compound organization is a new kind of entity in exactly this sense. A management theory that treats the compound itself as the primary productive unit has not yet cohered. What exists instead is the prior theory, applied to an entity it was never designed for. It produces readings. Those readings measure something — just not the thing that actually determines competitive outcome.
The firm cannot see this from where it is managing.
This is not a failure of intelligence or attention. It is structural. The firm has always struggled to see how work actually gets done — the formal account has always been an imperfect instrument for the richer, informal reality. The instruments through which the firm assesses its own performance are themselves part of the firm’s cognitive architecture. That architecture is increasingly run through AI-integrated processes. The assessment the firm performs on its compound entities is itself a compound process. What the compound entity adds is not a new kind of invisibility. It is a deeper layer on an old one: technical opacity now sitting on top of the social opacity that was already there. The management system is being integrated into the very thing it is trying to manage.
Hold that for a moment, because it is the turn the whole section rests on.
The observer is not watching the transformation from outside. It is running on the same substrate the transformation is reorganizing.
In plain terms: the tools the firm would use to study its own transformation are themselves being transformed by the same process. There is no clean vantage point left outside it to study it from.
If the compound-entity account holds, then some firms will do the work of reorganizing around it as the actual productive unit — rebuilding accountability structure, management theory, training architecture, and power analysis around what the compound actually is. Those firms will hold a structural advantage over the ones still running individual-practitioner frameworks against a reality that no longer fits them. And that advantage will not have come from solving a strategic problem. It will have come from correctly identifying what kind of entity the firm had already become.
The difficulty is that firms crossing the threshold must identify the change through instruments built for the entity being displaced.
None of this applies merely because a practitioner uses AI, even heavily. The argument begins only where the institution has reorganized work, training, and expected performance around output the practitioner is no longer expected to produce independently.
Where the compound threshold has been crossed, the firm’s management instruments remain calibrated for an entity that is no longer the productive unit. What they are pointing at now — compound, integrated, dependent, unobservable in its internal operation — is something those instruments were not designed to see.
References
- American Bar Association, Formal Opinion 512: Generative Artificial Intelligence Tools (ABA, 2024)
- Chandler, Alfred D., The Visible Hand: The Managerial Revolution in American Business (Harvard University Press, 1977)
- EU AI Act, Regulation (EU) 2024/1689 (European Parliament and Council of the European Union, 2024)
- NIST, Artificial Intelligence Risk Management Framework 1.0 (National Institute of Standards and Technology, 2023)
- OECD, Competition in Artificial Intelligence Infrastructure (OECD, 2025)
- Stanford HAI, AI Index Report 2025 (Stanford University, 2025)
- Taylor, Frederick Winslow, The Principles of Scientific Management (Harper & Brothers, 1911)
Copyright © 2026 Lloyd W. Taylor