HR Is Being Asked to Redesign Everyone's Work. It Hasn't Redesigned Its Own.

A CHRO said something to me a few months ago that I haven't been able to shake.

"I signed up to be the Chief Human Resources Officer. Not the Chief Work Officer. I never asked to become an expert on how work gets done, or what should be a person and what should be a machine."

She wasn't complaining. She was naming something most of her peers feel and few will say out loud: the job changed underneath her, and nobody her sent the email.

I think we all know what happened.

Work started changing. Not just who does the work, but what does the work – and when you should use a person versus an agent versus an automation versus some hybrid of the three.

The moment that question got real, the business turned to HR and said: “Tell us what this means for our processes. Our roles. Our skills. Our headcount. Our workforce plan. Our org design. Give us a point of view.”

Those are new asks. They are not the asks HR was built for.

That doesn't mean HR now owns the work definitions for every function in the business. The business must still own the work. Technology must provide insights into what is technically possible. Finance must understand the economics and value.

But someone must own the architecture and orchestration that connects those decisions to processes, roles, skills, capacity, cost, and organizational design.

That someone needs to be HR.

The function running the transformation has yet to transform itself

At TalentNeuron, we've spent the last few years telling the market and our clients a relatively clean story, and it's the right one.

Start with the required business outcomes. Define what work and work outcomes are required to achieve the business outcomes. Decompose the work into processes and tasks. Decide what humans, agents, and automation should each do. Reassemble that work into roles. Determine the skills and capacity required. Then redesign the workforce and organization around it.

Business outcomes → processes and tasks → human/machine allocation → roles → skills and capacity → workforce → organization structure.

Increasingly, this story is being told by competitors, analysts, influencers, and HR leaders. Industry thought leaders have been arguing for this kind of transformation effort across every business function.

Finance. Operations. Sales. Engineering.

Yet HR hasn't run the transformation on itself.  

At most orgs, it’s still the same recruiting workflow - absent maybe some aqentic sourcing and screening assists from in-built tech in the ATS or CRM. Same performance cycle. Same shared-services model. Same HRBP role. Same org chart it had before agents could do meaningful portions of the work.

It's not clear to me why HR hasn't embraced this more fully inside its own walls. Maybe the day job hasn't let up long enough. Maybe the mandate never felt official. Maybe the function has been so busy helping everyone else navigate the change that it hasn't had the capacity to apply the same thinking inward.

Whatever the root cause, the window won't stay open forever.

If HR doesn't take this work, someone else will. And the function will inherit a design it had no hand in shaping.

The data suggests the delay is getting expensive. i4cp finds that 83% of large-company leaders say AI is already reshaping what they expect from HR, yet 46% say AI hasn't changed HR's strategic impact at all, and only 3% say it has improved it meaningfully. More than half of HR functions still haven't moved past isolated pilots.

McKinsey puts the challenge more bluntly: a people function that hasn't reimagined its own work has limited standing to ask everyone else to reimagine theirs.

HR has to go first. Start by running the transformation on yourself.

The reframe is almost embarrassingly simple.

The same transformation model HR is being asked to bring to the business is the transformation model HR needs to run on itself.

But it doesn't start with the org chart. It starts with the work.

Pick a consequential outcome or workflow. Decompose it into the processes, decisions, handoffs, exceptions, and tasks that produce the result. Then ask, task by task, and process by process: “What should remain human-led? What should be AI-augmented? What can become agent-led with human oversight? What can be fully automated? And what should simply disappear?”

Then – and only then – reassemble the work:

• What roles are required now?

• How do existing roles change?

• What new skills are needed?

• What capacity is released?

• What new governance is required?

• And if the work and workforce change enough, what should happen to the structure?

This matters because the goal isn't to sprinkle AI across the existing operating model.

It is to redesign the operating model around what is now possible.

The recruiter may become the orchestrator of a multi-agent sourcing and screening system. The HRBP may become a work-design advisor rather than a policy desk. Onboarding may shift from a sequence of human handoffs to a human-plus-agent experience. Workforce planning may move from a quarterly exercise to a continuously updated decision system.

Those changes create new skill requirements, new measures of performance, new governance needs, and eventually new organizational structures.

That is not a reskilling program bolted onto the side of the org.

It's the same structural transformation HR is prescribing to everyone else, pointed inward.

You're not behind. The job changed.

If you're an HR leader reading this and feeling the gap, you're not behind. You're normal.

Nobody hired most of today's CHROs to be experts in agent orchestration, task decomposition, workflow redesign, or the economics of human-machine work allocation. That expertise wasn't in the job description as recently as 12 months ago.

The role expanded faster than our collective mental model of it.

The CHRO who told me she never signed up to be Chief Work Officer is right.

She didn't sign up for it. The work signed her up anyway.

The leaders pulling ahead right now aren't necessarily the ones with the best tools. They're the ones who stopped waiting for the mandate to feel comfortable and started treating their own function as the proving ground. And let me assure that while the vast majority of all businesses and CHROs are still at the starting line, there are some orgs who are already pulling away due to their early investments. Every single one of them share one thing in common - they didn't wait for clarity - they achieved clarity and purpose by meaningfully engaging in the work.

HR shouldn't merely be the function that explains the future of work to everyone else.

It should become the enterprise's laboratory for learning how that future actually works.

Be your own test case.

You want to own the conversation?  Start with your own team.

Use HR as the pilot for the transformation you're asking the enterprise to undertake.

But you should run two cases at once, one that establishes your team as capable and invested in transformation work, and another to build durable capability to support the business for years to come.

One is a transformation case. The other is an infrastructure case.

One proves the model.

The other makes it scalable.

The transformation case

Take a high-volume, consequential process you own: sourcing, screening, employee case management, onboarding, performance reviews...

Map the work as it actually happens today – not as the process diagram says it happens.

Identify the tasks. The decisions. The handoffs. The exceptions. The systems. The bottlenecks. The workarounds.

Then rebuild the workflow around the optimal combination of humans, agents, and automation.

Not to shave a few hours off cycle time.

To learn, inside your own function, what this transformation actually takes:

• Where does the work break?

• Where do humans still matter most?

• Where does AI create leverage—and where does it create risk?

• What governance do you wish you'd stood up first?

• What new skills emerge?

• What happens when your own people's roles change underneath them while you're asking the business to accept exactly that?

• And what happens to cost, capacity, speed, quality, experience, and risk?

Do this and you earn the right to be at the front of the room.

But don't stop at the pilot.

Codify what you learned into a repeatable method for decomposing processes, allocating work across humans and technology, redesigning roles, identifying skills implications, modeling economics, managing risk, and leading the change.

The goal isn't one successful AI implementation.

The goal is to build the organizational muscle required to do this repeatedly.

The infrastructure case

At the same time, you should stand up a Work Architecture capability with direct CHRO sponsorship – ideally anchored in Strategic Workforce Planning or People Strategy, but designed from the beginning as a cross-functional enterprise capability.

The core remit of this team is to help the organization continuously reimagine work at the intersection of business outcomes, process, humans, technology, AI, capability, and cost.

It should not be an HR-only team.

The business must own the outcomes and the work. Technology needs to understand what is possible. Finance needs ownership of the economics. HR needs to connect those choices to roles, skills, capacity, workforce strategy, and organization design.

A small permanent core team can own the methodology, work ontology, governance, tooling, and enterprise standards. Finance, Technology, HRBPs, and business leaders can operate as a federated network around specific transformation priorities.

That team needs to also own something no one owns today:

The canonical definition of work itself.

The shared language connecting business outcomes, processes, tasks, roles, and skills – the foundation the rest of HR, and eventually the enterprise, plans against.

Once you’ve done this work internally, you can walk into any other team with real-world, lived experience in the thing you're asking them to do. You’ll be able to share war stories, lessons learned, emerging best practices…

That's what turns HR from adviser into a walking, talking proof point of what's possible.

Moderna offers one version of what this can look like. By bringing HR and technology under a single leader, the company explicitly connected workforce design with technology design – asking how tasks, information, and decisions should flow across people and technology.

You don't need to copy the reporting structure.

But you do need to institutionalize the question:

What work needs to be done, and what is the optimal combination of humans, agents, automation, and systems to do it?

The two critical set pieces

Once HR starts doing this work repeatedly, the importance of that infrastructure project becomes evident fast.

Every transformation starts by reconstructing the same basic facts:

• What is this role?

• What work does it actually contain?

• What processes is it part of?

• What tasks are being performed?

• What skills does the work require?

• How does that compare to the external market?

• How is the work changing?

• What can technology now do that it couldn't do a year ago?

Without a shared foundation, every redesign starts from scratch.  What’s required are two investments:

The first is that shared organizational layer you built out in your infrastructure project – the Work Architecture team – an “always-on” capability with the remit to define the facts above in the first place and continuously evolve it as the nature of work changes.

The second is a shared semantic layer: a common definition of what a process, role, task, and skill actually are. Once you have a shared definition of the “facts” of the work architecture – you need to propagate this understanding into every system and decision-matrix linked to work.

Most HR functions are missing both set pieces, and the downstream impacts are debilitating when it comes to work and workforce transformation work.

Their own systems can't agree, and none of them speak the same language as the labor market outside. The HRIS has one representation of work. The learning platform has another. The talent marketplace has a third. Recruiting has a fourth. External labor-market data speaks an entirely different language.

Without a shared semantic layer, every transformation begins with reconciliation.

Every comparison requires translation.

Every plan is built on shifting definitions.

And every AI agent is being asked to reason over a different representation of reality.

This is where Work Architecture becomes more than job architecture or a skills framework.

It becomes the enterprise's canonical representation of work – a shared model connecting business outcomes, processes, tasks, roles, and skills that every HR application, every AI agent, every finance model, and every business planning process can reason over.

But the foundation alone is not enough.

You need a team to build it, own it, and maintain it. A static model of work starts decaying the moment it is published. That's why every Job Architecture project that ends in an Excel spreadsheet is doomed from the start.

Definitions drift. Processes change. Technology matures. Skills evolve. Agents gain capabilities. Jobs absorb new tasks and shed old ones. A taxonomy that was right at launch can be stale within quarters.

And that’s where the “Work Architecture” team earns it’s keep over time.

One piece is the map.

The other are the cartographers who draw it – and never stop redrawing it.

Build the map without the mapmakers, and the map rots over time.

Assign mapmakers to make decisions without the map, and they argue in circles.

HR needs both. And right now, most functions have neither.

Getting started...

Not with a three-year transformation program.

Not with a new HR org chart.

And probably not with another technology purchase.

Start with four moves.

Prove it. Redesign one meaningful HR workflow end to end – not by adding AI to the existing process, but by rebuilding the work around the optimal combination of humans, agents, automation, and systems.

Codify it. Turn what you learn into a repeatable methodology for process decomposition, task allocation, role redesign, skills implications, economics, governance, risk, and change.

Institutionalize it. Create a permanent Work Architecture capability with CHRO sponsorship and a federated operating model across HR, Technology, Finance, and the business.

Build the foundation. Create and continuously maintain the canonical representation of work that connects business outcomes, processes, tasks, roles, and skills to external market data and evolving technology capability.

Prove the model. Codify the method. Institutionalize the capability. Build the infrastructure.

Then do it again.

And again.

Because this isn't a one-time transformation.

The technology will keep moving.

The work will keep changing.

The organization will have to keep adapting with it.  This is the new normal and why it’s so important to build this muscle now.

So, here's the question I'd put to every CHRO right now.

"If the business walked into your function tomorrow and ran the same transformation audit you're increasingly being asked to run on them:

• New work

• New processes

• New human-machine allocation

• New roles

• New skills

• New workforce

• New structure

How would HR score?

If the honest answer is "not well," then it’s time to get moving. This period of transformation is too impactful to business operations and long-term financial health to go unmanaged. HR is the right point of orchestration, but it’s not the only option.

We’ve already seen these initiatives led by teams outside of HR – Operations, IT, CIO, Office of Business Transformation, CEO special projects…  At least 25% of the projects we’re doing with clients are started outside of HR.  

And then the bigger, scarier question is “If you are not orchestrating the implications of automation into the workforce and not owning the related workforce strategy and planning, what exactly do you own?”  Compliance related stuff, your Workday or SAP instance, a bunch of disconnected Talent Management tech?  

Absent ownership of the upstream understanding of the work and the workforce, the only work left is effectively execution and compliance.  

Which leads to the next and final scary question: “If all the heavy lifting on strategy is done outside of HR, why wouldn't we disintermediate what’s left into functional leads – which already exist in most orgs – and effectively eliminate the CHRO role?”

I’m not saying I want this to happen. I think CHRO’s should be driving this transformation bus, but there is a real risk that if they don’t hop into the driver’s seat soon, someone else will, and then they might find that they aren’t on the bus at all.