Arabic LMS for Jordanian Companies: Testing Employee and Manager Journeys

Most Arabic LMS demos follow the same pattern. A skilled presenter logs in on a large screen, clicks confidently through a polished course catalog in Arabic, opens a manager dashboard full of sample data, and finishes within the hour. Everything works because the person driving the demo knows exactly where to click.

Your employees will not use the platform that way. A sales representative in Irbid will open the invitation on a phone between customer visits; a warehouse supervisor in Aqaba will check his team’s progress at the end of a shift; a department head in Amman will approve a request between meetings. A learning management system demo that never puts these people in front of the screen tells you very little about how an Arabic LMS will work in a Jordanian company.

This article describes a different kind of trial demo: two scripted journeys, one for employees and one for line managers, performed by your own people, with a separate acceptance criterion for each role. It complements our guide to what training managers actually need from an Arabic LMS, which covers the training team’s own tasks.

Why a Presenter-Led Demo Hides the Real Arabic LMS Experience

A presenter-led demo answers the question ‘can this Arabic LMS do it?’ What you need to know is ‘can our people do it, unaided, on the devices they actually use?’ The gap between those two questions is where most adoption problems begin.

Usability practice offers a better model. The UK government’s Service Manual guidance on moderated usability testing describes watching participants try to complete specific tasks, using tasks that are relevant and believable and set a clear goal, and advises the moderator not to give away the answer or hint at how to complete them. Applied to an Arabic LMS, this means your employees and managers hold the phone or the mouse, and the provider’s team watches.

A second problem is averaging. When one score covers the whole Arabic LMS, a smooth employee experience can hide a weak manager experience, or the reverse. Separate journeys with separate acceptance criteria prevent that.

Scripting the Employee Journey in an Arabic LMS

Write the employee learning journey as a sequence of realistic tasks, in the order a new or existing employee would meet them in the Arabic LMS. Each step needs a clear goal and an observable end point:

• Open the invitation in Arabic, by email or text message, and reach the sign-in page

• Sign in for the first time, including setting or resetting a password, on their own phone

• Find the assigned course in the Arabic LMS without being told where it is

• Complete a short module that mixes Arabic text with English system terms, stop halfway, and resume later from the same point

• Submit an assessment and understand the result

• Open the certificate and check that their name appears correctly in Arabic

• Find out how to ask for help if something goes wrong

Write each task in plain Arabic, the way employees talk about their work, and never give away the steps. ‘You have been asked to finish the new safety refresher before Thursday. Find it and complete the first part.’ is a real task; ‘Click My Learning, then open the course’ is a set of instructions. The resume step deserves particular care, and our guide to testing course resume and results covers it in more depth.

If some employees rely on screen magnification or a screen reader, include them. The W3C’s WCAG 2 overview explains that the WCAG documents set out how to make web content more accessible to people with disabilities, notes that WCAG 2.2 was published in October 2023, and states that WCAG applies to web on mobile. Asking which WCAG version and level an Arabic LMS targets is a reasonable part of the employee journey.

Scripting the Line Manager Journey

The manager journey in an Arabic LMS belongs to line managers rather than the training team: branch managers, supervisors and department heads who have a few minutes, a phone and a team to look after. Script the tasks they will repeat every month:

• Open a notification that a team member is overdue and find out who it is

• See the team’s progress on one mandatory course, limited to their own staff

• Send a reminder in Arabic to one employee without leaving the platform

• Approve or decline an employee’s request to join an optional course

• Sign off an on-the-job checklist after observing a team member at work

• Confirm that the Arabic LMS does not show them employees outside their team

Managers judge a new Arabic LMS quickly. If the first notification is unclear or the team view is three screens deep, many will stop logging in and ask the training team for a spreadsheet instead. Run this journey with at least one manager who is not enthusiastic about technology; their experience is usually the more realistic test.

Setting Separate Acceptance Criteria for Employees and Managers

Agree on the criteria before anyone touches the Arabic LMS, and write them down. Each role gets its own thresholds, judged on its own evidence:

• Task success: the share of participants who complete every step without help, for example, at least four of five employees finishing unaided on their own phones

• Critical steps: steps that must never fail, such as signing in, resuming a course, or a manager seeing only their own team

• Language: labels, messages and certificates are clear to participants, and mixed Arabic and English text displays in the right order

• Time: a realistic upper limit for each journey, such as 15 minutes for the employee journey, based on the time people really have

• Recovery: after a mistake, participants can get back on track without calling for help

Treat the two results independently. If the employee journey passes and the manager journey fails, the Arabic LMS has failed for managers. That calls for a fix and a retest before signing, not an average that looks acceptable. Decide in advance which failures block the decision and which can be accepted with a written fix date.

Running the Arabic LMS Trial Demo with Jordanian Teams

Choose participants who reflect the workforce that will use the Arabic LMS: head office staff in Amman, branch or field employees from other governorates, shift workers, and at least one recent joiner. A small group per role is enough to reveal recurring problems; you are observing behavior, not running a survey.

Set up test accounts with anonymized data in an Arabic LMS sandbox, and ask participants to use their own phones on the networks they normally use, including mobile data. The GOV.UK guidance notes that sessions usually take between 30 and 60 minutes, recommends inviting observers and arranging a note-taker for each session, and reminds teams to store any personal data from notes or recordings securely.

The moderator reads each task aloud and then stays quiet. The provider’s staff observe but do not take the phone or explain the screen. For each participant and each step, record whether they succeeded, how long it took, and what they said. A note such as ‘looked for the course under Library, not My Courses’ is worth more than a general rating.

A Hypothetical Example: Testing an Arabic LMS at a Jordanian Retailer

The following example is hypothetical and only illustrates the method.

A retail and distribution company with stores in Amman, Irbid, and Aqaba has shortlisted an Arabic LMS and wants evidence before signing. The learning team writes a seven-step employee journey and a six-step manager journey, then invites five store employees, two warehouse supervisors and two store managers to a half-day trial demo in the provider’s sandbox.

The employee journey passes: four of five employees finish unaided on their own phones, and the one who struggles stalls at a password reset message, which the provider rewrites in clearer Arabic. The manager journey fails a critical step: both store managers can see employees from other stores in their team view, and one cannot reach the approval request from the notification.

Because the criteria were set separately, the result is clear. The company does not merge the two journeys into a ‘mostly good’ score. It asks the provider to fix the team permissions and the notification link, reruns only the manager journey a week later with two different managers, and signs for the Arabic LMS once both journeys meet their criteria.

After the Trial: Using Journey Results in Your Arabic LMS Decision

Summarize the results on one page per role: the criterion, the result, the evidence, and the fixes agreed. Attach both scripts to the contract or acceptance documents, so the same journeys can be rerun after launch, after major updates, and whenever a new group joins the Arabic LMS.

New groups may need their own journey. If you plan to train partners, distributors, or other external users on the same platform, add a third script for them; our guide to using an LMS to train partners and distributors in Jordan looks at that audience.

Summary

A polished demo shows what an Arabic LMS can do in expert hands. A scripted trial demo shows what your employees and managers can do with it on their own, on their own devices and in the language they work in.

Write one realistic journey for each role, set a separate acceptance criterion for each before testing, let your people drive while the provider watches, and fix and retest any journey that fails. That turns the choice of an Arabic LMS for a Jordanian company from an impression into evidence.

Click here if you want Skillup MENA to help you.