BLX Designer as product proof
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.
From storyboard to digital learning module
Components as the smallest learning-design unit
The storyboard is a critical point of transition: the design becomes tangible pages, media, questions and activities. To maintain coherence, every component retains an explicit link to its learning objectives, activities and evidence.
BLX Designer brings together the storyboard, media requirements and interaction logic. Each section can record its objective, narrative, activity, format, duration, Bloom level, UbD stage, CLT strategy and evidence reference. Media are described and selected within the section rather than managed separately.
This is particularly important for multilingual or audience-specific learning content. Localisation may affect examples, screenshots, voice-over scripts, imagery, legal notices, terminology and interactions as well as text. BLX Designer keeps these requirements visible in the storyboard so that localisation does not become disconnected rework on a finished package.
This makes media information specific for each section, the selection of images, videos or H5P interactions remains traceable, license and source information is located in the right place, and the connection between outline, storyboard and blueprint remains controllable. Media thus appear as didactically based components of a learning activity and not as a subsequent illustration.
Quality assurance through review gates
Built into every stage of production
The BLX Designer works with clear transitions:
|
Gate |
Stage |
Test focus |
|---|---|---|
|
A |
After research, briefing and high-level concept |
Subject-matter basis, audience, learning objectives, capability framework, scope, language and regulatory requirements |
|
B |
Outline and storyboard |
UbD chain, Bloom level, CLT indicators, media fit, interaction logic, translatability and reusability |
|
C |
after analysis and blueprint |
Component structure, review status, xAPI/cmi5 references, release readiness, measurability and connection to the LXMS |
- Gate
A
- Stage
After research, briefing and high-level concept
- Test focus
Subject-matter basis, audience, learning objectives, capability framework, scope, language and regulatory requirements
- Gate
B
- Stage
Outline and storyboard
- Test focus
UbD chain, Bloom level, CLT indicators, media fit, interaction logic, translatability and reusability
- Gate
C
- Stage
after analysis and blueprint
- Test focus
Component structure, review status, xAPI/cmi5 references, release readiness, measurability and connection to the LXMS
Quality is built throughout production rather than assessed only at final acceptance. Each gate confirms that the content has a sound subject-matter basis, coherent learning design, reviewable editorial copy and a technically viable implementation.
An analysis dashboard for better decisions
Quality is visible
BLX Designer makes storyboard quality visible. Its analysis dashboard assesses whether sections are sufficiently defined and whether duration, activity types, formats and learning-design references are complete. It highlights the distribution of learning time, incomplete sections, coverage and readiness, and whether format, activity and target level are aligned.
The dashboard is an active part of the workflow rather than a separate reporting tool. It highlights and prioritises open issues, with corrections made directly in the relevant storyboard field.
For complex modules, this can reduce coordination substantially. Teams can review gaps, time budgets and learning-design coverage together instead of relying on subjective impressions alone.
Blueprint and implementation in the LXMS
A structured handover for digital learning content
After subject-matter and learning-design approval, BLX Designer generates a blueprint as the structured basis for implementation. It describes the planned module in a form that can be processed and implemented in the LXMS.
The blueprint contains more than a page structure. It carries forward the relevant learning-design references from the high-level concept, outline and storyboard, preserving the link between planning and implementation.
During implementation, BLX Designer creates module structures in the LXMS, selectively adds to or replaces existing structures, and turns storyboard decisions into editable components. The blueprint describes a defined content version, including its structure, media and learning-design references, review state, language and variant logic, and the information needed for delivery and evaluation.
Even with existing content, the blueprint thus becomes the basis for decision-making. An old SCORM or storyline course does not have to be blindly replicated. It becomes visible which parts can be adopted technically, which structure should be rethought, which media are reusable and which sections are better built natively in the LXMS.
This reduces the familiar disconnect between the design document and the production system. Teams no longer need to interpret changes manually from spreadsheets or presentations; a structured design process carries them through to implementation.
Iteration between design phases
Learning-design feedback during production
BLX Designer does not treat its design phases as a one-way sequence. Research, briefing, high-level concept, outline, storyboard, analysis and blueprint each produce a distinct output while remaining connected. If a later phase reveals an unclear objective, an overlong section, an unreliable source or an unsuitable interaction, the issue can be taken back to the relevant earlier phase.
This iteration is not an export mechanism; it is learning-design feedback within production. Every phase produces a reviewable result and tests whether earlier assumptions still hold.
The efficiency of the BLX Designer is not only due to faster text creation. The greater effect lies in fewer media breaks, less dual care and less unclear transfers between specialist concept, storyboard, media production, technical implementation and review.
A shared structure makes briefs easier to compare. Sources and existing content remain traceable, objectives become measurable earlier, and storyboards retain their connection to the concept because they belong to the same artefact chain. Media decisions are made in context, while review gates reveal gaps before they become costly to fix.
This is particularly relevant for organisations that maintain many learning products, regularly update them or deliver them in a multilingual manner. Then the BLX Designer not only reduces production time, but also coordination, translation, version clarification and re-releasing work.
The result is an iterative process: research informs the brief; the high-level concept shapes the outline; the outline shapes the storyboard; and storyboard data feeds the analysis. The analysis can send work back to any earlier phase. The blueprint is therefore both the final step before implementation and a practical check that the proposed learning architecture can be delivered consistently.
In practice, changes return to the right place: source gaps go back to research, storyboard gaps to the structure, and blueprint issues reveal where the concept or storyboard needs refinement. The process remains traceable through multiple iterations.
BLX Designer replaces a rigid waterfall with connected, reviewable phases. Each result can be tested, revised and fed back into the wider process, improving quality, speed and traceability.
AI support with subject-matter control
Assistance within the editorial workflow
BLX Designer uses AI as an assistant within the editorial workflow, not as a black box. It can summarise research, propose briefing content, structure high-level concepts, generate outlines, prepare storyboard sections, support review questions and classify evaluation results.
In existing projects, AI can also help analyse learning content by clustering topics, identifying duplication, suggesting learning objectives, flagging outdated passages and comparing language versions. For translation, it can produce initial drafts, check terminology and propose variants. Responsibility for subject-matter accuracy, legal acceptability and learning-design quality remains with the designated reviewers.
The controlled workflow is critical. Existing content remains reviewable and editable; generated outputs are stored as working artefacts; designated people retain responsibility for reviews and releases; and gates prevent premature handover to implementation. Prompts and templates follow the learning-design framework.
This allows productive use of AI without blurring professional responsibility. BLX Designer is particularly useful where structure, variant creation and consistency checks consume significant editorial and learning-design time.