Stepping into the role of eLearning Manager for the Educator Learning Center at Hanover Research presented a challenge: not only was I the first in-house developer; I was also responsible for building our production process from the ground up.
As a subscription-based service, the Educator Learning Center needed to deliver a premium experience. A “good enough” approach simply wasn't going to cut it. To deliver a commercial-grade product, we had to raise our design standards, refine our learning approach, and improve the production workflow.
I couldn’t wait to get started!
Previously, the organization relied on a disconnected network of freelance developers. Rigid PowerPoint storyboards and siloed communication contributed to modules that lacked visual polish and opportunities for engagement. We needed to move from ad hoc production to a holistic, repeatable system.
Streamlining SME Collaboration
One bottleneck was clear: PowerPoint storyboarding was labor-intensive for our Instructional Designers and SMEs, resulting in slow review cycles and limiting how screen design and interactivity could be communicated. Because developers were largely expected to execute what was documented in the storyboard, the format left little room to explore or refine the visual and interactive experience during development.
Once we pulled the process in-house, we transitioned to a customized Word template, which streamlined content generation and enabled developers to provide direct, inline feedback. To further support our SMEs, we established formal documentation—including a core module framework and comprehensive style guides—ensuring that new contributors could integrate seamlessly and meet our quality expectations from day one.
Improving Development Efficiency
To accelerate development, we created a library of Storyline “builder files”: preconfigured interactions ranging from animated treatments to complex self-checks. The library helped instructional designers and SMEs envision interactivity during storyboarding. For developers, reusable triggers, variables, and layers reduced repetitive work without limiting creativity.
Building a Visual Library
Master templates established a consistent visual identity, but we didn't want every module to look alike. We created custom graphics in Adobe Illustrator and Photoshop, along with short-form video, and organized shared assets in a centralized graphics library. The result was a recognizable ELC experience with room for each topic to have its own character.
Improving Production Operations
We also improved the operations behind the learning experience. WellSaid digital narration reduced the cost and turnaround time associated with recording and revising live voice talent. We moved frequently updated, LMS-independent resources—including linked references, downloadable materials, and ancillary Rise content—to a web server. That allowed us to update those resources without republishing the modules that linked to them. Jira and a Gantt scheduler gave us clearer visibility from storyboard development through SCORM deployment.
Conclusion
By identifying and addressing the major points of friction in our workflow, we created a more consistent production process that improved both the quality of our learning modules and the speed at which we could develop them. My experience running a custom learning business had already taught me the value of sound production practices; the ELC reinforced that lesson on a larger scale. A scalable process isn't just an operational convenience. It gives a team more time to focus on the learning experience itself.
How satisfying!
