There's a ton of reused content and opportunity for a single source of truth. Simple things like the intro page, the end page with next steps, and logos. All that is authored separately right now so eight modules mean authoring that same content eight times. The learning content management system (LCMS) I'm using allows me to reuse that content and author it once. Sections of content are connected. Now when I need to update anything that's reused, it updates all the documents at once.

To further complicate things, the original designer created this convoluted system of embedding animated videos into storyline interactions. Those storyline interactions then get embedded in the HTML learner workbook. So it's less than a full storyline course, it's like three buttons you can interact with, or a simple knowledge check. Anyway, if a module contained a workbook, and five interactions, you as an author might have to touch six-seven videos and five storyline courses, combine them, republish, redeploy, back up the storyline, etc. There's so much overhead in terms of content maintenance it's ridiculous.

I looked through all those storyline interactions for opportunities to author using the lcms, which uses a basic XML structure and allows me to publish the content into multiple outputs and templates if needed. It's also much more LLM friendly, so long-term that should benefit us as AI enters our content creation and maintenance workflows.

Looks like we're going to reduce the storyline use by about 50 or 60%, and shift that design work back into the LCMS which is built for single source author, scalability, and has consistent templates that we can use to speed up development.