OMNI University

Generic training gets treated as generic

People take training as seriously as it appears to have been taken. A module that looks like it came out of a template gets clicked through, because its own presentation signals that it is a box to tick.

That mattered more here than in most deployments, because the material was craft knowledge. Technique is learned by watching it done properly and then being checked, and neither of those survives being flattened into a slide deck with a quiz bolted on.

Video is the lesson, not an attachment

Authoring is built around uploading video, with questions attached to confirm the material landed. For teaching a physical craft that ordering is not a preference, it is the requirement, because the demonstration is the content.

Keeping authoring that simple also kept the library growing. The people who hold the expertise are not instructional designers, and any workflow that demanded more than record, upload, and add questions would have quietly stopped being used.

The right set for the right role

Courses are assigned from job title and area rather than presented as a catalogue. Somebody logs in and sees what applies to their job, which removes both the navigation problem and the possibility of the wrong training being assigned by whoever handled onboarding that week.

As roles change or courses are added, the assignment follows automatically. Nobody maintains a spreadsheet of who owes what.

Assessment that means something

Each course resolves to a pass or a fail against its questions, recorded per person. A failure notifies the team so it can be addressed, and the failed section stays locked until it is reopened rather than being immediately retakeable.

That lock is what keeps the result honest. Without it, an assessment becomes a memory test of which answer the system accepts, and the record it produces is worthless.

Administrators can see the whole picture: who was assigned what, who completed it, and how they did.