EduLMS

About EduLMS

Most people who administer a learning management system were handed it. Understanding how that happens explains almost everything about why these systems are the way they are.

There is a particular kind of job that nobody applies for. Somebody leaves, or a role is restructured, or a manager notices that you are the person in the room who can be trusted with a spreadsheet, and by the end of the week you have the administrator password for a learning platform holding four thousand enrolments and eleven years of accumulated decisions. You did not choose the platform. You did not choose the version, the theme, the twenty-six plugins, the naming convention for course categories, or the arrangement by which the finance team receives a report every Tuesday in a format that exists nowhere in the software's documentation. All of it is now yours.

This is not a complaint about anybody. It is the ordinary way that these systems are staffed, and it is worth naming because so much of the writing about learning platforms assumes a reader who is choosing one. That reader is rare. The far more common reader is the person who has inherited a working system and needs to keep it working while gradually understanding why it was built this way. Those are different problems, and advice written for the first is often actively harmful to the second, because it treats every inherited arrangement as a mistake to be corrected rather than a decision somebody made for reasons that may still hold.

Almost every support ticket is an enrolment problem wearing a different hat.

Everyone wants the numbers to mean something. They disagree about what.

EduLMS is written for the person who administers a learning platform without having chosen it: the coordinator who inherited the password, the trainer who became the accidental expert, the small team keeping a system running for a few thousand people with no dedicated budget.

Explore topics & services

Useful website links