Mobile Learning in a Workshop Environment

Mobile learning in an office is a phone on a train. In a workshop it is a device in a bay, with gloves, noise, poor light, worse connectivity, and a technician who is paid by the job.

Most mobile learning is designed for the first case and deployed into the second.

What has to work

Offline. Workshops have poor connectivity, particularly in the bays and below ground. Content must be downloadable and progress must synchronise later. A platform that cannot do this does not support workshop learning, whatever its mobile interface looks like. See standards.

Interruption tolerance. A technician is called away mid-module. The session must resume where it stopped, on a different device if necessary, without losing progress.

Short units. Something that can be completed in the time available between jobs. A forty-minute module in a workshop is a module that gets started and abandoned.

Readable in bad conditions. High contrast, large text, and video that works with the sound off — because either it is too loud to hear or the technician cannot use headphones safely.

Usable with gloves, or with a stylus, or with minimal input.

Fast. A login that takes ninety seconds is a login that does not happen.

And it must work on the device they actually have, which is frequently a personal phone rather than a supplied tablet — with everything that implies for what may be installed and what data may be held.

What mobile is genuinely good for

Being specific about this prevents the common failure of putting everything on mobile.

Reference at the point of work. A procedure, a specification, a wiring diagram, a torque figure. This is the highest-value use and it is closer to performance support than to training.

Short refreshers, spaced over time. Retention improves with spacing and mobile is the only practical delivery for it.

Capturing evidence. A photograph of completed work, submitted for assessment. See assessments that predict performance.

Notification. A new bulletin, an expiring certification, an available course.

Quick knowledge checks, a few questions rather than a test.

Video demonstration of a procedure, watched at the vehicle rather than in a classroom.

What mobile is bad for

Anything requiring sustained attention. A forty-minute module on system principles is not a workshop-floor activity, and delivering it there produces completions without learning.

Detailed diagrams. Anything requiring a large view. A wiring diagram on a phone is technically available and practically unusable.

Assessment that matters, unsupervised, where identity and conditions cannot be established.

First exposure to a complex topic. Mobile suits reinforcement and reference better than initial instruction.

The reference case deserves separating

The most valuable mobile use is not learning at all.

A technician looking up a torque specification is not training, and treating it as a course wastes everyone's time. Reference material should be searchable, fast, and not require completing anything.

Two different products, frequently conflated. Performance support is searched at the moment of need; training is completed and recorded.

Building reference material as courseware is the common error, and it produces a library nobody uses because finding the one fact takes four screens.

Design the reference layer separately, index it properly, and make the search actually work.

Practical deployment

Decide on devices before content. Supplied tablets, personal phones or workshop terminals produce different constraints.

If personal devices, address it properly. What is installed, what data sits on it, what happens when the technician leaves, and whether they are being asked to use their own data allowance. This is both a data protection question and a fairness one.

Provide the connectivity if you are asking for workshop-floor use. Expecting a technician to use their own mobile data is a small cost to you and it is noticed.

Consider the time. A technician on flat-rate pay who does training between jobs is doing it unpaid. If training is expected, it should be paid time, and if it is not paid it will not happen consistently. See flat rate and clock time.

Pilot in one workshop, with real technicians, before the network. The objections that arise there are the ones that matter.

What to measure

Completion is a weak measure here, because a mobile completion may be a module left open on a bench.

Look at whether reference material is being searched, and for what. The search log is the most useful data in a mobile deployment — it tells you what technicians need and cannot find.

Look at whether it is used in the workshop or at home. If everything is completed in the evening, the workshop-floor design was unnecessary and the technicians are doing it unpaid.

And ask them. A short conversation with six technicians tells you more than the analytics.

The short version

Offline capability with synchronisation is the requirement, not mobile responsiveness.

Short units, interruption tolerance, readable in bad light, usable with gloves, and fast to open.

Reference at the point of work is the highest-value use — and it is performance support, not training, and should be built separately.

Do not put sustained-attention content on mobile. It produces completions and not learning.

And if training is expected during the working day, pay for the time — otherwise it happens at home or it does not happen.

For guidance on making mobile learning interfaces accessible, see W3C mobile accessibility guidance.