How modernizing the learning ecosystem transformed course creation, improved learner engagement, and drove measurable results.
When the learning team at Global Medical Response needed to modernize how training was built, delivered, and experienced, I didn't just swap out an authoring tool.
The team was building online training in Lectora, a platform that had run its course. It limited our ability to create modern, interactive learning experiences, made mobile optimization nearly impossible, and slowed course development at a time when training demands were growing fast.
Tap each step to expand.
Before touching a single course, I started with a thorough needs assessment and process audit. I reviewed existing development workflows, identified constraints in our authoring environment, and consulted with stakeholders to align the transition with our long-term learning strategy.
One of the first and most important changes I made wasn't about tools at all. I introduced a new learning project request standard rooted in performance consulting, requiring teams to identify the root cause of a performance gap before a course was ever scoped.
It ensured we were building solutions that actually addressed business needs. From there, I designed and documented a streamlined course-request-to-development process, so every project followed a consistent, repeatable framework.
I led the full transition from Lectora to Articulate Storyline 360 and Articulate Rise, redesigning and developing 20+ courses in the process. To support consistency and scalability across the team, I built out a complete suite of design standards:
Each resource was designed so any team member could produce work that looked and felt cohesive, regardless of the project. I also incorporated scenario-based learning and interactive simulations into our redesigned courses, creating more engaging, learner-centered experiences that reflected how our workforce actually performed on the job.
Modernizing the learning ecosystem had a measurable impact on both the team and the learners we served.
Beyond the numbers, the team inherited a fully documented, scalable development framework they could build on independently.
When I transitioned out of the role, I made sure nothing was lost. I selected and mentored my successor, handing off my full workflow documentation, SME contact sheet, SME intake questionnaire, project tracker, and all templates built in Microsoft Project.