• Content Team was tasked with creating 8 new courses for our company's primary product (online OSHA training that is targeted primarily at high school students). They were given 5 months to accomplish this task &mdahs; prior to this, creating a single course in two months was a stretch
• From previous experience working with their front-end developers, I knew that much of their development workflow involved a tedious process of copying and pasting the same files and pages of code over and over again with only minor revisions

I designed and pitched a new tool that would streamline the content development process, eliminate redundant work, automate Jira ticket creation, and auto-generate the code layer needed to publish.

• Discussed the idea of an approved content management tool with the Content Team and got them on board
• Created a functional prototype and presented it to the Chief Product Officer (CPO) and the rest of the development team to get approval for the project
• Spent a day whiteboarding the entire content development process with the Content Development Manager (CDM) and Lead Instructional Designer to identify areas for process improvement and automation
• Met regularly with CDM and CPO to prioritize feature implementation
• Worked with Perla to document all 40+ existing page types used by the team for development of new courses and designed a custom ticket schema in Jira
• Deployed a beta version of the application that the content team began using to create the new courses
• Met daily with members of the Content Team for two months to discuss their needs and iterate on features

• Automated code generation
  • Eliminated the need for two full-time developers and dramatically reduced the time needed to publish a new course
  • Bugs in front-end code could be fixed one time in one place, rather than requiring a code fix in every instance of a course

• Auto-generated Jira tickets for all asset creation
  • Provided full visibility into the LOE/scope of work required to bring a course to production for the first time
  • Missing or forgotten graphics are no longer discovered during the final QA review of a new course

• Re-architected content structure
  • Divided courses into smaller pieces that could be re-arranged or combined to create custom courses
  • Separated the content from the display layer, allowing flexibility in where and how content is used