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?
No comments:
Post a Comment