This post is about the pros and cons of using a web-based emitter and API rather than a regular LMS. We’ve tried to fair, but ultimately, it’s up to you to decide if any of this works for you.

“Alright then, break it down for me.”

Here’s a list of the pros and cons for the web-based modules:

Web-Based Modules, Emitter and API

Pros:

  • $ – No cost per user, one time setup
  • Provides self-help training.
  • No sign-up process or complex courses and itineries.
  • No per-seat costs (so go big).
  • Predictable budget costs.
  • Short set-up time.
  • Low learning curve.
  • Very rich data collection possible (full LRS vocabulary and more).
  • Once it’s working, you can add other modules easily.
  • Use any backend for data analysis (even ChatGPT).
  • Typically seen as less intimidating to users.

Cons:

  • Not a structured course or syllabus.
  • Need to sign-in to modules or use a passkey to identify the learner.
  • Needs assistance from IT to set up.
  • Some tweaks to your StoryLine required.

“Wait a moment, those last three cons sound like we will need some technical help.”

Yes, that’s true! But actually, it’s quite a small ask. Once you’ve established an API, you can use it for any of your courses (i.e. it’s a one-time investment). The total time needed by someone developing a simple API is modest when compared to the monthly cost of an LMS. The set up time is usually no more than a couple of days.

However, if you’re looking to connect this API to your enterprise systems, then that raises a whole bunch of other issues to do with security, data, consistency, etc.

We don’t recommend taking that approach as this is intended to be a quick and simple solution that creates a significant amount of useful data which could be easily manipulated with a spreadsheet or other report software, not a replacement for an enterprise LMS.

OK, now let’s look at the LMS option:

Traditional Enterprise LMS

Pros:

  • User Management
  • Progress Tracking & Reporting
  • Certification & Compliance
  • Centralized Content Management
  • Integration with other enterprise systems
  • Notifications & Reminders
  • Scalability
  • Designed to handle thousands of users, multiple teams,
    departments, and use cases.

Cons:

  • $$$ – Cost per seat plus overhead
  • Complex and somewhat intimidating for users.
  • Not so good at self-service.
  • Often require someone to manage and maintain.
  • Learning curve for managers.
  • Learning curve for users.

Conclusion:
Obviously, no one size fits all! What is true, however, is that many projects fail to get off the ground because of the potential investment needed to set up and run an LMS. If you find yourself in that situation, then this approach might prove to be a scalable, effective and cost-efficient way to gather data about the efficacy and performance of your training modules. If you need compliance and a record of the learners’ activities, that is the only way outside of an LMS/LRS to achieve that.

Most importantly, it creates an opportunity for learners to self-service and use just the training that they need without engaging with a potentially intimidating LMS.

Read part six for a final conclusion.

Previous Sections of this Blog:
Part 1: “Why You Might Not Need an LMS After All”
Part 2: “Loads of Training Data Without an LMS”
Part 3: “What can you do with learning data?”

Upcoming Sections:
Part 4: “How to Implement a non LMS SCORM Solution”
Part 5: “Why You Might Want to Choose an LMS” You are here.
Part 6: “Conclusion – Cheap, Easy, Effective – Why Not?”

Before You Go, A Quick Feedback Loop

I’ll practice what I preach:

        • Was this post useful to you?
        • Did the stories help clarify the message?
        • What parts felt unclear or too abstract?

Reply with your thoughts — or better yet, tell me one small change you made after looking at your own assessment data. Because when we listen, we learn. And when we learn, we create eLearning that actually changes behavior, not just knowledge.