01 July 2026

Last time, this series followed the skills data L&D builds as it quietly outgrew the function and became something the whole business runs on — feeding hiring, workforce planning, and the decisions about who moves where. That shift is easy to celebrate and easy to stop thinking about too soon. Because if the data has left home, there is an obvious question sitting right behind it that almost nobody asks out loud: what happens to L&D itself?

For most of its history, L&D has known exactly what it was — the function that makes and runs learning. In 2026 that definition is quietly coming apart. When the point of the work is no longer the courses but the capability picture underneath them, the team that built that picture can’t keep describing its job the way it did in 2018. The interesting story this year isn’t only that skills data changed the business; it’s that it’s changing the function that made it.

The Old Job Description Runs Out

Ask most L&D teams what they do and the answer is still framed around output: courses designed, programmes launched, completions logged, satisfaction scored. It’s a job description built for a world where the deliverable was content and success meant people consumed it. That world hasn’t vanished, but it has been demoted. When the organisation starts asking whether capability actually moved — and using the answer to hire, staff, and promote — a tally of courses shipped stops being a measure of anything that matters.

This is uncomfortable precisely because the old metrics were so easy to report. A completion rate is clean; a claim that the workforce is measurably more capable is not. But the moment skills data becomes the thing the business relies on, L&D’s worth is judged by the quality of that data and the capability behind it, not by the volume of learning it pushed out. The job description didn’t get updated so much as it quietly ran out of road.

From Producing Content to Stewarding Capability

The clearest change is where the team’s centre of gravity sits. Producing content used to be the core craft — storyboarding, authoring, building the catalogue. That work doesn’t disappear, but it’s no longer the point, especially as faster ways to produce and assemble content make the raw making of courses less of a bottleneck. What becomes central instead is stewardship: keeping the skills taxonomy honest, making sure profiles reflect reality, and connecting learning to the capability it’s supposed to build.

In practice that reframes almost every existing activity. Managing the catalogue becomes less about how much sits in it and more about whether each piece maps to a capability the business actually needs. Setting learning goals stops being an annual formality and becomes the way individual development ties back to the skills picture leaders are now reading. The team’s product isn’t a library any more; it’s a trustworthy, current view of what people can do.

The Team Becomes a Broker, Not a Factory

Once skills data feeds hiring, mobility, and planning, L&D can’t operate as a self-contained factory that takes requests in and ships courses out. It sits in the middle of a conversation that now includes recruiters, workforce planners, HR, and the line managers who own the day-to-day of capability. Its most valuable move is often not to build something but to broker — to translate a business problem into a capability question, and a capability question into the right mix of development, hiring, or redeployment.

That’s a consulting posture more than a production one. It leans on the same signals the rest of the business is starting to trust: what development conversations reveal, where aspiration and readiness line up, and what the capability data says is genuinely missing. The team that used to be measured by throughput becomes valuable for judgement — for knowing which lever to pull, and when building a course is the wrong answer.

New Skills for the Skills Function

A function that stewards capability and brokers decisions needs a different toolkit from one that produces courses. Data literacy stops being a nice-to-have and becomes core: if the team owns the skills picture, it has to be fluent in reading, questioning, and governing it. The same analytics that once tracked learning now have to be interpreted for an audience making real workforce decisions, which is a genuinely different skill from reporting completions.

Alongside that sits a more consultative craft — business partnering, facilitation, the ability to sit with a leader and shape the problem rather than take an order. It’s worth naming that this can be a stretch for teams hired for instructional design and content production. The skills function needs its own skills, and building them is part of the transition, not an afterthought to it. There’s a neat symmetry in it: the function that tells the business to take capability seriously has to do exactly that with itself.

The Catch: Giving Up the Old Scoreboard

None of this is free, and the honest catch is about identity as much as capability. A team that has always known its worth through course counts and completion rates is being asked to give up a scoreboard that was reassuringly concrete for one that’s harder to point at. Measured by the old numbers, the new L&D can look like it’s doing less; measured by the new ones, it may be doing the most important work it ever has — but only if the organisation agrees to change what it counts.

That’s the real risk in 2026: not that L&D fails to evolve, but that it evolves while everyone around it still grades it on the old metrics. The functions that navigate this well tend to renegotiate their own scoreboard early — agreeing with the business that success now means trustworthy capability data and better workforce decisions, not a busier learning calendar. The skills data may have outgrown L&D, but the function that stewards it hasn’t shrunk. It’s being asked to grow into something considerably more valuable — and to stop measuring itself by the thing it used to be.