The Next Great HR System Won't Be a System of Record

I think we're watching a new software category take shape. I've been part of a few of these, notably software simulation and social learning in ed tech, then Talent Management during my years at Taleo. What I remember most is how none of them really announced themselves. Individual inflection points threw off signals, but every early success came wrapped in uncertainty, confusion, and fair questions about whether the thing would last.

Then the signals started accelerating and building on each other. New roles appeared. Existing conferences got bigger, and new conferences emerged. Analysts built research categories around problems that used to live across disparate markets. Companies with nothing in common started investing in suspiciously similar capabilities. At some point, that collection of isolated trends stopped looking isolated and started looking structural. It went from “one-off moments” to something that felt more like “momentum and inevitability.”

We're close to that point with Strategic Workforce Planning, Work Intelligence and Workforce Redesign. Consider the signal data:

• According to our own data, the number of people carrying SWP leadership titles is up roughly 23% year over year.
• According to the Workforce Planning Institute, attendance at their dedicated SWP events has more than doubled in three years, and separately a new SWP conference launched last year under a new organizer.
• Gartner published its first Market Guide for Workforce Planning Technologies, alongside a new enterprise SWP framework that explicitly connects strategy, work, technology and talent.
• Everest Group created an Innovation Watch around Work Intelligence and Workforce Redesign, and described the market as being at an inflection point.

Any one of those signals on its own is noise. Together they're harder to dismiss.

The market signals tell one story. Enterprise buying behavior tells a better one. Across our own SWP customer base, the organizations investing deeply right now include two global airlines, a leading global pharmaceutical company, three of the world's largest manufacturers, three major reinsurers, two global technology giants, four leading energy companies, two of the world's largest food and confectionery businesses, a major fintech, and one of the world's leading consultancies. Just to name a small, but representative sample.

I'm not listing them to brag, though if you've been wondering whether our move from global LMI leader to LMI, SWP and Work Architecture is real, then hopefully that list settles it.

The point here is the breadth. If this were a response to one industry's labor shortage or specific workforce / AI challenges, demand would cluster. If it were an HR technology refresh cycle, the use cases would be narrow and repetitive. Neither is happening. Airlines, manufacturers, pharma, energy, technology and financial institutions have almost nothing in common in how they organize labor, and they are arriving at the same question anyway:

How do we continuously understand how work is changing, and turn that understanding into decisions about the workforce we need next?

Most HR technology was never built to answer that.

From “systems of record” to “systems of planning”

For decades the center of gravity in enterprise HR technology has been the system of record: who works here, what job they're in, what they're paid, who they report to, what benefits they get, how they performed. Those systems are essential, and they aren't going anywhere. But the questions that now determine whether a strategy is executable sit one level above them:

• What capability do we actually have today?
• What work will the business need to be doing five years from now?
• How are AI and automation changing that work already?
• Which tasks stay human, which get automated, which become hybrid?
• What skills will the remaining work require, and where should that capability sit?
• Do we build it, buy it, borrow it, or bot it?
• What does each of those choices cost, and what happens to the operating model if we choose wrong?
• And once we decide all of this, how do those decisions propagate into jobs, hiring, learning, pay, org design and deployment?

None of those are “system of record” questions. They're “system of planning” questions. That's where the next layer of the stack is being built.

AI is turning work into a moving target

AI makes this urgent because it’s forcing a continuous redesign of work itself and how that work is completed. For most of HR technology's history the job was a stable unit. You could build an architecture, attach skills to it, put people in it, and refresh the structure every few years. That assumption is getting harder to defend.

AI doesn't transform organizations at the job level. It changes tasks. Some disappear, some accelerate, some become more valuable, some migrate to a different role entirely, and new combinations of human and machine work show up where no job description exists. The model of work has to become as dynamic as the work.

Which is why I've argued that Work Architecture needs to behave like enterprise master data: a living representation of outcomes, processes, roles, tasks, skills, technology and capacity that changes as the business changes. Without it, organizations struggle to deploy AI well, because they have no shared account of the work as it is or as it should become. And the ones that deploy anyway still can't redesign around it, for exactly the same reason. Automation without a semantic model of work produces efficiency in places nobody planned for.

If your organization doesn't have that layer, you're not behind. Almost nobody does. It has never been anyone's job to own it, no vendor has sold it as a category, and the closest thing most companies have is a job architecture built for compensation — which was never designed to carry this weight and can't be stretched to fit it.

Planning becomes the connective tissue

This is also why workforce planning is moving away from headcount and financial modeling toward scenario-driven, multi-year frameworks that define an operating envelope rather than a single plan. Traditional workforce planning was an annual event: strategy comes in, headcount gets modeled off current state and existing trendlines, supply and demand gaps get calculated from those projections, a plan and a budget come out. Done.

That model was always thin, but it held while the world moved slowly enough for last year to predict next year. It makes no sense when technology, skills, labor markets and the work itself all change inside the planning cycle.

What's replacing it looks less like a process and more like an orchestration discipline. It senses change in the business and in the external labor market. It reads how work is changing. It models alternative futures, tests the economics and feasibility of each, and then pushes the resulting decisions into the systems that actually execute them: talent acquisition, learning, internal mobility, compensation, org design, automation, finance and technology.

I've stopped thinking about SWP as another HR process. It's becoming part of the planning infrastructure of the enterprise, and it belongs in the same conversation as financial planning and capacity planning.

The category may be bigger than SWP

This may be the most important part. I'm not sure the category being created is Strategic Workforce Planning at all.

SWP is part of it. So are Work Intelligence, Skills Intelligence, Labor Market Intelligence, Work Architecture and organizational modeling. But enterprises aren't buying those things because they want more HR capabilities. They're assembling an answer to a much larger question: how does an organization continuously redesign the combination of people, skills, work, technology and AI required to execute its strategy?

That problem barely existed in this form five years ago. Today it shows up in boardrooms across every industry, and in a vendor field that has gotten genuinely confusing. Gartner says it is tracking more than 90 technology solutions claiming to do SWP. Ninety vendors is not a market. It's a signal that a real problem has outgrown the categories available to describe it. And the infrastructure required to solve it doesn't fit comfortably inside the old HR technology categories, whatever the suite vendors say to the contrary.

In my experience, this is how categories actually begin. Not because a vendor invents a clever name, but because enough companies hit the same unsolved problem at the same time and the existing tools stop being sufficient.

The systems of record will remain. The talent management systems will remain. But another layer is forming above them, built not to administer the workforce you have, but to continuously model, redesign and orchestrate the workforce you'll need.

The center of gravity is moving from recording the workforce to planning the work. And we're much closer to the beginning of that shift than the end.

So a question for anyone building this inside their own organization: who owns this layer at your company today? Have you created a new “normal” for all of this?  In most of the client conversations I’ve had, it seems like this is all very much in flux with emerging leadership coming from all corners of the business, not just HR.