PRODUCTION INFRASTRUCTURE

The OpenAEV launch proved we could deliver under pressure. It also made clear that we were relying on individual effort, not shared structure. If we were going to sustain a four-course annual roadmap, production needed to become predictable. Now our goal was to make course production repeatable.

DEFINING THE LESSON DELIVERY LIFECYCLE

There was no documented process from idea to publish. I formalized a Lesson Delivery Lifecycle that defined:

• SME alignment

• Script review

• Recording

• Editing

• QA

• LMS formatting

• Publish

Each stage included clear ownership and review gates. This allowed us to estimate timelines realistically and protect an 8–9 week production cycle for full courses. Major rewrites after sign-off were deferred to maintenance cycles to prevent blocking other lessons.

INTRODUCING QA DISCIPLINE

Quality checks were non-existent before I joined. 

I introduced:

• A pre-publish QA checklist

• Peer review before release

• Verification of navigation, captions, quizzes, metadata, and accessibility

REDUCING SPEAKER FRICTION

Recording quality varied widely. Retakes slowed production.

I created:

• A Speaker Recording Checklist

• Clear framing and audio standards

• A lightweight Video Recording Kit system for remote contributors

I’m happy to say that the kit model was adopted and improved baseline video quality across the company.

MAKING WORKFLOW VISIBLE

Production tracking lived in conversations and inboxes. I Introduced Agile-style tracking, and centralized planning in a shared Notion board with:

• Status tracking

• Priority tagging

• Ownership clarity

• Written decision logs

I also established a quarterly executive report to provide visibility into roadmap progress and production capacity.