Why Employees Don't Use the LMS (And What Does)

Key Takeaways

• LMS non-usage is structural, not motivational. The LMS was built for scheduled, mandatory training - compliance, onboarding, certification - which is roughly 5% of workplace learning. The other 95% is unplanned and happens somewhere else entirely.

• Employees aren't refusing to learn. They're refusing to commute to a portal. The same person who ignores a mandatory module will spend twenty minutes on YouTube figuring out a problem that's blocking their work right now.

• This off-platform learning has a name: "shadow learning." It's unrecorded, so L&D can't see it, credit it, or build on it. It's a demand signal, not a compliance failure.

• Nudges, gamification, and relaunch campaigns don't fix this. They optimize adoption of the wrong layer. The fix is meeting the demand where it fires: at the moment of the question, not on a course calendar.

The completion metric is measuring the wrong 95%

Every L&D leader has heard some version of this: "I only use your LMS when it's mandatory." It's usually said half-apologetically, sometimes not apologetically at all. "Dude, what do you want from me? I'm good with YouTube."

These aren't outliers. They're the honest version of what your usage dashboard already shows: completion rates that look fine for assigned compliance tracks and fall off a cliff for anything optional. The instinct is to read that gap as an engagement problem, then reach for the engagement toolkit: badges, leaderboards, a relaunch email, a mandate from a VP.

None of that addresses what's actually happening, because the gap isn't about motivation. It's about where the LMS lives in the employee's day versus where the need for skills actually shows up.

The LMS was built for a specific, real job: scheduled, mandatory, auditable training. Compliance modules, onboarding tracks, certifications. It's good at that job, and it's measured on it, because completion is the metric that maps to audit requirements. That job is real, but it's also small. It covers roughly 5% of the learning that happens in a company in a given month.

The other 95% is unplanned. An engineer hits an error she's never seen. A new manager has to run her first difficult conversation on Thursday. Someone on the support team gets asked about a product area they've never touched. None of that shows up on a training calendar, because none of it is schedulable. It happens the moment the need appears, and it needs to be resolved in minutes, not after a manager approves a course enrollment.

So the employee does what anyone does when they need an answer now: they search. YouTube, ChatGPT, a Slack thread to a colleague who's dealt with this before. That's not employees avoiding the LMS out of laziness or spite. It's employees solving a problem using the tool that actually answers the problem, at the speed the problem demands.

Shadow learning has a name

This unrecorded, self-directed learning has a name: shadow learning. It's shadow AI's cousin, not a compliance failure but a demand signal that most L&D functions have no visibility into. Learn more about what shadow learning is and how to measure it. IT already fought - and lost - this exact battle with unsanctioned tools; we unpack the playbook it built afterward in Shadow AI and Shadow Learning.

The reason it matters to name it is that it reframes the problem from "our employees aren't engaged" to "our employees are already learning constantly, just somewhere we can't see." Those are very different problems with very different fixes. The first one points at incentives. The second one points at infrastructure.

Learning in the flow of work starts with intent, not with a catalog. An employee opens YouTube because they have a specific question, right now. They don't open a catalog and browse for something relevant, because relevance isn't the constraint. Speed and specificity are.

Why the fix isn't another relaunch campaign

There's a pattern that repeats across L&D functions that are stuck on adoption: a new campaign to "drive engagement" with the same platform that structurally can't serve the moment the learning need appears. New badges. A leaderboard. An all-hands push. Usage ticks up for two weeks and settles back down, because none of it changed where or when the LMS shows up relative to the employee's actual problem.

This is the incumbent's dilemma playing out inside a single company. The LMS vendor's business is the catalog: licensing it, expanding it, reporting on completion against it. Protecting the catalog is rational for the vendor and for the L&D team that bought it. But protecting the catalog means the fix always gets proposed as "more catalog, presented better," when the actual gap is that no catalog, however well presented, is sitting in Slack at 2:47pm when someone needs an answer to keep working.

Blockbuster didn't lose because people stopped wanting movies. It lost because the format that mattered moved from "drive to a store on a schedule" to "press play right now," and the incumbent kept improving the store. The same shift is happening to workplace learning. The catalog isn't wrong, exactly, it's just answering a question fewer and fewer employees are asking.

What an L&D team can actually do this quarter

None of this requires abandoning the LMS. Compliance, onboarding, and certification still need a system of record, and the LMS is still the right tool for that 5%. The work is building visibility and a response for the other 95%, without pretending a relaunch campaign will get employees to route their real, unscheduled questions through a portal.

Audit what employees are actually asking. Pull a sample of real questions from Slack threads, support tickets, and manager 1:1 notes over the last month. Not the topics you assigned, the ones that came up unprompted. That list is your actual demand signal, and it will look almost nothing like your course catalog.

Measure time-to-learning, not just completion. Start a clock at "employee has a specific question" and stop it at "employee is learning something relevant to it." If that number is measured in days because it requires finding a course, requesting access, and scheduling time, that's the number driving your adoption numbers, not employee motivation.

Pilot a flow-of-work layer alongside the LMS, not instead of it. The question worth testing isn't "can we replace the LMS." It's "what happens to unprompted adoption when learning shows up inside Slack or Teams, at the moment someone asks, instead of behind a portal login." We wrote up the model for what that layer looks like in our guide to LMS alternatives, and Plynn is one implementation of it: see how learning inside Slack works.

Look at what happened when someone else tried this. In one fintech deployment, 60% of employees adopted a flow-of-work learning layer with no prompting or mandate, 90% of people who created a course came back to create another, and cost per learner came in roughly 70% below the existing per-seat LMS licensing. Small cohort, one company, measured rather than projected. Full numbers and methodology are on the pilot results page.

The number worth watching isn't how many people finished an assigned module. It's how many people came back on their own, without being told to. That's the number that tells you whether you've built something people actually want to use.

Frequently Asked Questions

Why don't employees use the LMS even when leadership pushes adoption?

Because the push usually targets motivation, and the real barrier is structural: the LMS is built for scheduled, catalog-based learning, while most employee questions are unplanned and need answering in the next few minutes. A mandate or a relaunch campaign can raise completion of assigned content, but it doesn't touch the 95% of learning that happens off the platform, because that learning was never routed through the LMS to begin with.

Is low LMS engagement a sign employees don't value learning?

No. The same employees who skip optional LMS modules are often teaching themselves new tools on YouTube or working through problems with ChatGPT the same week. They're learning constantly. It's just happening somewhere the LMS, and by extension L&D, has no visibility into. That gap is what "shadow learning" describes.

What's the difference between shadow learning and just Googling something?

Scale and consequence. Every employee, in nearly every company, is doing some version of "just Googling it" multiple times a week to unblock real work. In aggregate, that's a massive, continuous stream of on-the-job learning happening with zero curation, zero record, and zero connection to what L&D knows about skill gaps on a team. Naming it as shadow learning is what makes it visible enough to measure and design for.

Should we replace our LMS to fix adoption?

Usually not. The LMS still does its job well for compliance, onboarding, and certification, the mandatory 5%. The fix for adoption is adding a layer that serves the other 95%: unplanned, task-triggered learning that happens where employees already work. Most teams that solve this run the two side by side rather than ripping one out. Our LMS alternative guide walks through how to evaluate that layer without disrupting what already works.