Diorysos
Short answer
Build each module around one task and one decision, keep it between three and seven minutes, and make it usable on a phone in a noisy place with gloves on. End with a question that makes people apply the rule, then bring the key point back a few days later. Microlearning works well for refreshers and procedures. It does not replace initial certification or hands-on training.
A maintenance technician finishes a night shift at 6 a.m. A line supervisor has twelve minutes between the safety briefing and the first job. A drilling crew rotates every two weeks and spends the first day catching up on changes. None of these people will sit through a 45-minute module, and nobody should expect them to.
This is where microlearning earns its place. Done well, it fits into the gaps of a working day and keeps procedures fresh. Done badly, it is a long course cut into slices, and people notice. Here is how we design it for shift-based teams in aviation, oil & gas and manufacturing.
What counts as microlearning
Microlearning is a short, self-contained lesson that helps someone do one specific thing better. The length is a consequence, not the goal. A five-minute lesson that covers three unrelated topics is not microlearning; it is a short course that nobody will remember.
A useful test: can you write the purpose of the module as one sentence that starts with a verb? "Complete a pre-entry gas test in the right order." "Choose the correct extinguisher for an electrical fire." If you need two sentences, you probably need two modules.
Seven design rules for shift-based teams
1. One task, one outcome
Pick a single task and the decision that matters most within it. Everything that does not help with that decision goes into the reference document, not the module.
2. Open with the situation, not the policy
Start where the learner will be when they need this: "You arrive at the tank. The permit is signed but the standby person has not arrived." People pay attention to a situation they recognize. They skim a paragraph that starts with "The purpose of this procedure is".
3. Aim for three to seven minutes
That is long enough for a short scenario and a check, and short enough to finish during a break. If a topic needs more, split it into a sequence and let people take the parts on different days.
4. Design for the real environment
- Large tap targets that work with gloves or on a small screen.
- Captions on every video, because many workplaces are too loud for audio.
- Light files that load on a weak connection, and offline access where the site has no signal.
- The language the crew actually works in, not only the language of head office.
5. End with a decision, not a summary
Replace the closing recap with one or two questions that make the learner apply the rule to a new situation. A decision shows whether the module worked. A recap only shows that the learner reached the last screen.
6. Space it out
People lose a large part of what they learn within days unless they come back to it. This has been known since Hermann Ebbinghaus described the forgetting curve in 1885, and the spacing effect has been confirmed many times since. In practice, send a two-question follow-up a few days after the module and again a few weeks later. It costs very little and makes a visible difference.
7. Put it where the work happens
A QR code on a piece of equipment, a link in the job card, a module pinned in the shift handover app. The closer the lesson is to the task, the more likely it is to be used at the moment it matters.
When microlearning is the wrong tool
Microlearning is excellent for refreshers, procedure changes, pre-task reminders and reinforcement after a full course. It is the wrong choice for:
- Initial qualification, where people need the full picture and the regulator expects structured training hours.
- Complex systems, where understanding comes from seeing how the parts connect.
- Hands-on skills that need practice on the real equipment or a simulator. A short module can prepare people for that practice, but it cannot replace it.
How to tell whether it works
Completion rates are the easiest number to report and the least useful. Better signals are:
- Scores on the decision questions, and which wrong answers people choose.
- Results of follow-up questions a few weeks later.
- Findings in audits and inspections on the topics you covered.
- Questions supervisors stop getting on shift.
If modules are taken on phones or offline, standard SCORM tracking may not capture all of this. xAPI can, if your platform has a Learning Record Store. We explain the difference in our guide to SCORM, xAPI and cmi5.
Short is not the point. Useful at the moment of work is the point, and short is usually how you get there.
