Job Architecture: The backbone of a skills-based organisation
Everyone wants to talk about skills right now. Skills taxonomies, skills clouds, skills-based hiring, skills-based pay. Far fewer people want to talk about job architecture, it sounds administrative next to the promise of a "skills-based organisation" - the unglamorous filing cabinet under the shiny new AI-powered talent marketplace.
That's a mistake, you cannot build a skills-based organisation on top of a broken or absent job architecture, you can only build confusion faster. In the same manner, before we can have a sensible conversation about delivering the benefits of AI in any organisation, applying agentic AI to poor quality data will only exacerbate the problem.
Here's the paradox at the heart of the skills agenda: roles are becoming more fluid, work is being reshaped by AI faster than any job description can keep up with, and yet the need for clarity and structure has never been greater. Skills don't exist in a vacuum, a skill only means something in relation to a job, a level, a career path, a pay range. Strip that structure away and "skills-based" becomes a slogan, not a system.
The data backs this up, most organisations already have some form of job architecture - but the vast majority never built skills into it. The result is two parallel, disconnected systems: an org chart that governs pay and progression, and a skills initiative that lives in a separate tool nobody trusts. Meanwhile, the organisations that do get this right - who build job architecture as the connective tissue between skills, roles and pay - are significantly more agile, and far better at deploying learning and mobility against what the business actually needs.
At EX3, in the conversation we continue to have with clients we find that for some organisations, becoming “skills aware” may be all that is required to make a difference rather than a full transformation to being a “skills based organisation”. As we have seen in many areas, what works for one organisation may not work for another – every organisation has different needs and levels of maturity. Our view is that the shift from fixed roles to a skills model isn't a rip-and-replace exercise. It's a redesign of the foundation, done deliberately:
- Simplify before you digitise – Sprawling, inconsistent job catalogues don't get easier to manage by adding skills to them - they get harder. The organisations seeing real value are the ones who first collapse hundreds of narrow titles into fewer, broader job profiles, making skills genuinely mappable to real work.
- Design skills into the architecture – Not alongside it. Skills should sit as a native layer of the job framework - tied to levels, career paths and pay ranges - not bolted on as a separate taxonomy that only the L&D team logs into.
- Build for change, not for launch – A job architecture that's accurate on go-live day and stale twelve months later isn't an asset, it's technical debt. The organisations built for AI and constant change treat architecture as a living structure, governed and refreshed continuously.
This is also where the AI conversation gets real, rather than aspirational. AI can only recommend the right learning, the right mobility move, or the right hire if it understands what "right" means - and that definition lives in the architecture, not the algorithm.
As our CHRO, I'd put it more bluntly: Every organisation says it wants to be skills-based. Almost none of them are willing to do the unglamorous work of fixing their job architecture first. That's backwards, you don't earn agility by declaring it - you earn it by building a foundation strong enough to carry the weight of constant change. Job architecture is that foundation: get it right and skills, internal mobility and AI all start pulling in the same direction; get it wrong and you're just relabelling the same rigid structure with new, fancy words.
If your skills strategy is struggling to land, the honest first question usually isn't "which skills platform should we buy?" It's "do we actually have a job architecture that can carry the weight of what we're trying to build?"
Get the backbone right, and everything else - skills, mobility, pay transparency, AI-driven insight - has something solid to stand on.
Contact us
