Learning Analytics
Evaluating use and impact
The basis for continuous improvement
Learning analytics is built into the learning experience rather than added after the content is finished. Dashboards can combine interaction events, video tracking, navigation data, progress and completion status.
Authors can see whether activities are clear, whether media appear in the right context and whether learning journeys work as intended. Course leaders can identify where participants need support, while content owners gain evidence about use, progress, engagement and potential bottlenecks.
Typical evaluation questions are:
- Which parts of a video are watched in full, skipped or abandoned?
- Which activities lead to repeated attempts or long completion times?
- Where do learners drop out, pause unexpectedly or show little activity?
- Which interactive formats generate strong engagement?
- Which content should be revised, simplified or differentiated?
This perspective is particularly valuable for Legacy Content Operations. Usage data can show which existing content works reliably, which sections lead to drop-outs, which packages are rarely used and where modernisation would have the greatest effect. Analytics can therefore guide priorities for legacy content and migration as well as improve new modules.
The LXMS supports a continuous improvement cycle: teams publish content, evaluate how it performs in practice and use the evidence to refine it.
Content analytics and quality management
Evidence for maintenance, modernisation and priorities
SCORM reporting is often limited to completion, scores and basic progress. That is rarely enough for sound operational decisions. Teams need to know which content is used, where learners drop out, which activities cause difficulty and which sections need revision.
The LXMS relates usage data to content structure, activities and releases. This shows which modules and variants work reliably and where revision is worth the investment. Analytics becomes a basis for maintenance, modernisation and prioritisation, not simply reporting.
From learning data to evidence
xAPI, cmi5, LRS and LTI 1.3
The actual strength of the LXMS lies below the surface. Learning activities are recorded as evaluable events via xAPI and cmi5. This can include answers to questions, interactions in videos, editing time, repetitions, breakpoints, scores, progress, notes or annotations in PDF.
A Learning Record Store (LRS) holds this data for analysis, dashboards and reporting. It shows how learners engage with content: which activities they repeat, where they stop watching a video, which sections take unusually long and which interactive elements they use.
The integrated LRS and LTI 1.3 connector extend these capabilities. Native LXMS content can run within an existing LMS without being shipped as a fixed package. Existing SCORM content can remain operational while new delivery and tracking models are introduced gradually.
This is not an either-or architecture. The LMS remains the organisational system for courses, participants and certificates. The LXMS manages the learning content itself—its structure, storyboards, variants, reviews, delivery and detailed usage data.