EduLMS / Standing back

Why these systems all look the same

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

Learning platforms are widely mocked for feeling dated, and the criticism is often fair, but the sameness has causes worth understanding. Each of them has to hold records that may be needed years later, support roles with different permissions, work for people on old hardware and slow connections, and produce evidence that satisfies somebody external. Those constraints narrow the design space considerably.

The features that seem redundant usually exist because some institution somewhere depends on them and removing them would break a working arrangement. This is the same pressure that makes long-lived business software accumulate: the cost of removal falls on identifiable people who will object, and the benefit is diffuse.

It is also true that the people who buy these systems are not the people who use them, and that the purchasing conversation rewards a long feature list rather than a coherent one. A platform that does forty things adequately wins a comparison against one that does eight things well, and then everybody lives with the forty.

The realistic response is not to wait for a better category of software. It is to use a narrow slice of what you have, deliberately and consistently, and to resist the pull toward using more of it simply because it is there.

The corollary for anybody evaluating these systems is to weight the parts that are expensive to change and discount the rest. Reporting, enrolment and permissions are structural and will shape a decade of administration. The appearance of the front page, the presence of a particular activity type, and the design of the mobile application are all either configurable or replaceable, and they are what demonstrations are built around because they are what shows well in an hour.