Course Suite Creation & Maintenance

[Iliana — describe the original mandate. Was it "build a curriculum from scratch"? "Replace ad-hoc training"? "Support a specific launch"? Set the stakes — who needed this and why.]

Every course in the suite follows the same backbone: a stated outcome, a context section that names who this is for and when they'd use it, a guided walkthrough, and a knowledge check tied to the original outcome. Consistency at the structural level is what lets a single person maintain a library of this size without it sprawling.

[Iliana — add specifics. What's your authoring template? How long is a typical course? What modalities do you use (video, interactive, text, scenario)? Are there learning paths that bundle courses?]

Most course libraries die from neglect, not from poor initial design. The maintenance system is what separates a curriculum from a graveyard.

• Per-release reviews — Every product release triggers a sweep of affected courses with a defined SLA for updates.
• Quarterly accuracy audits — Random sample of courses re-walked against current product behavior.
• Engagement-driven retirement — Courses below a usage threshold get reviewed for retirement or rewrite.
• Stakeholder feedback loop — CSMs and AEs flag inaccuracies via a single intake channel I triage weekly.

[Iliana — outcomes go here. Things to consider: course completion rates, time-to-productivity for new hires, reduction in "how do I do X" questions in Slack, qualitative feedback from team leads. Even one strong number is enough.]

[Iliana — pick one. What did you over-build, under-build, or sequence wrong?]