{"id":6654,"date":"2025-05-20T00:00:00","date_gmt":"2025-05-19T22:00:00","guid":{"rendered":"https:\/\/seriousfactory.com\/blog\/?p=6654"},"modified":"2025-08-20T16:22:37","modified_gmt":"2025-08-20T14:22:37","slug":"create-structured-e-learning-paths-with-the-sequence-block-of-vts-editor","status":"publish","type":"post","link":"https:\/\/seriousfactory.com\/blog\/en\/create-structured-e-learning-paths-with-the-sequence-block-of-vts-editor\/","title":{"rendered":"Create Structured E-Learning Paths with the Sequence Block of VTS Editor"},"content":{"rendered":"

Structure Your E-Learning Modules with the VTS Editor Sequence Block<\/h2>\n

In many e-learning, simulation, or serious game projects, the challenge isn\u2019t just about creating rich content, but also about organizing it in a clear, repeatable, and maintainable flow. The VTS Editor Sequence block<\/strong> answers precisely this need. Upon each activation, it triggers the next output (S1, then S2, etc.). Once the last output is reached, it loops back to the first. This lets you define a simple and reassuring learning cycle (e.g., brief > activity > feedback) without duplicating blocks or cluttering your scenario map. For a training manager or instructional designer, it’s a lever for standardization and quality that speeds up production.<\/p>\n

Why Use the VTS Editor Sequence Block<\/h2>\n

Bring Order Without Complexity<\/h3>\n

If you\u2019ve ever tried to enforce a strict step order, you know too many conditions can hinder clarity. The Sequence block in VTS Editor<\/em> restores clarity. It removes undesired branching when guided progression is needed, while maintaining the flexibility of a controlled loop. The same cycle can be replayed as many times as necessary (e.g., demonstration > practice > debrief). For the learner, this repeated structure creates mental cues that strengthen memory retention, supported by spaced practice and active recall.<\/p>\n

To learn more about the efficiency of spaced practice and active recall, refer to these academic studies: Testing effect and active recall (Rowland, 2014)<\/a> and Spacing effect (Cepeda et al., 2008)<\/a>.<\/p>\n

Learning Objectives and Business Benefits<\/h3>\n

Pedagogically, the sequence paces the information > action > feedback cycle\u2014 a key condition for long-term retention. Adding a badge at the end of the sequence or displaying progression can boost motivation. On the business side, you reduce block duplication, simplify maintenance, and standardize workflows. Your team can adapt \u201csequence templates\u201d for different topics (compliance, safety, onboarding, sales) and reuse them across projects, thus reducing production time<\/em>. See how our clients apply these approaches in our client cases<\/a>.<\/p>\n

How the VTS Editor Sequence Block Works and Use Cases<\/h2>\n

Sequential Triggering and Looping<\/h3>\n

The block follows a fixed order: each activation triggers the next output. Upon reaching the last, it loops back to the first and can repeat as needed. Example with 4 stages: Intro > Instructions > Exercise > Debrief. The fifth activation returns to Intro\u2014 ideal for training, reinforcement, or microlearning. For instance, you can loop back to the sequence after a debrief if the score is too low and allow progression to another scene once a threshold is reached.<\/p>\n

Choosing Between Sequence, Counter, Random, and Switch<\/h3>\n

\u2022 Sequence: enforces a fixed order.
\u2022 Counter: limits attempts before offering a plan B (e.g., 3 tries, then help).
\u2022 Random: introduces variety if you want to change cases at each session.
\u2022 Switch: routes content based on a variable (e.g., learner\u2019s selected level).
Combine them as needed: a Sequence for structure, spiced with Random for varying the \u201cExercise.\u201d<\/p>\n

Practical Use Cases<\/h3>\n

\u2022 Onboarding: Company culture > Key tools > Usage scenario > Evaluation to ensure a consistent experience.
\u2022 Compliance: step-by-step process with checks at each milestone.
\u2022 Safety: training ritual (video, guided practice, timed practice, debrief).
\u2022 Sales: progressive quiz series with differentiated feedback and final badge if the overall score crosses a threshold.<\/p>\n

Combining the Sequence Block with Other Blocks<\/h3>\n

The power of VTS Editor<\/a> comes from smart combinations. Examples: a \u201cQuiz\u201d in S3 to measure, a \u201cMessage\u201d in S2 for instructions, \u201cSpeak\u201d + \u201cEmotion\u201d in S4 to humanize feedback, \u201cVideo\u201d or \u201cSlideshow\u201d in S1 to set context. Add \u201cProgress\u201d to display 25\/50\/75\/100%, \u201cScore\u201d to highlight effort, and \u201cBadge\u201d to mark completion. Insert \u201cClickable Zones\u201d or \u201cSet Interaction\u201d between outputs without losing the thread: the VTS Editor Sequence block<\/strong> remains your main backbone.<\/p>\n

Step-by-Step Method with the VTS Editor Sequence Block<\/h2>\n

Map the Learning Journey<\/h3>\n

Start with a simple storyboard. For each step, ask two questions: what behavior should follow this step? How will we measure it? Examples: S1 sets the context with a Slideshow and voiceover; S2 provides instructions using a Message and media; S3 prompts action via a Quiz or Clickable Zone; S4 delivers feedback (based on score) with a Speak block, Emotion, and Character Animation; S5 ends the cycle updating Progress, awarding a Badge, and optionally looping to S1.<\/p>\n

Configure the Sequence and Chain the Outputs<\/h3>\n

Create the block, then link each output to a relevant \u201cpivot\u201d block for each step. Instantly, your chart becomes a readable backbone: S1_Intro, S2_Instructions, S3_Activity, S4_Feedback, S5_Transition. Group them for clarity, add Notes to document logic (success criteria, thresholds, variables), and visually align steps to assist review.<\/p>\n

Manage Returns and Controlled Navigation<\/h3>\n

When a learner exits the flow via \u201cjump to another scene\u201d (clickable zone, media click, countdown, or menu), bring them back to the right spot. Place a Checkpoint at the entry of each key step. Activate \u201cSave Return Point\u201d in any block that causes a jump, then use the Return block set to \u201cLast Return Point\u201d to bring them back exactly. This discipline prevents dead ends and unintended loops.<\/p>\n

Measure Progress, Time, and Success<\/h3>\n

The Progress block indicates advancement and completion\/success status per your criteria. This is useful for SCORM export and monitoring in VTS Perform<\/a>. Add \u201cSend Data\u201d where real-time reporting is needed (end of a step or sequence). If time is part of the skill (e.g., urgency, customer service), deploy a Countdown. Choose an appropriate display (visible or hidden timer) and clear routes upon expiration.<\/p>\n

Effective Assessment and Feedback<\/h3>\n

Feed a \u201cScore\u201d per skill (e.g., safety, communication, quality) rather than a single global score if stakeholders desire detailed diagnostics. Then, check these scores using \u201cCheck Score\u201d to allow or block progression, award an excellence badge, or redirect to targeted reinforcement. For feedback, diversify formats: explanatory Message, Speak embodying a mentor\u2019s reaction, Emotion\/Character Animation, or background media showing consequences. To understand the impact of feedback on learning, see Hattie & Timperley (2007)<\/a>.<\/p>\n

Validate and Test the Flow<\/h3>\n

Before publication, test the standard flow and variations. Open the Variables State window to check your flags, scores, and counters. Add temporary Messages at each step’s output to confirm activation. Verify media (1280\u00d7720 format recommended), audio levels, subtitles, and accessibility (zoomable images). If the sequence is replayable, use \u201cReset\u201d before a Quiz or Counter to start cleanly each loop.<\/p>\n

Best Practices, Customization, and Performance<\/h2>\n

Pacing and Learner Experience<\/h3>\n

An effective sequence alternates between exposure, action, and feedback. The \u201cWait\u201d block adds pauses for dense screens. Subtle background audio and sound effects (via \u201cSound\u201d block) guide attention. Use \u201cGaze\u201d to direct character eyes toward a point of interest at the right time. For narration, combine \u201cSpeak,\u201d \u201cEmotion,\u201d and \u201cCharacter Animation\u201d to humanize guidance. Keep gamification light but visible: in-game scoring, badges at key checkpoints, and a progress bar.<\/p>\n

Customization with Variables and Media Variables<\/h3>\n

Variables (INTEGRAL plan) take you to the next level. Route content by profile (technician, manager), vary question order, and store choices to adjust upcoming steps. Media variables eliminate duplication: a Clickable Zone can display different images based on a variable (e.g., case A, B, or C), decided by a prior response. Your graph stays leaner, and easier to maintain.<\/p>\n

Reusability and Simplified Maintenance<\/h3>\n

Turn your mini-sequence into an internal template. Save the Instruction > Activity > Feedback structure in a Group, then turn it into a Function. With the \u201cCall Function\u201d block, invoke it wherever needed\u2014no copy-pasting. Every improvement instantly benefits all scenarios. For repeat training, place a \u201cReset\u201d just before a Counter or Quiz to ensure a clean experience each time.<\/p>\n

Accessibility, Multilingual, and Compliance<\/h3>\n

Enable subtitles, use high-contrast backgrounds for Messages and Foreground, offer zoomable images for diagrams. If your project is multilingual, the \u201cLanguage Condition\u201d block directs to the correct version. For tracking, export as SCORM to your LMS or deploy via VTS Perform<\/a> for detailed stats (progress, scores, badges). The Progress and Score blocks let you decide what to track, and when. To reduce cognitive load, refer to Cognitive Load Theory<\/a>.<\/p>\n

Common Mistakes and Quick Diagnostics<\/h3>\n

Sequences too long without feedback can tire learners. Break into sub-sequences and insert frequent micro-feedback. Avoid logical conflicts by mixing Sequence (fixed order) and Random (chance) only with clear intent. Master your returns: use a Checkpoint at every milestone, \u201cSave Return Point\u201d on jumps, and \u201cReturn\u201d via \u201cLast Return Point\u201d mode. For performance, stick to 720p video, monitor lingering background audio, and test on all targets (desktop, mobile, web, or VTS Player). If in doubt, rely on the Variables State window and temporary debug Messages.<\/p>\n

Implementation Checklist for the Sequence Block<\/h2>\n