How We Built a Content Machine: From 50 to 637 Modules in One Year
12x content scaling in one year. What we built, what broke first, and what actually drove the number.
Intake-to-publish workflows, content operations, QA frameworks, and how to scale production without scaling headcount at the same rate.
Content systems are the infrastructure behind what L&D ships: how requests come in, how they get scoped, how content gets reviewed, and how quality holds at scale. Most teams build these reactively — a spreadsheet here, a shared inbox there — and then wonder why 12x volume breaks everything.
Everything here is written from the experience of building intake, QA, and review systems that held at 637 modules, cutting SME review cycles from 6 weeks to 2, and documenting the playbook that makes institutional knowledge survive turnover.
12x content scaling in one year. What we built, what broke first, and what actually drove the number.
The bottleneck isn't the SME. It's the process we built around them. A structured review process and AI-assisted drafting cut our cycle from 6 weeks to 2.
The case for a minimum viable playbook when most L&D teams run on tribal knowledge.
A triage framework built on Thomas Gilbert's Behavior Engineering Model. The intake process that determines what gets built.
Content systems plus AI adoption. What the full equation actually looked like.