SWP, Work Architecture & Job Redesign, and the New HR Organization

Houston, we have a problem.

One of the less noisy but deeply problematic challenges we're going to face as an industry over the next 12 months has nothing to do with technology. It's an org chart problem. And it's hiding in plain sight inside almost every large HR function I walk into.

Here's how I find it. I ask three questions.

Who owns your job architecture? The answer almost always: Comp & Ben.

Who owns your skills framework? Usually L&D, whoever runs the Talent Marketplace, or Talent Management.

Who owns your task framework? And this is where the room goes quiet. The honest answer is some version of no one - or maybe the business, loosely, and only because tasks eventually find their way back into job descriptions that are two or three years out of date.

Sit with that for a second. Roles live in one place. Skills live in another. Tasks live nowhere. Three things that are completely interdependent - that only create value when they work together - are split across three teams who rarely sit in the same meeting.

This has been true for the whole history of the HR function. And for most of that time, it was a tolerable kind of messy. It isn't anymore.

Automation is the reason. Not AI narrowly, but the full spectrum of it: GenAI, business process automation, industrial automation. Automation operates at the task level. It augments some tasks, eliminates others, and leaves a role looking nothing like the one you wrote a job description for. When the tasks change, the role changes. When the role changes, the workforce has to change. When the workforce changes, the structure that holds it has to change too.

Now look back at how the work is owned. The single input that drives all of this - task-level automation exposure - sits in the one box on the org chart that nobody actually owns. So when the question finally lands on someone's desk: which of our roles are most exposed, and what do we do about it? There's no team to catch it. The analysis falls between the cracks, and the redesign work that should follow never starts.

That's the blocker. Any HR organization that hasn't reorganized around this is going to feel it the moment automation pressure becomes real - and for most of you, it already is.

What I think the answer looks like

I've started telling clients that the next phase of HR maturity requires two new horizontal layers reporting up through the CHRO - layers that cut across the traditional silos rather than living inside any one of them.

One: Work Architecture. Not job architecture. Work architecture - the connective tissue that defines how work is organized, performed, and evolved across the enterprise, and that holds roles, tasks, skills, capabilities, and structures together as a single interdependent system. I've come to think of it as a kind of Rosetta stone: the layer that lets your HRIS, your LMS, your ATS, your internal talent marketplace, and your view of the external labor market all speak the same language about roles, skills, and tasks. Without it, none of these systems speak the same language and comparative analysis becomes impossible.

Critically, this same team should own work redesign - job and role redesign especially. You can't separate the people who maintain the map of work from the people who redraw it. They're the same discipline.

Two: Strategic Workforce Planning. This is the layer that takes the intelligence work architecture produces: demand drivers, automation exposure, skill gaps, and turns all of that into a forward-looking plan the business can actually act on. SWP is how you go from the disruption and chaos of "the work is changing" to a data-led strategy that confident asserts "here's the talent we'll need, here's where we'll be short, and here's our build / buy / borrow / bot strategy to close the gap." It's the bridge from insight to plan to execution. Without it, work architecture is a beautiful map with no destination.

Neither of these belongs to Comp & Ben, or L&D, or any single existing team. They span all of HR, and they need to be staffed that way.

A few things I've learned about making this work

These two layers are led by HR - but they don't succeed inside HR alone. The teams that get this right run matrixed strike teams, with permanent seats for Finance and IT, and ad hoc representation from the functional business leaders whose work is being redesigned. Automation exposure is a finance question as much as a talent question. Actualizing automation potential into automation realization is an IT investment question. And nobody knows the texture of the actual work better than the leaders who own it. This problem is genuinely cross-functional, and the org design has to reflect that from day one.

I work with very large, very sophisticated global organizations and a vanishingly small number of them have made this shift. And only a slightly larger cohort is even thinking this way. So if you're reading this thinking we're nowhere close to this - you're not behind, you're normal.

But "normal" is exactly the point. "Normal" is your opportunity window. The organizations that move first build a real, durable advantage. When you can see how automation can reshape a role, plan the workforce around it, and then redesign both the work and the org structures to match - and do all of it from a shared foundation rather than three disconnected ones - you realign your talent faster and more accurately than competitors still passing the question between teams. In a labor market changing this fast, that speed is your competitive moat.

The technology to do this is already here. We help Fortune 1000 clients with this every day. The harder part - the part I'd start on now - is the org design that enables you to fully unlock the design and business side of this challenge.

A starting checklist

If this resonates, here's where I'd begin:

1. Run the three-question audit. Ask who owns job architecture, skills, and tasks. Map the actual answers. The gaps and overlaps will tell you most of what you need to know.

2. Name an owner for Work Architecture - including task frameworks. Even a small, cross-functional team is a start. The goal is one place where roles, tasks, and skills are reasoned about together.

3. Pair Work Architecture with Work Redesign. Don't split the team that maintains the map from the team that redraws it.

4. Stand up SWP as a distinct layer that consumes work-architecture intelligence and turns it into forward-looking plans - and make sure the plan connects to where the work actually happens.

5. Build the matrix early. Permanent Finance and IT seats, ad hoc business-leader representation. Design for it from the start rather than bolting it on.

6. Pick one business unit and prove it. Don't attempt a big bang. The organizations that succeed almost always start with one talent segment or one pressing problem, build the muscle, and expand from there.

Curious whether others are seeing the same ownership gap - or whether some of you have already solved it. What's worked?