AGM Studios Alexander G. Myers

Work · Technical learning and AI-assisted production

How I turned recorded sessions into a self-serve course, with a check at every gate

I built a repeatable production line that turns source material into interactive H5P lessons and quizzes for the learning platform (LMS). The subject expert signs off at four points, and every build passes three quality checks before a learner sees it.

Context Example XYZ Consulting (fictional): turn recorded advisory sessions and a curriculum into a course for small-business owners My role Course outline, production pipeline, H5P build, SOPs and end-to-end testing Tools H5P, LearnDash, WordPress, draw.io, Playwright, dev-browser

Reconstruction. Fictional company and data, built from scratch to show a similar methodology. The original work is covered by a confidentiality agreement (NDA). The real course was built during a 2026 internship at a regional business-advisory firm, listed on my CV.

The problem

The firm had hours of recorded sessions and an advisor’s curriculum, and wanted a course small-business owners could take on their own. The hard parts were not the slides. The hard parts were keeping every claim faithful to the source, keeping the expert in control of the content, and making sure the course still worked once it was inside the LMS.

The production line

View diagram full sizeScroll sideways to see all of it
01 Source intakeSubject Expert + ProducerSupply, transcribe and scrub sensitive material. Approval gate.02 Plan approvalSubject Expert + ProducerDraft the course plan; review pedagogy,sequence and claims. Approval gate.03 Script fidelityProducer + QADraft module scripts and quiz specs;trace every claim to source. Approval gate.04 Media and deckProducer + AI ToolingRender narration, sound and visuals; assemble the interactive deck.05 Build validationQA and GovernanceInspect every slide at learner widths. A failed gate returns tobuild.06 Accept and freezeSubject Expert + QACheck content and pedagogy against the ratified plan. Freeze thebuild.07 LMS verificationLMS and Front EndImport packages; verify structure,completion, progression and reporting.Approval gate.08 Learner testQA and GovernanceWalk the course as a new learner,including deliberate failure.Publish when clean.Fictional reconstruction. Detailed swimlane map is retained in the editablesource.failedgate
The overview reduces the process to eight milestones. The editable source has the detailed five-lane map, with four expert sign-offs, three QA gates and one media choice. The approval gates and remediation loops stay on that source page.
made with draw.io, generated from a structured process definition last committed 2026-10-27 source file ↓
  1. Source first. I keep the original recordings untouched and work from a transcript.
  2. Scrub before drafting. I remove names and sensitive details from the transcript before any drafting or media tool sees it.
  3. The expert ratifies the plan before I build a single slide. Structural changes late in a build cost far more than early ones.
  4. Fidelity review. I trace every script line and quiz item back to the approved source, and remove invented claims.
  5. Media: narration or custom sound and motion, each in a fixed slot, so a change in one lesson does not ripple.
  6. Check at real widths. I inspect decks as a learner sees them on a laptop and a phone, not in the editor preview.
  7. Freeze, then import. Only an accepted build goes into the LMS. I record its package IDs, structure and quiz gates.
  8. Fail on purpose. QA walks the course as a new learner, deliberately fails a quiz, and checks completion and reporting before publishing.

The interactive part, rebuilt

I rebuilt the four activities below for the fictional firm using interaction types I wrote myself. They play in the browser and download as standard H5P packages.

Open the course
Inbox triage, vendor data sharing, a branching client request and a knowledge check. About 25 minutes.
Open the course →

What it proves

QualityI trace every claim to its source, and a person approves every stage before the next one starts.
CraftCustom H5P content types, not only the stock ones, packaged with licences and checksums.
HandoverWritten instructions (SOPs) for each stage, tested end to end with browser automation, so the next person has a documented process to follow.

In an interview, I can walk through

  • the course outline, and how the expert sign-off worked in practice;
  • the XML and CSS overlays I used to bend stock H5P types to a brand;
  • how the end-to-end tests caught layout and gating problems before learners did.