Civil Aviation Safety Authority · 2015–2021

Six years designing learning platforms and digital learning for CASA.

Long enough inside one regulator to design the platforms, the courses that ran on them, and the production system that let a team keep building after I stopped.

Client
Civil Aviation Safety Authority
Sector
Government · aviation
Role
eLearning Specialist
Period
2015–2021
Disciplines
LMS front-end design and development · information architecture · learning design · production systems · video

01Platforms

The CLASS platform home page: the CASA Learning Academy for Safe Skies wordmark above a five-item navigation bar, a welcome carousel showing a hot-air balloon at dusk, and six task tiles labelled Find a Course, My Learning, New Courses, Resources, Calendar and Achievements.
CLASS, one of the two internal platforms whose front end I designed and built. It is the only platform screen in the recovered archive that carries a positive identity, which is why the AviationWorx page beside it is written without imagery rather than with a borrowed one.

In 60 seconds

The problem
A safety regulator with learning obligations across two internal platforms, several distinct audiences and a design team that needed to produce at volume without producing inconsistency.
My role
eLearning Specialist, in-house, across six years.
Scope
LMS front-end design and development for two internal platforms, course and catalogue information architecture, instructional and assessment design, a reusable Storyline production system, and in-house video and livestream production.
Where it got to
Two internal learning platforms with front ends I designed and built, a national flight examiner program, and a production system the regulator's design team used after I left.
Built with
Articulate Storyline · Adobe CC · AviationWorx · CLASS

The situation

CASA regulates civil aviation safety in Australia. Its learning obligations run in several directions at once: technical and regulatory training for its own inspectors and examiners, corporate and leadership development for its wider workforce, and process learning for the systems staff use every day.

Those audiences do not want the same thing, do not have the same time, and in several cases were not even on the same platform. Over six years I worked across the whole of that estate rather than on any one part of it.

What was actually wrong

It is tempting to describe six years as a list of courses. That is the wrong unit. What actually accumulated was a set of connected systems: platforms that had to hold content, catalogues that had to make content findable, and templates that had to make content producible.

The through-line is that each layer was designed so the next one did not have to be improvised. A course template exists so the catalogue is consistent. A catalogue exists so the platform is navigable. A platform front end exists so a busy inspector can find the one thing they came for.

My role, and who else was involved

I designed and developed the LMS front ends for both internal platforms, designed course and catalogue information architecture, wrote and built learning and assessment, produced video and livestreams in house, and created the reusable Storyline production system used by the wider instructional design team.

  • CASA subject-matter experts, including flight operations inspectors and delegated flight examiners
  • The internal instructional design team, who authored courses against the production system
  • Editorial placeholder: Confirm which internal team owned each platform and who else worked on the front ends

Multimedia and production, across the program

Two capabilities ran underneath everything else. Being able to author and to shoot in house changes what can be designed, because a scenario can be written for footage that is actually obtainable.

02Multimedia

A video editing timeline showing footage of two pilots in a full-motion flight simulator, with colour scopes above and multitrack audio below.
Interviews, scenarios and livestreams were produced in house. The constraint that usually kills a scenario is that the footage does not exist; owning the camera and the edit removes it.

03Production systems

The Articulate Storyline authoring environment showing a CASA course title slide under construction, with a slide timeline, layers panel and object properties open.
The authoring environment the production system had to work inside. A template only holds if it survives contact with the tool: components had to be reusable as Storyline objects, not just as a specification.

What the six years contained

Grouped by body of work rather than by date. Only the engagement period and the March 2021 filming date are firmly evidenced; individual project dates are unconfirmed.

  1. Platforms

    LMS front-end design and development for the two internal learning platforms.

  2. Structure

    Making a large and role-specific body of learning findable by the right people.

  3. Production

    The template, component and asset system the design team built courses from.

  4. Programmes

    The national examiner program built on top of all of it.

Where it got to

  • Designed and developed the LMS front ends for AviationWorx and CLASS, two internal CASA learning platforms
  • The Australian Flight Examiner Rating Course and Professional Development Program, for air transport, helicopter and general aviation examiners
  • A reusable production system for the regulator's design team: style manual, Storyline, PowerPoint and InDesign templates, component specifications and an icon library
  • In-house video and livestream production, including interviews, scenarios and presentations

Audience numbers, completion data and evaluation results are not published and are not claimed here.

What I would do differently

The production system outlasted the courses. Six years on, the part of this work I would defend hardest is not any single module. It is that a team could produce consistent regulated learning without me in the room.

Recognise any of this?

If your situation rhymes with this one, the useful next step is usually a short conversation about where the problem actually sits.

Or write directly: glenn@glennhammond.com