Wednesday, February 25, 2026

The work behind the work (2)

 ...so I am still pondering the new world of L&D and the role of AI. 

AI changes the economics of producing many of the things that have traditionally defined our work. It can generate a course outline, write a draft, produce a quiz, create scenarios, summarize information, and help assemble learning materials at a speed that would have been difficult to imagine just a few years ago. The output may need considerable review and revision, but the barrier to producing something that looks like a finished product has dropped considerably.

So: If producing the deliverable becomes easier, what happens to the value of the expertise that goes into deciding what the deliverable should be? I remember writing years about about the fact that often something we have accomplished likely took "half an hour plus the rest of our lives up till now."

I don't think the answer is to abandon instructional design or stop making things. Rather, I think we need to pay much more attention to the parts of our work that have always mattered but haven't been especially visible. What did we notice that prompted us to take a different direction? Why did we decide a course wasn't the right answer? What did we learn from talking with employees? Which assumptions did we challenge? What trade-offs did we consider? How did we arrive at a recommendation, and what happened as a result?

These are not incidental activities surrounding the "real" work. THEY ARE THE WORK.

AI introduces an interesting possibility here, too. It can help lower the cost of making work visible. Rough notes from a conversation can become a useful summary. A collection of observations can be organized into patterns. A series of decisions can be turned into a record that others can follow. AI can help us communicate and document work that might otherwise remain scattered across notebooks, inboxes, meeting transcripts, and individual memories.

Of course, making something visible doesn't automatically make it meaningful or credible. AI can produce a polished explanation of a decision without having any knowledge of what actually happened. The value is in connecting what we share to real work, real decisions, and real consequences. The technology can help us tell the story, but we still have to supply the substance.

I began thinking about a different kind of professional portfolio, too. Not one that consists primarily of samples of courses, presentations, and other finished deliverables, but one that makes professional thinking visible. What did you notice? What questions did you ask? What did you recommend, and why? What did you decide not to do? What changed as a result of your involvement?

This is a different way of thinking about evidence of expertise. A polished deliverable can show that you know how to make something. It tells us considerably less about how you think, how you exercise judgment, or how you work through ambiguity.

I realized I'm not just interested in helping L&D practitioners become more visible. I want to help them recognize, articulate, and demonstrate the expertise that was already present in their work, much of which had been obscured by a profession that had come to measure itself by what it produced.

The work behind the work deserves to be seen.The organizations that hire us need to understand what expertise looks like, where it resides, and what it makes possible.

Thursday, February 19, 2026

The work behind our work

Since we moved into this new year I found myself returning to an idea that had been on my mind for quite a while: visibility. Not visibility in the sense of personal branding, self-promotion, or making sure people know your name. I was thinking about something more fundamental: how much of the work L&D practitioners actually do remains invisible, even to the people who depend on it.

I've been arguing for awhile now that organizations need more than courses and content to become adaptable. They need social infrastructure, continuous learning, and the human capacity to make sense of what is happening and decide what to do next. AI can amplify those capabilities, but it can't substitute for the human work that makes them useful.

The more I thought about that, the more I began to wonder about the implications for the L&D profession itself. For a long time, we've been defined by what we produce. We develop courses, build eLearning, create job aids, design workshops, develop programs, and populate learning management systems. Those things are tangible. They can be counted, reviewed, approved, delivered, and reported. Someone asks for a course, we make a course. Someone needs a program, we develop a program. The finished product becomes the evidence that work has been done.

There's nothing inherently wrong with producing those things. Organizations need learning experiences, and there's real expertise involved in creating them. But over time, the product has come to stand in for the work itself. The conversations that preceded it, the questions we asked, the assumptions we challenged, the decisions we made, and the alternatives we considered tend to disappear from view once the deliverable is finished.

This has consequences for how L&D is understood and valued. Much of our work has been transactional. A client or manager brings us a request, we produce something, and the transaction is complete. We may have done considerable investigation, negotiated competing priorities, consulted subject matter experts, tested ideas, and made judgments along the way. But what the organization sees is the course, the workshop, or the job aid. The work behind it is largely hidden.

I've written for years about showing your work and working out loud. I've encouraged practitioners to share small things, narrate their thinking, make their discoveries available to others, and help knowledge travel across organizational boundaries. I've also recognized that this can feel like one more thing to do. People are busy. Documenting every decision or writing a polished account of every project isn't realistic, and it shouldn't become another administrative burden.

I began to see that visibility was about more than helping individual practitioners demonstrate their expertise. It was also about changing how organizations understand the contribution of L&D. If all people see is the finished product, they are likely to keep defining our work in terms of finished products. If they can see the investigation, judgment, collaboration, and problem-solving that went into the work, they have a different opportunity to understand what we contribute.

I'm still trying to work this out. I was writing about pieces of it, responding to things other people were saying, and making connections between ideas that had previously seemed like separate conversations.

And so now I am pondering: What would happen if we made more of the work behind the work visible?