A leader wants training assigned to everyone. Not recommended or available. Assigned. 

Learning professionals know what that means. The learning platform will track and provide a dashboard monitoring compliance. Regardless of whether learning and development (L&D) agrees or disagrees, mandatory enrollment happens. Post-training, there is proof that people were enrolled, completion was measured, assessments were administered and the organization can point to a number and say that training happened. But did it? 

Dear L&D, the hard conversation is about what the profession protects (and leans on). 

The persistent yet misguided belief is simple: Completion means someone is educated, upskilled or changed. That belief does a lot of work outside of its own lane. Enrollment turns to action, completions to evidence and, often, “learning management system (LMS) traffic” becomes a budget justification for the platform.  

The enrollment-to-justification loop is not built by one person. Leaders may ask for enrollment and completion because those are the most common metrics made visible to them. L&D supplies them because those are among key data points an LMS tracks. Nobody is dishonest, yet the story is misleading. The metric is weak and load bearing at the same time. 

Why L&D Protects the LMS 

To be fair, L&D does not protect the LMS because of confusion about how adults learn. Most know learning happens outside of the course. APQC found knowledge workers spend 8.2 hours a week (400 hours a year) looking for, recreating and duplicating information and expertise. By contrast, ATD’s 2026 State of the Industry report found that employees used an average of 16.7 formal learning hours across the entire year. People question, search, skim, watch, try, fail and ask for help.  

The platform is guarded because it gives the learning shape. Courses are artifacts that can be counted and controlled. They are intentionally designed assets with defined outcomes and structure.  

The LMS is also territory and one of the places L&D fully owns compared to informal channels, help centers and in-application guidance that may be owned by other functions. Protecting the LMS can feel like protecting L&D itself, because at budget time the invisible learning is harder to measure and does not defend the L&D department. 

Underneath all of it is the fear that, if learning already happens everywhere else without L&D, the concept of a broader knowledge ecosystem starts to sound like an argument for a training team’s irrelevance. 

Learning Already Happens Outside the LMS 

The knowledge ecosystem is not a theoretical concept; it already exists. Learners are in applications, help centers, chat threads, video feeds, search engines and day-to-day interactions. They are using whatever gets them unstuck the quickest. They are also creating their own content to share with peers. Like water in a river, learners follow the path of least resistance. Over time, they carve the channels that get the job done. That practice is not a failure of structured learning in an LMS. Structured learning still has an important job inside the ecosystem, because some knowledge has no demand. Learners cannot search for what they do not know is missing.  

However, continued learning and knowledge acquisition are not equal to knowledge governance. A self-organizing ecosystem does not equate to accuracy, maintenance, structure or planned resources. It does not even protect learners from confident but outdated answers and misinformation. 

“Stop protecting the LMS” does not mean abandoning the platform. Instead, it means stop asking it to represent the whole function of learning. The LMS has a role holding structured learning, supporting compliance and accounting for the known unknowns. That has not changed. But the actual function is much larger than just the LMS.  

Where L&D Fits in the Knowledge Ecosystem 

To expand the organizational mindset of learning, first consider what is happening right now with artificial intelligence (AI) as it is changing patterns and relationships with knowledge. In some organizations, a knowledge management function already holds part of this work. In most small to mid-sized organizations, no one does. Either way, one question goes unasked, and it is the question L&D exists to answer: Does the knowledge produce capability? 

L&D is positioned to audit where people go when they need instructions, new information and answers. Learning professionals also identify where workarounds, repeated questions, abandoned searches and peer support happen. That gathered information is evidence, not noise. The evidence differs by audience. Inside the organization, it often looks like informally created content that spreads because it is a quick fix, not because it builds longer-lasting capability. In customer learning, it looks like functions publishing in parallel without connecting the dots, so the customer receives conflicting instructions from the same company. 

Bring the Capability Question to the Table 

With evidence in hand, look for areas of missing governance: 

• Where is no one accountable for accuracy? 

• Where is content duplicated? 

• Where are learners getting five versions of the same answer? 

• Where does the right answer exist, yet performance still does not move? 

The first three questions belong to knowledge management (KM). The fourth belongs to L&D, and no other function is asking it. 

What L&D does next depends on what already exists. Where a KM function is present, join it and bring the capability question to the table. Where there is none, and where organizations cannot resource one, convene the content owners and advise. The role flexes; the accountability for coherence does not. 

This is not an argument for new territory. The profession does not need another platform to protect. It is an argument for showing up to a shared problem with expertise that is currently overlooked and missing from the table. The timing matters, because organizations are rushing to point AI at ungoverned knowledge. An AI tool trained on five versions of an answer delivers the wrong one with confidence — or all five at once adding to confusion. Diagnosing why that damages performance is learning expertise, not data hygiene. 

The LMS was never the profession; it was one delivery channel that happened to come with a dashboard. Protecting it keeps teams focused on the place where learning can be counted. Learning stewardship and advocacy follows people to every place learning happens. So, dearest L&D, recognize that the dashboard is not the destination.