Learning platforms · eLearning · Project delivery
I help organisations run better learning platforms, and get people using them.
I've spent almost six years in software and learning technology, most of it at a small Melbourne eLearning studio that works with government, education and corporate clients. I manage platform projects with vendors and partners, administer learning management systems, build courses in Articulate Storyline and Rise, and do the data work that shows whether it's all working.
Moodle 5.0 and Drupal-based LMSs: users, roles and permissions, enrolments, certificates, notifications, reporting, and support by email and live chat.
Requirements, permissions models, vendor tracking, user acceptance testing and release sign-off, across organisations that don't report to each other.
Articulate Storyline and Rise, SCORM, video and subtitles, with accessibility checked against WCAG 2.1 AA.
Guides, walkthroughs and support that get people using a new system, and the reconciliations and reports that show whether it's working.
over 3,800 users
Case study CS-01
As project manager, I moved a state government training portal from an outdated Drupal LMS to Moodle 5.0, with online modules and session booking on one platform.
8 modules
Case study CS-02
How I ran production, testing and release for an 8-module First Peoples cultural safety eLearning program for a state transport department.
29,016 user-module completion records
Case study CS-03
Two data investigations on a newly migrated government LMS: reconciling 29,016 completion records, and matching booking confirmations to 1,232 enrolments.
124
items tracked through 19 test rounds
From CS-04 : Rebuilding two governance tools for school councils, ready for department reviewAbout 3,200
queued notifications kept from reaching users
From CS-05 : Fixing a training portal's 26 system emails and restoring the survey link17
quarterly reports in a row, none missed
From CS-06 : 17 quarterly reports in a row, each now done in under a day50
eLearning titles kept current on Go1
From CS-08 : Keeping a 50-title eLearning catalogue current, including a 2026 law updateA 60-second scenario based on how I run releases. Choose what you'd do, then try two quick questions.
The vendor's release note says item #214, a broken help link, is done. What do you do?
Close the item. The vendor has confirmed it.
Not yet. A vendor's “done” tells you the change has been released. It doesn't yet tell you it works for users. Close it now and it may come back as a reopened item.
Check it on staging, then close it.
Closer. Staging shows the fix works on a test copy of the site. But the live site can differ in settings or data, so an item can pass on staging and still fail on live.
Check it on staging and on live, save evidence of each check, then close it.
That's how I do it. The item closes only when it passes on both sites, with a screenshot or download saved against its number. That keeps conversations about status short and factual.
Completion badge: Release check complete
Requirements, a permissions matrix and a numbered tracker that the client, the partner and the vendor all work from.
Nothing closes until it passes on staging and on live, with a screenshot or download to show for it.
Small tools and in-place fixes, so routine needs don't queue behind the main build.
Record-level reconciliations and checks before any number goes out.
The best way to reach me is by email or LinkedIn.
Based in Sydney, Australia