HotEnrolmentGradebookMigrationPluginsBackupsRetiring
Latest Nobody chooses a learning platform. Somebody chose one, years ago, and now it is yours.
The inherited system

You did not pick this platform and it is yours now

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.

Continue reading

Running it

The gradebook argument nobody wins

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

Backups you have never restored are not backups

The test is not whether the job runs. It is whether the file opens.

Changing it

Migration is mostly deciding what not to bring

The technical part is the easy part. The editorial part is the work.

Retiring a course properly

Hidden is not archived, and archived is not deleted.

The people

What learners actually complain about

Rarely the feature. Almost always the not knowing.

The administrator who cannot go on leave

Single points of failure are usually people, not servers.

Standing back

Why these systems all look the same

Not laziness. Convergent pressure from the same set of obligations.

When the right answer is not a platform

Some things being run through an LMS should not be.

About EduLMS

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.

The bias here is toward the inherited and the ordinary. Most published writing about learning platforms addresses a buyer comparing options. That is a rare situation. The common situation is somebody maintaining a system full of decisions made by people who have left, and that needs a different kind of advice.

Nothing here is affiliated with, endorsed by, or speaking for any software vendor or project. Where a particular platform's behaviour is described, it is described as an example of a pattern that recurs across systems of this kind, not as instruction for a specific version.

Where the subject touches record keeping, retention or assessment evidence, the treatment is general. Obligations differ by jurisdiction, sector and the specific arrangements an organisation operates under, and the applicable rules should be read directly rather than inferred from an article.