Move Over HCM

Every enterprise keeps one place where it goes to become legible to itself. Not the strategy deck and not the org design workshop, but the human capital management platform — the system that decides what, where, and why a person is inside the organization. And that system, in almost every enterprise running today, is built on a template that is older than any living person.

The template has a name in the industry: position management, sometimes called org management. Underneath it sits a three-object model. There is the job, an abstract classification. The position, a specific instance of the job. And the person, the temporary occupant of that instance, or box. The job is the engineering drawing. The position is the place on the line. The person is the part that fills it.

This is not a neutral piece of data architecture. It is a philosophy of work, encoded and shipped as software, and the philosophy is the assembly line. The name of the philosophy is bureaucracy.

Conventional wisdom already left this behind

The strange part is that few defend the assembly line paradigm of work anymore. The case for fluid, non-hierarchical, adaptive organization is not a frontier idea waiting to be proven. It is decades old and thoroughly mainstream.

Warren Bennis named the alternative in 1968, in The Temporary Society: the adhocracy, an organization of temporary teams that form around a problem and dissolve when it is solved. Two years later Alvin Toffler put the word into general circulation in Future Shock and predicted, plainly, that adhocracies would displace bureaucracies as the environment accelerated. That was more than half a century ago. Every serious account of organization since has agreed on the direction of travel: away from the fixed slot, toward the fluid arrangement. Virtually every thought leader in the AI era echoes this point.

And yet the systems enterprises actually run their people through never moved. HCM platforms chained themselves to the bureaucratic paradigm of position management and stayed there, because the bureaucratic paradigm is what the software was built to administer. And because society at large is slower to make the transition.

The industrial compromise, digitized

I argued in The AI Enterprise that this is the “industrial compromise” made durable. At around the turn of the twentieth century, the Industrial Revolution struck a bargain with its predecessor, craft production: give up the whole in exchange for scale. The craftsman who once held an entire product in mind was narrowed into an operator of one step, and the meaning of the work migrated out of the work itself and into the conditions around it — the wage, the title, the security of the slot.

Position management is the industrial bargain encoded in the people system of record. Its entire purpose is to make people interchangeable — to define a slot precisely enough that qualified persons can be identified, recruited, and deployed so that the machine keeps running. That was a rational answer to a real constraint. When expertise was scarce and coordination at scale was hard, interchangeability was how large organizations stayed consistent, fair, and auditable. The platform did not invent the logic. It simply applied it.

The unit of work just changed

What breaks the model is not a better philosophy. It is a change in what actually performs the work.

The Theory A manifesto describes this as the emergence of human-machine dyads: work increasingly done by a person and a machine acting together against an outcome, adapting as conditions change. Position management has no object for that. It can describe a job, a box, and an occupant. It cannot describe a person teamed with an agent, because in the three-object world the machine is not a member of the organization. It is a tool assigned to a slot that still assumes a single human part.

“When the thing doing the work no longer fits the only shapes your system of record can hold, the record stops describing reality.”

When the thing doing the work no longer fits the only shapes your system of record can hold, the record stops describing reality. It starts describing a fiction the organization agrees to maintain. It makes the organization legible through a lens that is really only useful for regulatory governance.

The prognosis is bifurcation, not reinvention

Here is where the practical prediction diverges from the tidy one. The tidy prediction is that HCM platforms will be reinvented — that the slot gives way to the outcome, the position to the engagement, and the software follows. It will, eventually. But it will not happen soon, and the reason was named a century ago.

In 1922, William Ogburn coined it cultural lag. Material culture — technology, tools, capability — advances quickly. Adaptive culture — values, norms, and above all law — changes slowly, and the gap between them is a period of maladjustment that a society has to live through. Organizations are societies. The technology of the human-machine dyad is arriving now. The adaptive apparatus around it is not.

Labor law alone is a century of bureaucratic management encoded into statute. Imagine trying to uncover or defend discrimination without documentation of stable jobs and positions. Classification, headcount, the employer-employee relationship, the very legal existence of “the position” — these are load-bearing fictions of the industrial era, and they will not be rewritten to accommodate the new model in a product cycle. They will take years.

So the near-term outcome is not one reinvented HCM. It is two. One will manage the employee. The other will manage the worker. Organizations will maintain one system of record to satisfy the regulator — positions, headcount, the legal shape of the job, everything compliance and labor law still require to be true. And they will maintain a second to reflect what is actually happening: humans and machines teamed against outcomes, forming and dissolving as the work demands. For some period of time, both run at once.

The org chart will not be reinvented on a vendor’s roadmap. It will be quietly duplicated. The question that follows is the one worth sitting with: when your two systems disagree — and they will, constantly — which one will you actually manage by?

If human resources relegates itself to managing the employee side of the equation and not the worker side, it is setting itself up for irrelevance.