Designing a Short eLearning Task That Demonstrates Procedure Understanding in Tunisia

A distribution company in Tunis rolls out its revised purchasing procedure with an eLearning module and a ten-question quiz. Almost everyone scores above 80%. Three months later, the finance team is still receiving the same pattern: one large purchase split into two smaller requests, each just under the amount that would need the finance manager’s approval. The employees knew the thresholds. What the quiz never checked was whether they understood why the thresholds exist.

Knowing the steps of a procedure and understanding it are different things. Understanding shows when someone faces a case the procedure did not spell out and still makes the right decision, and can explain why. A short eLearning task can make that visible in about five minutes, if it asks for a decision and an explanation, not just recall.

This article gives HR and digital learning teams in Tunisia a model for that kind of eLearning task, a practical way to assess the explanation behind the decision, and a small user test to run before the task reaches every site.

Knowing the Steps Is Not the Same as Understanding the Procedure

An employee who knows the steps can list them. An employee who understands the procedure knows what each step protects, recognizes when a condition applies, and notices when a case is an exception. Most eLearning procedure quizzes test the first. A well-designed eLearning task tests the second by presenting a case and asking two questions: what would you do, and why?

The “why” does double duty. Research on self-explanation, defined in a meta-analysis by Bisra and colleagues as a process in which learners generate inferences about causal connections or conceptual relationships, found self-explanation prompts to be a potentially powerful intervention across a range of instructional conditions. In other words, asking employees to explain their decision is not only a way to assess them; it is also part of how they learn. The studies were not about workplace procedures specifically, so treat this as a design principle rather than a promise.

A Model for a Five-Minute eLearning Task

Keep the eLearning task small enough to finish on a phone between other work. It has four parts.

1. The Case

Three to five sentences describing a realistic situation, with one detail that decides the correct action. The detail should test the purpose of the procedure, not a number to remember. A good case is one that a supervisor recognizes immediately: “That happens every month.”

2. The Decision

Three or four options for what to do next. Each wrong option should be something employees actually do, such as following the letter of the procedure while missing its point, or asking for help when the employee could have decided alone.

3. The Explanation

A short prompt asking for one or two sentences: “Which part of the procedure applies here, and why?” For large groups, you can offer three or four possible explanations to choose from instead of free text, but keep free text for at least a pilot sample. Written explanations reveal reasoning that a set of options cannot.

4. The Feedback

After submitting, the employee sees a model answer in the eLearning feedback: an explanation written by the process owner, so they can compare it with their own. The model names the condition in the procedure, links it to the detail in the case, and states what the procedure is protecting.

Assess the Explanation, Not Only the Choice

Combining a decision with an explanation in eLearning gives four patterns, and each one tells you something different:

• Right choice, sound explanation: the employee understands the procedure.

• Right choice, weak explanation: the answer may be a guess or a memorized rule that will fail in the next unusual case.

• Wrong choice, partly sound explanation: the employee is applying a real rule in the wrong place, which often points to unclear eLearning content or an unclear procedure.

• Wrong choice, no real explanation: the employee needs the basics again, ideally with a supervisor.

To score explanations consistently, use a three-point rubric. Does the explanation name the relevant condition or rule? Does it connect that rule to the detail in the case? Does it show what the procedure is protecting, such as budget control or customer safety? An explanation that meets all three shows understanding; one that meets none shows that the employee is still recalling, not reasoning.

Ask the process owner and one supervisor to score the same ten pilot explanations separately, then compare and refine the rubric where they disagree. Do not mark down spelling or grammar unless writing is part of the job. If teams also meet in live sessions, the most interesting explanations make good discussion material, as described in our article on facilitating VILT for Tunisian teams through practice attempts.

Test the eLearning Task with a Few Users Before You Scale

A short task has little room for confusion: one unclear sentence can turn a test of understanding into a test of reading. Before releasing the eLearning task across sites, test it with a handful of real employees. Jakob Nielsen’s widely cited guidance on testing with five users holds that the best results come from testing no more than five users and running as many small tests as you can afford, with additional users when there are several highly distinct user groups.

For an eLearning task, a small test looks like this:

• Choose five employees from the target role, mixing sites and experience; add three or four more if two very different groups will use the task.

• Ask each one to complete the eLearning task on the device they normally use, thinking aloud, while you watch without helping.

• Note where they hesitate, misread the case, ignore the explanation box, or take more than five minutes.

• Fix the problems, then test the revised version with a new small group.

Pay particular attention to language. If your employees work with procedures in French but speak Tunisian Arabic at work, check that the case reads naturally and that the explanation box accepts whichever language they write in. The goal is to assess understanding of the procedure, not fluency in one language.

A Hypothetical Example: Purchase Requests at a Distribution Company in Tunis

The following example is hypothetical and is included only to show how the model works.

Under the company’s procedure, purchases up to 5,000 dinars need the line manager’s approval; larger purchases also need the finance manager, and splitting one purchase into several requests is not allowed. The eLearning task presents a case: a warehouse supervisor needs 7,600 dinars of shelving for one new storage area, and a colleague suggests sending two requests of 3,800 dinars, “to save time”.

The options are to send two requests, to send one request for line manager and finance approval, to wait until next month’s budget, or to buy part now and part later. The explanation prompt asks why the chosen option fits the procedure. A sound explanation says that the shelving is one purchase, so the total decides the approval route, and the rule exists so that finance can review larger spending.

In the user test, five employees from the Tunis office and the Sfax warehouse try the eLearning task. Two misread “storage area” as two separate areas, so the case is rewritten to say “one new storage room”. After launch, most wrong answers come with explanations that cite the line manager’s limit correctly but miss that the total is what counts. The finance team adds one sentence to the procedure, and the eLearning feedback is updated to match.

Scale the Task Across Sites and Procedures

Once the task has passed two rounds of testing, release it through your eLearning platform to every site that uses the procedure. Review explanations by pattern rather than by individual: if many employees share the same misunderstanding, the fix belongs in the procedure or the eLearning content, not in a reminder email. Then use the same four-part template for the next procedure, so that corporate eLearning builds a library of short tasks rather than long modules.

An eLearning task completed on a phone is still evidence from a simplified case. Confirm on the job that the understanding shows in real decisions, using an approach such as the one in our article on following up on procedure application after eLearning.

Summary

A short eLearning task can show whether employees understand a procedure, not just remember it, when it combines a realistic case, a decision, and a brief explanation of that decision. Scoring the explanation with a simple rubric separates understanding from lucky guesses and points to unclear content.

Test the eLearning task with a few real users before scaling it, fix what confuses them, and test again. The same attention to realistic wording matters for customer-facing roles, as discussed in our article on designing eLearning content for service employees in Tunisia.

Click here. If you would like to design a first short eLearning task for one of your procedures and test it with real users, the SkillUp MENA team can talk through your requirements.