Split a training module when it contains learning objectives that people can use or practise separately. Keep dependent steps together when separating them would remove necessary context. Plan each lesson around one useful task or decision, with the explanation, example and check needed to support it. Runtime follows that purpose; a shorter video is not automatically a better lesson.
Find the learning objectives before you cut the footage
Start with the current script and source material. Mark the tasks, decisions and questions it covers, then write an observable objective for each potential lesson. “Explain the new CRM” is a broad subject; “Create a contact and check for duplicates” describes an action that a learner can practise.
CDC's learning-objective guidance, developed for public-health training, recommends clear, measurable objectives to guide content and assessment. Applying that planning principle to a corporate series is an editorial recommendation, not evidence that a particular video length improves performance.
Group objectives that depend on the same context. Do not split a demonstration midway through a safety-critical sequence just to make each file the same duration. Where a learner needs the full sequence, keep it together and consider chapters or supporting reference material.
Worked example: split one CRM module into focused lessons
This hypothetical example starts with a module covering sign-in, contact creation, opportunity updates and escalation. The proposed lessons are a planning template, not a Probbit client result.
| Lesson | Observable objective | Keep or show | Suggested check |
|---|---|---|---|
| Access and help | Find the approved support route for an access problem | Current sign-in and help screens | Locate the correct help route |
| Create a contact | Enter the required information and check for duplicates | One complete workflow in a test account | Complete a sample contact task |
| Update an opportunity | Choose the correct stage for a stated situation | Approved stage definitions and a worked example | Select a stage and explain the choice |
| Escalate an exception | Identify when to stop and contact the process owner | A realistic exception and the approved escalation route | Decide the next action in a scenario |
A contact-creation demonstration should still show the full action, including confirmation. It should not depend on a detail hidden in a different lesson. Where one lesson must come first, state the prerequisite in the series map and at the start of the lesson.
For a product and systems training series, verify screens against a current test environment. Use sample records and remove personal or customer data from captures.
What belongs inside each lesson?
Give each lesson a clear promise, enough context to orient the learner, one complete example or demonstration, and a relevant next action. Use a title that someone can find again, such as “Update an opportunity stage,” rather than “Part 4.”
A scenario question can check a decision. A practice task can check whether a learner can use a system. A reminder card can support later reference. Choose the activity to fit the objective instead of adding the same quiz format to every clip.
For an onboarding video programme, organise access by the learner's stage: before day one, week one and role-specific follow-up. For a policy series, separate topics only where the policy owner confirms that the necessary context remains clear.
How short should a microlearning video be?
There is no universal duration that makes a lesson effective. Remove repetition and production filler, but retain the steps and explanation required for the task. Test a draft with representative learners and ask where they lose context or need to replay a section.
Wistia's 2026 video report analyses viewing on its own platform and shows that engagement varies with video length, format and industry. It also notes that longer educational content can retain attention. Those are viewing observations, not proof that a fixed three-to-seven-minute rule improves workplace learning or task performance.
Use engagement data to find possible friction, then check whether the learner can answer the question or perform the intended task. Completion and watch time do not replace that check.
Package and measure the series deliberately
Decide whether learners need a complete pathway, independent reference lessons or both. Then agree how lessons launch, resume, report progress and contribute to any overall completion rule.
Lesson-level tracking depends on the package design, LMS implementation and reporting configuration. It does not follow automatically from choosing SCORM 2004, xAPI or another standard. Ask the LMS administrator to test the actual package for the behaviours and reports you need.
- Confirm the launch order, prerequisites and whether learners can return to one lesson independently.
- Define what completion means for each lesson and for the whole series.
- Test the records produced by completed, interrupted and resumed attempts.
- Check captions, keyboard controls, readable text and playback on the devices employees will use.
- Agree how replacement lessons affect existing assignments and completion records.
Compare the full scope of a split and an intact module
A series may require additional openings, captions, translations, assessment items, approvals and package tests. It may also let you update one changed workflow without revising unrelated lessons. The balance depends on the source material, reuse and delivery requirements.
Compare proposals using the same assumptions about lesson count, languages, review rounds, editable files and LMS testing. Do not assume that more files always cost more, or that shorter files always reduce the budget. Ask how the proposed scope changes the work.
A continuous procedure or story may work better as one video with chapters. A searchable set of independent tasks may work better as a series. The useful decision is how the audience will learn and revisit the content, rather than which option produces more clips.
Plan updates as a series, not a folder of exports
Keep a register linking each lesson to its objective, source version, reviewer, language files and delivery location. When one process changes, check its prerequisites and cross-references as well as its own scenes. A local edit can affect another lesson that assumes the old workflow.
Bring an existing script or module to a Probbit consultation. Our microlearning video series solution provides a starting point for agreeing the lesson map, production scope, review responsibilities and delivery tests before rebuilding the library.