The Blueprint for Modern Learning: Why cmi5 Is Reshaping the Future of LxD
- marleegeiger
- Jun 25
- 3 min read
Pop-ups are out. Portability, flexibility, and real learning data are in. Here's how cmi5 is revolutionizing digital learning—quietly, powerfully, and now.
I never think about what happens on the backend of an LMS when a course launches, and I would bet you don’t think too much about it either. Why would we? We click, and it launches. Progress bars slowly get filled, and somewhere, a report is marked completed.
It sounds simple, but it’s built on a foundation designed over 20 years ago. Back when, web pages were static and phone apps weren’t even a bubble in Steve Jobs’ mind.
But that foundation is cracking.
And in its place, quietly and carefully, a new framework has emerged: cmi5.
It’s not SCORM, and it’s not just xAPI. It’s smarter and more expansive than SCORM learning. It’s opening the doors.
The Core of cmi5: A New Kind of Launch
When you get down to it, cmi5 is going to feel a lot like SCORM. A course is still launched from an LMS, activities are still assigned, and completions are still tracked.
But underneath it all, everything is different.
Instead of relying on browser scripts and rigid data models, CMI5 courses utilize xAPI, which tracks experiences across platforms, devices, and contexts.
The result?
cmi5 preserves the assignable structure LMSs need, while giving designers the freedom to build learning that happens anywhere.
A course might be a traditional eLearning module.
Or it might be a VR simulation.
Or an offline mobile app that syncs once the learner reconnects.
From the LMS's point of view, they’re all just cmi5 Assignable Units. Modular pieces of a bigger learning journey.
How cmi5 Works (Without the Jargon)
When a learner clicks Start Course, the LMS launches the Assignable Unit (AU) and passes along a few key things:
An authentication token (so the content can securely send back data)
A session ID (to group learning records together)
Rules for what counts as “completion” and “success”
The content then communicates back to the LMS (via an LRS) by sending xAPI statements. Structured, timestamped reports of what happened.
For example:
"Alex launched Scenario 3." "Priya answered Quiz 2 incorrectly." "Jordan completed Module 5 successfully."
At the end, the content reports whether the learner completed and/or passed the AU, based on clear rules.
Unlike SCORM, there isn’t a fragile JavaScript frame to manage or pop-up blockers to worry about. Just clean, secure, portable communication.
Why This Matters for Learners
For a learner, cmi5 shouldn’t be visible. It shouldn’t even change their experience.
Courses can launch natively inside apps, or experiences can be offline-first.
And because cmi5 uses xAPI, what gets recorded is so much richer than just a Pass or Fail. We can track interactions, decision points, mistakes, etc., all without locking learners into a rigid browser environment.
For the first time, both learning data and learning experience can live and communicate with each other.
Learning isn’t something we take. It’s something we live, and cmi5 captures all the messy learning that happens in the real world.
The New Blueprint
If SCORM were a set of paved roads, cmi5 is a blueprint for an entire city.
You still have streets (modules).
You still have traffic laws (completion rules).
But now you have highways, bike paths, public squares, and VR portals.
It’s the infrastructure that acknowledges how people actually learn in the modern world across devices and locations. All the formal and informal ways.
cmi5 is about designing richer structures that feel more natural and human. That feels like they can last.
Because learning doesn’t happen in a pop-up window.
It happens everywhere.
And now, finally, our technology can keep up.
Next in the series: cmi5 vs. SCORM vs. xAPI: Choosing the Right Road for Learning Design
Comments