AI has removed L&D’s safety net. For years, we could prove our value by creating courses, workshops and content that helped people access knowledge. But when AI can deliver information faster, the question changes. If performance still varies when answers are everywhere, maybe the real issue was never access to knowledge. Maybe it was how the work was designed.

The threat isn’t that AI makes L&D irrelevant. The opportunity is that AI makes performance problems impossible to ignore. When everyone is experimenting, duplicating effort and getting wildly different results, the issue isn’t motivation or effort. It’s that the work hasn’t been defined clearly enough for people — or AI — to do it consistently.

The story of Ignaz Semmelweis shows what happens when a field stops blaming the individual and starts examining the environment. Doctors didn’t reduce mortality by making women stronger; they changed the conditions around them. And L&D may need to make a similar shift: skills still matter, but performance depends heavily on the system people operate within — especially now AI is part of the work.

If performance depends on people remembering, interpreting and improvising, results will always vary. That’s why skills alone aren’t enough — especially when AI needs clear instructions, context and guardrails to perform well. Before we train people to “think critically”, we need to define what good looks like and bake that guidance into the work itself. Environment first. Skills second.

Learning matters, but learning and performance are not the same thing. Learning is the means; performance is the outcome. And if AI is exposing the limits of knowledge transfer and capability building, L&D has a choice: keep defining itself around helping people learn, or step into a broader role focused on designing the conditions that help people perform.

The shift from learning professional to performance partner doesn’t start with a new job title, team name or org chart. It starts internally — with the decision to see learning as one tool inside a broader performance toolkit. And once you see work design as the starting point, not the afterthought, it’s hard to unsee it.

Sometimes the problem isn’t missing knowledge, weak skills or badly organised content. It’s the absence of a clear, repeatable way to do the work. In this example, new salespeople didn’t need more product training — they needed guided workflows that helped them prepare, run and follow up on demos consistently, using the wisdom already trapped in experienced people’s heads.

Even when L&D spots a clear opportunity to improve performance, the system around us often pulls us back towards visible, scalable, people-positive solutions — programmes, platforms and training libraries. That isn’t because practitioners lack ambition; it’s because many organisations incentivise employee experience over performance. And until that changes, we’ll need to keep pushing the conversation from learning activity towards measurable business impact.

Designing work sounds simple until you hit the reality of complex organisations: disconnected tools, fragmented ownership, undocumented workflows and best practice trapped in people’s heads. An AI prompt library is a perfect example — useful in theory, optional in practice. If prompts, guidance and standards aren’t embedded into the flow of work, performance still depends on memory, motivation and heroic effort.

Before I ever thought of work design as an L&D problem, I was trying to build a satnav for my own work — a system that showed me what to do next, surfaced the right context, and stopped everything disappearing into a hot mess of tags, reminders and good intentions. Looking back, those productivity experiments were my first attempt at designing an environment that improved performance. I just didn’t know it yet.

Notion was the first tool I’d found that let me design the system around the work, rather than squeeze the work into someone else’s system. By creating my own task database, properties and filtered views, I could finally surface what I needed, when I needed it — the elusive satnav for work. And that’s when the organisational dots started connecting.

Notion templates changed the dashboard from a task list into something more powerful: guidance embedded directly into the work. Instead of resources dying in SharePoint or hiding inside eLearning modules, checklists, examples, links and instructions could appear at the exact moment they were needed. For the first time, “in the flow of work” felt like more than a slogan.

Once databases could talk to each other, the system became more than a way to manage tasks. It became a way to capture what people learned while doing the work, then surface those insights for the next person at the exact moment they needed them. The wisdom usually trapped in heads, retros and forgotten documents could finally become part of the workflow itself.