Corporate Learning Design Infrastructure
Design. Build. Deliver. Improve.
BLX connects Learning Design, production, operations and evaluation for digital learning in one end-to-end LXMS.
From needs and learning objectives through design and production to delivery, usage data and continuous improvement.
Managing digital learning
AI can speed up content creation, but maintaining digital learning over time still creates avoidable work. Learning objectives, audiences and design decisions are often disconnected from the content that learners actually receive. Storyboards, review comments, assets, exports and usage data sit in separate systems, while approvals happen by email, PDF or chat and are difficult to trace.
This is particularly true of existing SCORM packages. Even a minor technical correction can require another export, upload and manual LMS test for every language version. Teams are left with parallel versions and may struggle to establish their origin, approval status and which one is current.
The challenge is operational, not merely technical. Teams create and publish digital learning but often lack a systematic way to maintain, review, translate, update and improve the underlying content.
A lifecycle from need to improvement
Design, production and operation interlock
Digital learning products do not unfold their value in a single production step. Needs, learning objectives, activities, assessments, review, production, delivery and evidence form a coherent work and improvement process.
- Need – clarifying needs and framework conditions
- Objectives – Formulating observable learning goals
- Activities – designing suitable learning activities
- Assessments – considering evidence and evaluation
- Review – examine professional and didactic quality
- Production – implementing content in a controlled manner
- Delivery – ship released versions
- Evidence – Using and evaluating learning outcomes
- Improvement – transferring findings to the next version
LXMS and Product Building Blocks
What makes the LXMS from BLX better
The LXMS manages learning content as version-controlled assets. Each asset remains connected to its audience, learning objectives, structure, variants, releases, usage data and improvement cycles.
The focus shifts from exporting individual SCORM packages to managing learning content throughout its lifecycle. Design, production, review, localisation, delivery and analytics all work from a single source of truth.
A change is no longer an isolated file operation, but a traceable update to a defined content version.
Existing SCORM content does not automatically require migration. The LXMS first shows what is available, what can remain in use, which text, media and variants need attention, and where migration would add real value. Teams can then decide based on condition, risk and benefit rather than treating migration as the default.
The LXMS complements the existing technology landscape. An LMS can continue to manage courses, users, enrolments and certificates, while the LXMS manages the learning content itself.
From learning theory to learning experience
In BLX Designer, learning design is not a quality layer added at the end. It is a reviewable part of production. Learning objectives, capability references, activities, evidence and media decisions are recorded so that the relationships between them remain visible.
The framework combines capability-based design, measurable learning objectives, Understanding by Design, Cognitive Load Theory and Bloom’s taxonomy. These are not abstract references: objectives are checked for measurability, activities for alignment with the target level, evidence for completeness and complex sections for their cognitive load.
The resulting learning structure supports not only initial production, but also review, translation, updates, re-releases and evaluation.
Support in context
The Learning Companion is embedded directly in the LXMS module as part of the learner dashboard and navigation, rather than appearing as an external support tool. Guidance is available where it is needed: within the current module, section and progress state.
Depending on the situation, the Learning Companion can display states such as Ready, Active, In Plan, Note, New Note or Critical. These are not decorative labels; they summarise signals from progress, failed attempts, periods without progress, momentum and coach recommendations into a clear assessment of the current situation.
Learners do not need to interpret a dashboard. They receive direct feedback on whether they are progressing as expected, whether guidance may help and whether a specific next step is recommended.
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.
AI Assists. People Review and Decide.
Controlled assistance in the work process
AI can assist with analysis, structuring, variant formation and editorial preparation. It does not replace professional responsibility or didactic decisions.
Sources, suggestions, changes and approvals remain traceable in the respective working context. People examine the results and decide what is adopted and published.
From design intention to next improvement
Evidence Loop
Evaluation becomes reliable if the original learning intention remains connected to data from actual use. The Evidence Loop brings these perspectives together systematically.
- Design Intent – Goals, Assumptions and Planned Evidence
- Runtime Evidence – observable use and results
- Evaluation – comparison of intention and actual effect
- Improvement – prioritized changes for the next version
Continue existing learning products in a controlled manner
Make migration an informed decision, not a technical prerequisite
L&D teams rarely start from scratch. They already manage SCORM packages, video, PDFs, interactive activities and LMS course structures that cannot simply be replaced. This content often needs to remain available while teams make urgent corrections, translate it, meet new regulatory requirements or resolve technical issues.
Legacy Content Operations provides a structured way to manage this content. Its value goes beyond importing SCORM packages: the LXMS supports targeted patches, variants and translation management.
The inventory remains executable, but at the same time controllable: with inventory, status, review, patch capability, translation status, release logic and reference to usage signals. Based on this information, it is possible to make a targeted decision as to whether a learning offer should continue to be operated, patched punctually, localised, newly released or migrated to a new learning module in the LXMS. This makes migration a informed decision, not a technical start condition.
This includes the issue of provision. The imported SCORM packages only need to be imported once and then no longer exported. Using cmi5 or LTI-based delivery models, they can be provided centrally, tracked more accurately and better integrated into existing LMS structures. The technical basis for this is described in the section on xAPI, cmi5, LRS and LTI 1.3.
Legacy Content Operations as an efficiency lever
A gradual migration path for existing SCORM content
Legacy Content Operations is one important part of the wider LXMS lifecycle. Many organisations need to continue using existing SCORM content. An immediate, wholesale migration is often neither economical nor practical.
The LXMS provides a controlled intermediate step. Existing content is inventoried, managed, versioned, reviewed, translated and assessed for risk before teams decide what to retain, patch, localise, re-release, rebuild in native LXMS structures or replace.
The economic advantage lies in prioritisation. Modernisation becomes a series of decisions based on effort, benefit and risk rather than one large programme. Organisations can invest first where technical condition, regulatory requirements or usage data show the greatest need.
The use cases illustrate that SCORM is not only technically obsolete, but also structurally inefficient. A central LXMS offers significantly lower operating costs, fewer sources of error and shorter time-to-market cycles through reusability, central control, language-specific management and modular maintenance.
Experience the LXMS live
Functions and workflows for your learning portfolio
In a personal online session, we show the functions and workflows that matter to your learning portfolio.
Instead of walking through a generic feature list, we demonstrate a coherent workflow—for example, learning design and storyboarding, review and approval, legacy SCORM content, localisation, delivery or learning analytics.
The session takes 30–45 minutes and focuses on your subject-matter and technical questions.