Article guide Jump to a section 8 min read · 8 sections
Engage Share or leave a rating Copy, send, or respond when you finish

Leave a rating

A story I keep telling other consultants when LMS comes up: a colleague described a small team that signed for a forty-thousand-dollar-a-year platform to track twelve mandatory courses. Three months in, the HR director was looking at the bill wondering what they had actually bought. The platform was doing exactly what they’d asked it to do. They just hadn’t needed to ask any of it.

The standard LMS demo is built around the part of the platform the vendor wants to show: the polished learner interface, a reporting dashboard, sometimes a SCORM playback engine. The parts the buyer will actually live with — the bulk-enrollment workflow, the content-update workflow, the auto-renewal clause — tend to land at the end of the meeting, when there’s less time to ask hard questions about them.

A learning management system (LMS) is the most common piece of software companies buy for training, and the second most common piece they regret buying. The buy decision usually starts because the team thinks they need a learning platform — but the actual problem is content delivery, content tracking, or content management, and an LMS solves only one of those well. Here is how to figure out which one is your problem before signing.

Quick Answer

A learning management system (LMS) is software that hosts training content, enrolls learners, and reports completion. The honest test of whether your team needs one: do you have a regulatory or audit requirement that “this person completed this training on this date” must be provable? If yes, you need an LMS or an LMS-equivalent. If no, you probably need a content delivery method instead, and an LMS is the wrong shape for that problem.

The rest of this post is the decision tree.

What an LMS actually solves (and what it doesn’t)

What an LMS does well:

  • Tracking and compliance. Who completed what, when, with what score, and on what device. Audit-grade. This is the original LMS job and the one it still does best.
  • Enrollment and access control. Cohorts, roles, prerequisites, expiry dates. Useful when the same content needs to reach different audiences with different permissions.
  • Content sequencing. Modules in order, gates between them, branching paths. Useful for genuinely linear curricula where the order matters and the learner has to earn the next module.

What an LMS does poorly, despite the marketing:

  • Content authoring. Most LMS authoring environments are worse than Word, slower than PowerPoint, and an order of magnitude harder to update than a SharePoint document. The team that authors content is the team that ends up resenting the platform.
  • Real engagement. Completion rates on self-paced LMS modules trend toward 30 to 40 per cent even when the content is excellent. Learners don’t enjoy the platform. They tolerate it.
  • Just-in-time delivery. The pattern people actually use at work — search the wiki, watch a 90-second video, get back to the task — is not what an LMS is shaped for. The LMS asks you to schedule learning. Work asks you to fix something now.

If your training problem is “people need to learn things while they work,” an LMS is at best a peripheral tool. If the problem is “we need to prove they did,” it is the right tool.

The four shapes the market split into

  • Moodle. Open-source, free to self-host, surprisingly capable. Strong if your IT team is comfortable running PHP and MySQL, and your content is module-and-quiz shaped. Weak if you want a polished learner experience without a budget for theming work. Common pick in higher-ed and unionised environments where licensing economics matter more than learner-facing design.
  • LearnDash on WordPress. An LMS plugin that turns a WordPress install into a course platform. Wins when you already have a WordPress site, want full control over the front-end, and your content is content-marketing-adjacent — free intro courses driving paid services, that shape. Loses when you need enterprise single sign-on (SSO) or genuinely deep reporting.
  • Vendor Learning Experience Platforms (LXPs). Cornerstone OnDemand, Docebo, 360Learning®, Absorb®. Subscription platforms with polished learner experiences and decent reporting. Win when you have 500 or more learners, a budget over $30,000 a year, and human-resources-system integrations to satisfy. Lose when you have 50 learners and three mandatory courses — the price tag in those cases is paying enterprise rates to track work that a list with a date column already tracks.
  • “No LMS” delivery in Microsoft Teams, SharePoint, or a wiki. Underrated. A SharePoint site with a content library, a Teams channel for discussion, and a Microsoft Forms® quiz with date-stamped responses gets you most of the LMS value at zero incremental software cost. Loses on cohort enrollment and on playback for legacy SCORM courses; wins on every other dimension for small teams.

When you don’t need an LMS

The “you don’t need this” cases that most vendor sales calls won’t volunteer:

  • Fewer than 100 learners total, no compliance requirement → SharePoint or Teams will do.
  • Training content that changes more than quarterly → an LMS becomes a content-management tax. The wiki is faster.
  • Training that’s instructor-led with a one-off PDF handout → the LMS is a glorified file-share. Email the PDF.
  • “We need analytics” with no defined metric → an LMS will give you a reporting dashboard. Whether anyone reads it is a separate question.
  • Content that needs to be findable in Google for content-marketing reasons → an LMS gates everything behind a login, including the search-engine value.

The decision matrix: volume × shape × audience

Three variables are enough because they map to the three ways LMS purchases tend to misfit the team that bought them: too small to amortise the cost of the platform, wrong content shape for the platform’s authoring environment, wrong audience for the platform’s interface. Volume, shape, and audience are the three constraints that, if any one of them is off, tend to surface as a regret somewhere in year two.

A 3-by-3 decision matrix mapping LMS choice to a team’s situation. Columns are volume (under 1,000 learner-hours per year, 1,000 to 10,000, over 10,000). Rows are content shape (modules and quizzes, reference, instructor-led). Cells with a pale teal fill recommend no-LMS — Teams, SharePoint, MS Forms, or a documentation site — and cover the under-1,000-volume column entirely plus the reference and instructor-led rows in the middle column. Cells with a pale gold fill recommend an LMS: LearnDash on WordPress for customer-facing modules at moderate volume, Moodle for internal modules at moderate volume or large-volume reference content, Vendor LXP (Cornerstone, Docebo) for the highest-volume cells. Cells with a thicker navy border require audit-grade completion proof, which excludes no-LMS as a viable option in those cells. Audience appears as small chips inside each cell: navy for internal, gold for customer and public, teal for partner.
You locate yourself, not a winner. Volume on the x-axis, content shape on the y-axis. Audience chips and audit-grade borders are constraints inside the cell — they refine the answer; they don’t pick the cell for you.
decision = f(volume, shape, audience)

Volume: learners multiplied by hours per learner per year. Under 1,000 learner-hours, the LMS overhead exceeds the learning benefit. Over 10,000, no-LMS approaches start to break.

Shape: is your content mostly modules-and-quizzes (LMS-shaped), mostly reference (wiki-shaped), or mostly instructor-led (calendar-shaped)? An LMS forces all three into module-and-quiz, which is why teams hate the move when the underlying content isn’t that shape to start with.

Audience: internal-only, customers, partners, or public? Internal-only is the easiest case — an IT-managed Moodle or a no-LMS approach works. Customer or partner training adds branding, scaling, and single-sign-on requirements that push the choice toward LearnDash or a vendor LXP. Public training is a content-marketing surface and probably wants WordPress with LearnDash so the front-end stays findable in search.

Common mistakes when buying an LMS

  • Buying for the demo, not the daily. The vendor demo is the polished version. Ask to see the bulk-enrollment workflow, the content-update workflow, and the reporting-export workflow. Those three are where the daily friction lives.
  • Confusing “we need reporting” with “we need an LMS.” If the report you actually need is “did this person complete this thing by this date,” a list with a date column is a better answer than a $40,000 subscription.
  • Buying SCORM compatibility you’ll never use. SCORM is the legacy interoperability format for course content. Most modern courses are authored in HTML5 or video and don’t need SCORM at all. If you’re not migrating an existing SCORM library, you don’t need SCORM support — and you don’t need to pay for it.
  • Underestimating the content-authoring tax. Buying an LMS is the cheap part. Authoring 40 hours of polished course content for it is the expensive part — typically ten to twenty times the LMS subscription in year one.
  • Forgetting the SSO bill. Single sign-on (SSO), the SAML standard for federated identity, and the SCIM standard for automated user provisioning are frequently sold as add-ons that double the contracted price on vendor LXPs. If your IT team requires SSO, get the SSO line item before you sign, not after.

A 30-minute audit before you commit

  1. Count your actual learners, hours per learner per year, and number of distinct courses you’ll run in year one. Write the three numbers down. If they’re less than 100 / 4 / 6, the LMS-vs-no-LMS conversation tilts toward “no LMS” hard.
  2. Open your most recent training content in whatever tool created it (Word, PowerPoint, Camtasia®). Imagine moving it into an LMS authoring environment. Write down the three things that would be hardest. If two of three are deal-breakers, the LMS choice changes — or the answer is “don’t move the content; deliver it where it lives now.”
  3. Ask three people who’ll administer the system (HR, ops, IT) what their existing workflow tools already are. If those tools cover seventy per cent of the LMS pitch already, you don’t need an LMS — you need to formalise the existing workflow.
  4. Get a one-page contract sample from the top vendor on your shortlist. Read the auto-renewal clause and the data-export clause. The first will surprise you on price; the second will surprise you on portability.

When to bring in a learning specialist

Where outside help saves an obvious mistake:

  • The decision is being driven by a vendor relationship rather than by a measured training problem — half a day with someone who’s bought and unbought several LMS systems usually surfaces the right shape.
  • The team is mid-migration from one LMS to another and the migration is bigger than expected — content portability questions need answering before the contract closes.
  • The training problem is genuine but the audience isn’t “self-paced module learners” — it’s “managers who need to coach their team better.” That’s instructional design, not LMS shopping, and they’re different jobs with different deliverables.

Before the next vendor demo, do the 30-minute audit above and walk into the meeting with the three numbers — learner-hours, content shape, and audience — written down. The pitch lands very differently when the buyer has already done the math the demo isn’t structured around. The system that fits the actual training problem isn’t always the platform with the best demo; it’s the one that matches what those three numbers describe.

Last reviewed May 17, 2026.