How to Use an LMS: A Practical Guide for Instructional Designers

Using a learning management system (LMS) as an instructional designer comes down to five core tasks: creating a course, adding users, enrolling them, uploading a SCORM or xAPI package, and tracking completions. You can learn all five in an afternoon, and they matter more than most new designers expect. When I surveyed more than 100 hiring managers for the Devlin Peck Instructional Design Hiring Manager Report, 50% named LMS skills one of the top three technical skills they want instructional designers to have on day one.

The LMS is the last mile of how to design eLearning. After the analysis, the storyboards, and the development, someone has to get the course in front of learners and prove they finished it. That someone is often you. This guide walks through each task in plain, tool-agnostic terms, shows you where to practice for free, and covers a few gotchas I've hit doing this work myself.

What Is a Learning Management System?

A learning management system is software that hosts learning content, controls who can access it, and tracks what learners did with it. Slide decks, videos, eLearning courses, assessments, live session records: if an organization wants to deliver it and report on it, it lives in the LMS.

For an instructional designer, the LMS is a delivery and reporting layer, not a design tool. You do the creative work elsewhere and use the LMS to publish, assign, and measure. That distinction matters because most guides to this topic are written for the people buying the system, not the people using it. If you're still getting oriented on the content side, start with what eLearning actually is and come back.

Nearly every employer you'll work for runs one of these platforms. The LMS market reached $30.51 billion in 2026 and is projected to hit $54.86 billion by 2031, according to Mordor Intelligence's LMS market report. This is not a niche tool you might encounter...it's standard infrastructure.

LMS vs. authoring tool vs. LRS

You build courses in an authoring tool, you deliver and track them in an LMS, and a learning record store (LRS) is a database that stores xAPI data. Storyline 360 and Rise are authoring tools; TalentLMS and Moodle are LMSs; an LRS usually sits behind the scenes, either inside the LMS or as a separate product. If you're mapping out your toolkit, my guide to instructional design software and authoring tools covers the build side in depth.

Is an "instructional management system" the same as an LMS?

Usually not. In K-12 education, "instructional management system" typically refers to district-level software for managing curriculum standards, instructional materials, and student data. It's an administrator's tool, not a course delivery platform. This guide covers the corporate LMS: the system a company uses to deliver and track workplace training. If you're a school administrator researching district systems, the tasks below won't map cleanly to your world.

Why Do Instructional Designers Need LMS Skills?

Because implementation is part of the job. Most corporate ID roles expect you to upload a course, enroll the right people, and pull a completion report without asking IT for help. Half of the hiring managers in my survey put LMS skills in their top three, and job postings back this up: "experience with an LMS" shows up constantly, even for roles that are mostly design work.

Think of it as the Implementation phase of the design process. A course that never makes it into the LMS correctly, or that reports "incomplete" for learners who finished it, is a failed project no matter how good the design was. The tasks are not hard. They're just unknown until you've done them once, which is exactly why practicing them before an interview pays off.

What Are the Core LMS Tasks Every Instructional Designer Should Know?

Five tasks cover the vast majority of what an instructional designer does inside an LMS: create a course, add users, enroll them, upload a SCORM or xAPI package, and track completions. Every platform handles the details a little differently, but the pattern is the same everywhere.

I recorded a walkthrough of these exact tasks in TalentLMS back in 2021. TalentLMS has redesigned its interface since then, so treat the video as a demo of the workflow rather than the current screens. The steps below are written to work in any LMS.

Create a course and organize content

1. Create a new course and give it a clear name, description, and category.
2. Add your content: a SCORM package, videos, PDFs, built-in quiz modules, or a mix.
3. Set the completion rule (complete all units, pass an assessment, or both).
4. Set the course's visibility or publish status so learners can actually see it.

Where this varies: some platforms call courses "learning paths" or bundle them into curricula and programs. The naming changes, but the create-add-configure-publish flow doesn't.

Add users and set roles and permissions

1. Add users manually, import them from a CSV file, or (in enterprise systems) sync them from an HR system.
2. Assign each user a role: learner, instructor, or admin.
3. Check what each role can see and do before handing out access.

Where this varies: enterprise LMSs often provision users automatically from an HRIS, so you may never add users by hand. Role names and permission granularity differ a lot between platforms.

Enroll users in a course

1. Open the course and add individual users or entire groups.
2. Set due dates if the training has a deadline.
3. Confirm the enrollment notification settings, so learners actually find out they've been assigned something.

Where this varies: some systems push courses to learners (assignment), others let learners self-enroll from a catalog, and many enterprise platforms use automated rules ("everyone in the Sales group gets this course"). Know which model your LMS uses before you promise a stakeholder that "everyone has it."

Upload a SCORM or xAPI package

This is the task that separates people who have actually done LMS work from people who have only read about it.

1. Publish from your authoring tool with the right settings: choose the standard (SCORM 1.2, SCORM 2004, or xAPI) and, critically, the completion trigger. "Slides viewed" means finishing X slides marks the course complete; "quiz result" ties completion to a passing score; trigger-based completion fires when a specific condition you built is met.
2. Take the zipped output file and upload it to the course. Don't unzip it. The LMS reads the package as-is.
3. Launch the course as a test learner and click through to the end.
4. Verify that the LMS recorded the completion and score you expected.

Track completions and run reports

1. Open the course or user reports to see who's enrolled, in progress, and completed.
2. Understand the status values: "completed" usually means the completion rule was met, while "passed" means an assessment score cleared the threshold. A learner can be 'completed' without passing, and stakeholders will ask about the difference.
3. Export the report (CSV or Excel in most systems) for whoever requested the training.

Where this varies: reporting is where LMSs differ the most. Some give you dashboards and scheduled email reports; others give you a raw export and wish you luck.

How Do SCORM, xAPI, and cmi5 Work in an LMS?

SCORM, xAPI, and cmi5 are the packaging and reporting standards that let a course built in any authoring tool talk to any LMS. Here's the practical version:

SCORM is the legacy default and still the safest bet. It reports completion status, score, and time spent, and virtually every LMS supports it. Its weakness is that this thin slice of data is roughly all it can carry.

xAPI is more flexible. It sends "actor-verb-object" statements ("Maria completed the safety module," "Maria answered question 4 incorrectly") and can track learning beyond the LMS entirely. The catch: xAPI data needs a learning record store, and in my experience many LMS vendors implement their LRS poorly, while plenty of organizations don't run one at all. So xAPI's promise often outruns its reliability inside a typical LMS setup.

cmi5 combines the two: xAPI's richer data with SCORM-style launch and completion rules. Support is growing, but check whether your specific LMS handles it before you publish to it.

The practical takeaway: publish to SCORM 1.2 or 2004 unless your organization has a working xAPI pipeline and a reason to use it.

One gotcha from my own xAPI work in Storyline: when you add a Storyline variable inside the xAPI statement editor, the editor throws an error unless you wrap the variable in quotation marks. I got hung up on this myself, convinced I'd done everything right, until some trial and error revealed the quotation-mark requirement. If you hit that error, this is almost certainly why.

Before you upload anything to a real LMS, test the package in SCORM Cloud from Rustici Software. It's the industry-standard testing environment, and the free trial tier (up to 3 courses and 5 GB of storage as of 2026, per Rustici's published plans) is plenty for checking how your package launches, tracks, and completes.

Which LMS Should You Practice With?

Any LMS with free access works, because the five core tasks transfer between platforms. TalentLMS is the fastest to start with; Moodle shows you the messier, enterprise-style side; SCORM Cloud is for package testing rather than full admin practice.

Platform	Free access	Best for	Source
TalentLMS	Free plan: up to 5 active users and 10 active courses, no expiry	Your first practice reps; clean, fast setup	TalentLMS help center
Moodle	Free and open source; self-host it or use the hosted demo	Seeing an enterprise-style, deeply configurable system	Moodle project
SCORM Cloud	Free trial tier: up to 3 courses, 5 GB storage	Testing how SCORM/xAPI packages launch and track	Rustici Software

I checked the free-tier details in mid-2026. Limits change, so confirm on each vendor's site before you build your practice plan around them.

My advice: run the same five tasks in at least two of these systems. The first time through, you're learning the platform. The second time through, you're learning the pattern, and the pattern is what you'll carry into every LMS you touch for the rest of your career.

Learn the pattern, not the platform: the five core tasks transfer to every LMS you will ever touch.

How Do You Practice LMS Skills Before the Job Interview?

Run the full loop once, end to end, and then be ready to describe it out loud: build a tiny course, publish it from your authoring tool, upload it, enroll a test user, and pull the completion report.

1. Build a tiny course

   Two or three slides in your authoring tool is enough. This is an LMS rep, not a portfolio piece, so don't polish it.

2. Publish for the LMS

   Publish to SCORM 1.2 or 2004 and set the completion trigger deliberately. Know which trigger you chose and why, because interviewers may ask.

3. Upload and enroll a test user

   Create the course in your practice LMS, upload the zipped package, add a second user account, and enroll it.

4. Complete the course as the learner

   Log in as the test user and click through to the end. Notice what the learner experience feels like, including anything you'd want to warn a stakeholder about.

5. Pull the completion report

   Confirm the completion and score recorded correctly, then export the report. Now you've done the whole job, not just the design half.

In an interview, "I set up a TalentLMS environment, published a SCORM package from Storyline with a quiz-based completion trigger, enrolled a test user, and verified the completion in the reports" beats "I'm a fast learner" every single time. It's specific, it's verifiable, and most career changers can't say it.

One caution while you're practicing: your portfolio projects do not belong behind an LMS login, and I wouldn't publish them through Articulate Review with its sidebar either. I host the published HTML5 package directly on a web server, like Amazon S3, so anyone with the link sees a clean, full-screen project. devlin.host, the free HTML project hosting that I offer to the community, exists for exactly this, and plenty of aspiring IDs use it for their portfolio sites and projects.

If you want structure and feedback while you build these skills, this is what we do at Peck Academy, my licensed career school for people transitioning into instructional design. Students learn ID theory, Storyline 360, and AI skills, they build a flagship portfolio project with extensive feedback, and yes, we teach them how to upload their eLearning projects to an LMS, because hiring managers keep telling us it matters.

Can You Deliver AI Practice Simulations Through an LMS?

Yes. Modern AI simulation tools package as SCORM or xAPI content, so a conversation practice sim can sit inside a Storyline or Rise course, or directly in the LMS, and report back like any other module.

This is what I build now. devlin.ai, my company, turns a plain-English description of a scenario into a working text or voice conversation simulation. It embeds in Storyline, Rise, or any LMS, and the AI evaluation, full transcripts, and scores report back to the course through SCORM and xAPI. If you're an aspiring ID or building a portfolio, the Starter plan is $9/month ($6/month paid annually).

I'll add one observation from 2026: some clients are starting to use devlin.ai itself as the system of record for practice, bypassing the LMS entirely. SCORM only carries a thin slice of data back, and these teams want full transcripts, performance over time, and a clear view of which skills learners struggle with versus excel at. Custom xAPI could deliver much of this inside an LRS in theory, but as I mentioned above, shaky LRS implementations make it unreliable in many environments. The LMS is still where most training lives; it's just no longer the only place rich learning data can live.

If you design scenario-based learning, try this firsthand. Describe a conversation your learners need to practice, test the simulation it builds, and keep in mind that this same sim can then be embedded in a course and tracked through your LMS.

Frequently asked questions

Is Google Classroom an LMS?

Yes, Google Classroom is an LMS, but a classroom-oriented one built for teachers managing assignments and students. Corporate instructional design roles use workplace platforms like TalentLMS, Docebo, Cornerstone, or Moodle, so practice on a corporate-style system if a corporate role is your goal.

What is the difference between an LMS, a CMS, and an LCMS?

An LMS delivers training and tracks learners. A CMS (content management system) manages website content and has nothing to do with learner tracking. An LCMS combines content authoring and delivery in one platform, though in practice most teams still author in a dedicated tool and deliver through an LMS.

How long does it take to learn an LMS?

The five core tasks (create a course, add users, enroll them, upload a package, run a report) take about an afternoon to learn in a free sandbox. Mastering a specific platform's quirks, automations, and reporting takes weeks on the job, but the core concepts transfer immediately.

Do all LMSs work the same way?

The tasks are the same, but the interfaces and details are not. Every platform handles the same create-enroll-upload-report pattern, but specifics like SCORM user identification differ enough that a package can behave differently from one LMS to the next. Always test in the target system before launch.