What's the actual difference between a role and a skill?

It sounds like a semantic question. It isn't.

A role is a job title with a set of assumed responsibilities attached to it. A skill is something a person can demonstrably do, get better at, and apply across more than one context.

Job descriptions describe roles. They rarely describe what someone can do.

That gap is why so many organisations are shifting toward skills-based structures; not because "skills-based" is trending, but because roles are changing faster than the documents describing them can keep up.

A few practical shifts this creates:

• Hiring moves from "who has done this job before" to "who can demonstrate this capability"

• Career pathways stop being a ladder and start being a lattice where skills transfer sideways, not just up

• Learning stops being tied to a role and starts being tied to specific behaviours someone needs to build

The organisations doing this well aren't rewriting every job description overnight. They're starting smaller: identifying the two or three skills that matter most for a critical function and building learning around those first.

This is exactly the kind of shift custom learning design exists to support. Generic training can't teach a skill that's specific to your organisation's context. Bespoke content can.

Roles will keep changing. The organisations that treat skills as the more durable unit will keep up. The ones still hiring and training against job titles won't notice they've fallen behind until it's a scramble.

Jen