Why job architecture redesign stalls and how to fix it

At our recent Work Design Collaborative session with The Learning Forum, we ran a quick poll. The numbers confirmed what many of us already felt.

Most leaders aren't redesigning job architecture for theory or optics. The top drivers are skills and learning alignment. And the ability to move talent quickly. Agility and capability.

Not compliance. Not documentation. Just outcomes.

Still, the majority said their current architecture is only partially aligned with strategy. A third weren't even sure. Only 8% said it's fit for purpose.

No one claimed it was "working well."

When asked what's blocking progress, the patterns were clear. It's not budget. It's not exec buy-in. It's complexity. It's fractured systems. It's teams trying to redesign work while still running it on old frameworks.

Skills initiatives stall because they're built on broken structures.

Job architecture is an octopus

One person called it that during the session. I loved it.

It reaches into everything. Skills, pay, learning, hiring, performance. Yet it rarely works in sync with the business. Most organizations have added layers and spreadsheets. But they haven't stepped back to ask the real question.

Does this reflect how work actually happens?

If I automate chaos, I just scale the chaos.

Task first. Then skill. Then structure.

The real shift underway isn't philosophical. It's operational. Map tasks first. The skills follow. Understand the work. Then design structure that works.

But most organizations do this backwards. They start with job titles. They guess at skills. They lose track of the actual work.

Work moves. It flows across projects, teams, and systems. It doesn't sit in fixed boxes. If your infrastructure can't track that, it's not infrastructure. It's friction.

From Job Architecture to Work Architecture.

Design the work. Don't just describe it.

This is where real value shows up. Not in HR documents. In execution. In resourcing. In work movement. In cost decisions. In every change your organization needs to make.

Don't wait for the perfect blueprint.

Start with what's true now. What's useful. What's moving.

Use the pressure

Someone said "patience is key." I disagree.

Pressure is better. It forces action. It forces focus.

The opportunity is here. Most organizations know the old way doesn't work. The smart ones are already building something better.

We'll meet again on November 5 at Google HQ in NYC for another in-person event. I'll recap my findings then.

Until then, stay with the work. Stay sharp. Don't wait for permission to fix what's broken.

Siobhan 💜