Case study 09 · Mar 2022 – Jan 2025 · eLearning developer, lead tester and delivery lead # Building and maintaining a 4-module office induction for a state transport department I helped build and test a 4-module online induction for one of a state transport department's offices, delivered it to the department's own LMS, then became the person who kept it up to date. ## At a glance - **My role:** eLearning developer, lead tester and delivery lead - **Period:** Mar 2022 – Jan 2025 - **Scale:** 4 online modules and 5 videos, hosted on the department's LMS; change rounds in 2022, 2023 and 2023–24 - **Worked with:** the department's project contacts, studio designers and the studio's director - **Tools:** Articulate Storyline 360, SCORM, Word, Vimeo - **Headline outcome:** the induction stayed accurate through change rounds in 2022 and 2023 and a department rename, with the final version delivered in May 2024 ## The situation The office needed an online building induction. The studio built it as 4 online modules and 5 videos, and the department hosted it on its own LMS alongside its other courses. I joined the studio in March 2022, while the induction was being built. Designers created the look and the Storyline templates. Others built, tested and delivered. ## My role I was one of the builders and the lead tester, and I prepared the deliverables for the department. Later the induction was mine from start to finish: every change request came to me, and I handled it end to end. ## What I did ### Fixed issues where I found them The induction was my first Storyline project. I didn't design the templates, but I led testing. When testing found small issues, I fixed them in Storyline myself rather than sending them back to the designers. It's also how I learned Storyline properly. ### Matched our output to the department's LMS Because the department hosted the induction on its own LMS, delivery meant working with its team so our SCORM export settings matched their system. We started with a sample package on their LMS, and getting it right took some back and forth: checking that it loaded properly, that quiz results reported back to their LMS as expected, and that learners could continue where they left off. I also ran the review rounds with the department, sending each version, collecting feedback and returning the next. ### Owned the change rounds The induction kept changing as the office did. There were change rounds in 2022 and 2023, then a larger update when the department was renamed (November 2023 to May 2024). I was responsible for that update from start to finish. I estimated the work and updated all 4 modules and the videos to the revised scripts. The department's old name was replaced with "the Department", so a future rename won't need another round. I set up a staging page with every final deliverable for the department to review: the online modules, SCORM files, scripts and all 5 videos. The final version went to the department in May 2024. ### Supported learners Until January 2025 I also handled learner issues with the modules. ## Results - A 4-module induction with 5 videos delivered to the department's own LMS. - Kept current through change rounds in 2022 and 2023 and a full rename update, with the final version delivered in May 2024. - Learner issues handled until January 2025. ## What I'd do differently - **Write for change.** Names and logos in narration and video are costly to change. Generic references from the start save a full update later. ## Tools and skills - **eLearning:** Articulate Storyline 360, SCORM packaging and LMS settings, accessible transcripts - **Delivery:** review rounds, change estimates, staging pages for client deliverables - **Support:** learner troubleshooting on a client-hosted LMS --- *Client names, people's names and some details are left out. Any visuals are recreations with invented data.*