Enterprise knowledge Live

Knowledge Management Self-Study Course

A 12-lesson interactive course on KM methodology and AI-first content strategy, built as a self-paced learning experience with knowledge checks and progress tracking.

Project
Henricks Media
Role
Author & Developer
Timeline
2026

Enterprise knowledge

What it is

A self-paced course covering knowledge management methodology in eight lessons, then applying it to AI-era content strategy in four more. Roughly an hour, free, no signup.

It exists because I spent a decade building enablement programs for publisher and coach networks at Symantec and Broadcom, and that material lived inside corporate training systems. This is the methodology extracted into something anyone can work through.

Why the second half matters

The first eight lessons are KM fundamentals — the practice as it’s understood by people who do it.

The last four are about generative SEO and answer engine optimization, and that’s the part I think is genuinely current. The audience for structured content is no longer only humans searching. It’s language models synthesizing answers. The disciplines that made knowledge bases work — clear titles, scoped articles, resolution-oriented structure, consistent metadata — turn out to be the same disciplines that make content usable by a model. That’s the argument the course ends on.

How it’s built

Lessons are defined as typed data with content, key points and a knowledge check per lesson, rendered by an Astro page that handles progress tracking, a sticky progress bar, lesson navigation, and quiz feedback for correct and incorrect answers. Content is authored in markdown and parsed at build time, so writing a lesson means writing prose rather than markup.

Building the delivery layer myself rather than using an LMS was the right call for this scope: no accounts, no enrollment, no cookie consent — just a URL that loads fast and works on a phone. The instructional design and the implementation are the same job here, which is much of the point.

Questions about this work?

Happy to go deeper on any of it — the decisions, the trade-offs, or what I'd do differently.