Most organisations don’t fail at eLearning because they picked the wrong software. They fail because the course itself was never designed to be finished. Anyone who has tracked completion rates on an internal training platform has seen the pattern — strong sign-up numbers, a sharp drop-off after module one, and a handful of stragglers who finish only because a deadline forced them to.
The fix isn’t more reminder emails. It’s rethinking how the course is built in the first place.
Start with the job, not the content
A common mistake is treating an eLearning course like a textbook chapter — here’s what exists to know about this topic, now go learn it. That works for an exam. It doesn’t work for an employee who needs to know, specifically, what to do the next time a customer complains, a machine breaks down, or an audit checklist lands on their desk.
Before building anything, it’s worth asking a blunter question than “what should they learn”: what should they be able to do differently after this course that they couldn’t do before? A compliance module isn’t successful because someone read it. It’s successful because someone applies it correctly six months later, under pressure, without looking it up.
Keep modules short on purpose
There’s a reason “microlearning” has become a real instructional design discipline rather than a buzzword: attention on a phone screen, often on data the learner is paying for themselves, behaves differently than attention in a quiet training room. A 45-minute video module gets started and abandoned. A 6-minute module that covers one specific skill gets finished — and gets revisited later when someone needs a refresher.
Breaking a long topic into smaller pieces also makes tracking more useful. Instead of one vague “completed: yes/no” for an entire onboarding course, a manager can see exactly which specific skill a new hire is still shaky on.
Build in a reason to engage, not just a reason to comply
Mandatory training has a credibility problem — people know it’s mandatory, and they learn to click through it as fast as possible. The courses that actually hold attention tend to do one of a few things differently: they use realistic scenarios instead of abstract rules (“here’s an angry customer at your branch” rather than “customer service principles”), they ask the learner to make a decision and show the consequence, or they break up passive content with a quiz every few minutes rather than one long test at the end.
None of this requires expensive production. A well-written branching scenario built simply can outperform an expensively animated video that nobody pays attention to.
Design for the device people will actually use
In a lot of Kenyan workplaces — and especially for field staff, branch employees, or NGO volunteers spread across counties — the primary device for training isn’t a laptop at a desk. It’s a phone, often on mobile data, sometimes with patchy connectivity. A course that assumes constant high-speed wifi and a large screen will simply not get completed by the people who need it most.
This affects real design choices: video file sizes, whether content can be downloaded for offline use, whether the interface is usable with a thumb instead of a mouse, and whether a learner can pick up exactly where they left off if their connection drops mid-module.
Measure the right thing
Completion rate is the easiest number to track and often the least useful one on its own. A learner can complete a course by clicking through every slide without absorbing anything. Better signals include assessment scores tied to specific learning objectives, performance data from before and after training (fewer errors, faster resolution times, fewer compliance violations), and whether learners return to specific modules later — a strong sign the content is actually useful as a reference, not just a one-time obligation.
The honest version of “we’ll build it ourselves”
Plenty of organisations start by assigning eLearning content creation to whoever is free — usually someone in HR or communications with no instructional design background. This isn’t a criticism; it’s just how most internal teams begin, and sometimes it works fine for very simple content. But instructional design is its own skill, distinct from subject-matter expertise. The person who understands compliance regulations inside and out is rarely the same person who knows how to structure that knowledge into something a tired employee will actually retain at 4pm on a Friday.
That gap is usually where outside support earns its cost — not by knowing the subject matter better, but by knowing how people learn.
Beets Consulting designs and builds custom eLearning courses and LMS platforms for businesses, educational institutions, NGOs, and government organisations across Kenya — from instructional design and content development to full implementation and ongoing support. If you have a training programme that isn’t getting finished, we’re happy to look at why.