Producing eLearning Units for Procedure Updates in Libyan Companies

A procedure changes, and the request reaches the learning team: ‘Please update the eLearning.’ Often the result is one of two extremes. Either the whole 25-minute module is re-recorded with the new step buried somewhere in the middle, so experienced employees click through it looking for what is different, or a single screen saying ‘Procedure revised, see attachment’ is uploaded and marked complete by everyone within an hour.

Neither tells employees clearly what has changed for them, and neither checks whether they understood it. A procedure update deserves its own kind of eLearning: a short unit made for people who already know the old way, built around the difference and tested before anyone is asked to complete it.

This article shows HR and digital learning teams in Libyan companies how to produce such units with three tools: a version template, one realistic scenario, and a comprehension test before publishing. It starts after the decision to update has been made; for deciding which changes need new eLearning at all, see our article on updating eLearning when work procedures change.

What an eLearning Update Unit Is, and What It Is Not

An update unit is a small piece of eLearning, usually five to ten minutes, for employees who already perform the procedure. Its audience is experienced, so its main risk is not a lack of knowledge but an old habit. That shapes everything about it:

• It covers the difference only, not the whole eLearning module again.

• It says just as clearly what has not changed, so people do not over-correct.

• It asks employees to apply the new rule in one realistic situation.

• It carries the procedure’s version number and effective date.

• It can be produced in days, because its structure never changes.

An update unit is not a replacement for the full eLearning module. New joiners still need the complete, revised course. The update unit exists so that people who learned the old way can switch to the new one without sitting through what they already know.

A Version Template for Every eLearning Update

The template is the main production tool. When every eLearning update unit follows the same structure, employees learn to read it quickly, and the learning team can build one from a revised procedure in a short time. The CDC Clear Communication Index, a research-based tool for developing and assessing public communication materials, offers useful checks here: one main message that the audience must remember, placed at the top, a call to action that tells people what to do, and specific directions on how to do it. A practical template for updating eLearning has eight parts:

• Version line: procedure name, old and new version numbers, effective date, and process owner.

• Main message: one or two sentences on what changes for this role, on the first screen.

• Old and new comparison: a two-column table showing the previous step beside the new one.

• Reason: one sentence on why the procedure changed.

• What stays the same: the nearby steps that employees should not change.

• Scenario: one situation in which the new rule must be applied.

• Comprehension check: two or three questions on the change itself.

• Help: who to ask, and where to find the full procedure.

The comparison table deserves particular care. Digital.gov’s plain language guidance on tables notes that tables can shorten and clarify complex material and help readers see relationships hidden in dense text. A two-column old/new table does exactly that for a procedure change: the difference is visible without reading the whole document.

Keep the template as an editable source file in your authoring tool, with fixed screen layouts and placeholders, and name each published unit with the procedure code and new version number. That way, the eLearning content always shows which version of the procedure it teaches.

Build One eLearning Scenario Around the Old Habit

The scenario is where the eLearning update unit earns its place. Ask the process owner a direct question: at which moment would an experienced employee most likely still do it the old way? Build the scenario around that moment.

A good update scenario is short: one situation, two or three decisions, and realistic documents or screens with any personal details removed. The first decision should be the point where the old habit produces the wrong action. Feedback then shows the consequence under the new rule, not a generic ‘Incorrect’, and refers to the line of the comparison table that applies. Add one decision about a step that has not changed: if employees start applying the new rule everywhere, you want to see it in the eLearning before you see it at work.

Resist adding more situations. A second or third scenario belongs in the full revised module, not in the update unit. The aim is a single, accurate rehearsal of the new step that people can complete between tasks.

Test Comprehension Before Publishing

Before release, test the eLearning unit itself, not the learners. Digital.gov’s guidance on testing content advises making testing an integral part of writing and planning, starting as soon as there is enough material to test, and planning to test at least twice. For an updated unit, a short test with three to five employees from the affected role, who have not seen the unit, is usually enough to find the main problems.

Let each employee complete the unit without help, then ask three questions:

• What has changed in the procedure?

• What will you do differently the next time this situation happens?

• What stays the same?

If two or more employees describe the change incorrectly, rewrite the main message or the comparison table before touching anything else. If they describe the change correctly but choose the wrong action in the scenario, the scenario or its feedback needs work. Revise, then run a second short round with different employees. This pre-publication test checks whether the unit communicates the change; for designing the task inside the unit that shows each learner’s understanding, see our guide to designing a short eLearning task that demonstrates procedure understanding.

Close with two sign-offs: the process owner confirms the content is accurate, and the learning team confirms that the comprehension test was passed. Only then publish the eLearning and assign it to the affected roles.

Practical Points for Multisite Companies

If your teams work across several sites or shifts, check the eLearning unit on the devices and connections they actually use, and keep media light enough to load reliably at the most remote site. If the procedure exists in Arabic and English, produce both versions of the update from the same template at the same time, so no site works from an older version.

A Hypothetical Example: A Seal Check at a Container Terminal in Misrata

The following example is hypothetical and is included only to illustrate the method.

A logistics company operating a container yard in Misrata revises its gate-in procedure. From the first of next month, gate staff must photograph the container seal and record its number before the truck enters, instead of after the container is placed in the yard. The existing eLearning module for gate staff is 20 minutes long and teaches the old order.

The learning team produces a seven-minute eLearning update unit from its template. The main message states that the seal check now happens at the gate, before entry. The comparison table shows the old and new order of four steps, and the ‘what stays the same’ screen confirms that damage inspection is unchanged. The scenario puts the learner at the gate at the end of a busy shift, with a queue of trucks and a driver asking to enter first and complete the paperwork later, which is exactly the moment the old habit would win.

In the comprehension test, two of four gate staff say the photo is now required in the yard as well, because the table’s wording is ambiguous. The team rewrites one row and tests again with three other employees, who all describe the change correctly. The operations manager signs off, the eLearning is published to gate staff on both shifts, and the full module is revised for new joiners the following month.

Keep Update Units Under Control After Launch

Update units multiply quickly. After three or four updates to the same procedure, employees face a chain of small pieces, and new joiners face a full module that may lag behind. Set a simple rule: once a procedure has accumulated a few update units, fold them into a revised full eLearning module and archive the update units, keeping their records.

Collect the questions employees ask in the first week after each release, and add the most common one to the template’s help section. Over time, this turns corporate eLearning updates from rushed reactions into a routine the whole company recognizes.

Summary

A procedure update calls for its own eLearning: a short unit for experienced employees, built on a fixed template with a clear main message, an old/new comparison, and a statement of what stays the same. One scenario placed at the moment where the old habit would win gives employees a realistic rehearsal of the new step.

Testing the unit with a few employees before publishing, and fixing what they misread, makes sure the eLearning communicates the change before anyone is assessed on it. What happens on the job afterwards is the next step, covered in our article on following up on procedure application after eLearning.

Click here. If you are planning eLearning update units for changing procedures and want a template your team can reuse, the SkillUp MENA team is glad to discuss your requirements.