Turning Scattered Files into Assessable eLearning in Iraqi Companies

Ask where the training material for a key task lives in many Iraqi companies, and the answer is rarely one place: a Word file on a shared drive, a newer version attached to an old email, a scanned circular signed by the general manager, an Excel template that only one branch fills in correctly, and explanations forwarded in a WhatsApp group. Together, these files make it almost impossible to say whether a new employee has actually learned the job.

The usual response is to upload everything to a learning platform. That creates a library, not eLearning that anyone can assess. An employee can open a PDF, scroll to the last page, and be marked complete without anyone knowing whether they can apply a single step.

This article sets out a narrower route for HR and digital learning teams: choose one file, find the task inside it, and build three things from that file only: a practice task, an assessment, and a reinforcement plan. Once one file works as assessable eLearning, the method can be repeated for the next.

Why a Folder of Files Is Not Yet eLearning

Most operational files record a decision or describe a procedure; they were never designed as eLearning. They rarely show what a correct result looks like, which errors are common or how a supervisor can tell a careful employee from a lucky one.

Cathy Moore’s action mapping approach puts the focus on what people need to do and why they are not doing it, and recommends realistic practice activities rather than information presentations when training is the right solution. That is the shift a file needs to make before it becomes eLearning. Much of the content can stay the same, but the eLearning is organized around an action the employee performs, not around the chapters of a document.

Here, “assessable” has a specific meaning: the eLearning produces evidence, scored against an agreed standard, that shows whether an employee can perform one task correctly. Completion status, time spent, and a few recall questions about the document do not meet that test.

Step 1: Choose One File, Not the Whole Folder

Do not convert everything at once. List the files people actually use for one role, where each lives and who updated it last, then choose one that meets these criteria:

• It supports a frequent task, not a rare exception.

• Mistakes in the task are visible and cost time, money, or customer trust.

• A named owner, usually the department that runs the process, can confirm the content is current.

• A supervisor can check the result in ordinary work, such as a completed form or a correct system entry.

Ask the owner to confirm the current version before building anything. If two versions contradict each other, resolve that first; eLearning built on the wrong version trains people to repeat the same mistake. If the key knowledge is not written down at all and sits with one experienced employee, start by documenting the specialist’s knowledge before they move on.

If your first file comes from a banking operation, a companion article covers eLearning that helps Iraqi bank employees identify missing documents.

Step 2: Turn the File into One eLearning Practice Task

Sort the chosen file’s content into three columns:

• Actions: what the employee does, such as checking, entering, recording, approving, or handing over.

• Decisions: points where the employee must choose, such as accept or return, approve or escalate, continue or stop.

• Reference information: codes, limits, contact lists, and tables that people look up rather than memorize.

Actions and decisions become the practice task. Reference information becomes a job aid, so the eLearning does not ask people to memorize a price table or a list of extension numbers.

Next, write a one-sentence task statement: given a realistic situation, the employee produces a specific result to a defined standard. Then ask supervisors which errors they see most often; those errors become the raw material for practice.

Build the practice around real inputs: a photo, a form with something missing, a customer request, or a system screenshot. The employee acts, receives specific feedback, and tries again. Two or three cases covering the common errors are usually enough. Attach the full file as a reference rather than turning it into thirty slides of eLearning content.

Step 3: Build an Assessment from the Same Task

An eLearning assessment is only useful if it measures the task, not the document. A question such as “According to section 4, how many copies are required?” tests reading. A case in which the employee prepares the copies, notices a missing signature, and decides what to do next tests the work.

Build it from the same task statement, using new cases the employee has not seen in practice:

• Use two to four realistic cases, at least one containing a common error to catch.

• Where the task produces a document, ask the employee to complete it from the case materials and score it with a short rubric.

• Agree on the passing standard with the process owner, and mark critical errors that fail the attempt, regardless of the total score.

• Allow a second attempt with a different case, so the result reflects ability rather than memory of the first answer.

Record results for each case and each rubric item, not only a final percentage. Knowing that most employees miss the same step tells you what to fix in the file, the eLearning, or the process. Check first what your platform actually captures; see our guide on testing LMS completion reports in Iraqi organizations.

Step 4: Plan Reinforcement Before You Launch

A single eLearning module, however well designed, is a one-time event. In an article for the APS Observer, researchers Hal Pashler, Doug Rohrer and Nicholas Cepeda note that studies going back more than a century have found that spacing learning episodes across time can enhance memory, and that the benefits of spacing seem to grow as the retention interval lengthens. For a work task, that suggests short, planned returns to the task rather than one long session.

Plan reinforcement in three layers, all drawn from the same file:

• Spaced practice: two or three short eLearning cases sent one, three, and six weeks after the module. Use new cases, not the assessment questions.

• Performance support: the job aid from Step 2, placed where the task happens, whether that is a printed card at a counter or a pinned file on a work phone.

• Supervisor check: a brief review of a small sample of real work using the assessment rubric, so employees hear one consistent standard.

The Kirkpatrick Model defines Level 3 as the degree to which people perform critical behaviors in their environment and are supported in and accountable for that performance, and lists performance support and the performance environment among its components.

Reinforcement is how a small corporate eLearning project reaches that level instead of stopping at a test score.

Finally, name an owner for updates. When the procedure changes, the file, job aid, practice cases, and assessment should change together. Otherwise, you are soon back to scattered versions, now with an outdated eLearning module added to the pile.

A Hypothetical Example: Vehicle Reception at a Car Service Center

The following example is hypothetical and only shows how the four steps fit together.

A car dealership with service centers in Baghdad and Basra keeps its vehicle reception procedure in an eleven-page Word file, an Excel form, and voice notes from the service manager in a WhatsApp group. Supervisors keep reporting the same problems: existing scratches not recorded, complaints written as “check the car” and personal items left in vehicles without a note.

The learning team picks this file for its first eLearning project because reception happens many times a day and every error becomes an argument at handover. With the service manager, it confirms the current version and writes one task statement: given a customer, a vehicle, and the customer’s description of the problem, the service advisor completes the reception form accurately before the car enters the workshop.

The eLearning practice shows a vehicle from four angles and a short recorded customer description. Advisors complete the form on screen and receive feedback on what they missed, such as a dent visible in one photo or a complaint too vague for a technician to act on. The assessment uses three new vehicles, and an unrecorded dent counts as a critical error. Reinforcement adds a new case every two weeks for six weeks, a one-page checklist at each service desk, and a monthly review of five real forms per advisor.

The team judges the eLearning not by completion rates but by whether the most frequent errors become less common in real forms, and which steps still fail.

Adapting eLearning to Iraqi Workplaces

Language as Employees Use It

Write eLearning cases in the language employees use at work. Teams in Baghdad or Basra may work mainly in Arabic, teams in the Kurdistan Region may need a Kurdish or bilingual version, and many forms carry English labels. Show terms exactly as they appear on the form or screen, and test the wording with a few employees before launch.

Devices, Connectivity and Shifts

If staff use their own phones or shared branch computers, keep each eLearning case short, compress photos and audio, and test the module on a weak mobile connection. Where a site’s connection is unreliable, schedule assessment attempts when they can be finished in one sitting, so a dropped connection does not look like a failed attempt.

Approval and Ownership

Procedures often carry formal approval, and employees may hesitate to follow an unsigned version. Ask the process owner to approve the eLearning cases, rubric, and job aid as well, and show the version date inside the module. Use results first to improve the file and the employee learning experience; any use of individual results in performance decisions should follow your organization’s HR policies.

Summary

Scattered files are a normal stage for a growing company. The problem starts when uploading them is treated as finished eLearning. Choosing one file and building practice, an assessment, and reinforcement from it turns a document into eLearning that shows what employees can actually do.

Start with the file behind the error your supervisors mention most often. When that single piece of assessable eLearning works, with an owner, a rubric, and a reinforcement plan, the next file takes less time, and your eLearning library grows around tasks rather than folders.

Click here. If you have a folder of procedures and would like help deciding which file to turn into eLearning first, the SkillUp MENA team can talk through your requirements with you.