Running the Academy: operations and curriculum
Three full courses and six mini-courses shipped in 14 months, on production systems I built along the way.
Good courses don't ship on time by accident. Since joining Filigran, I've led content operations and production for the Academy and built the workflows the team now works from: how a course gets planned, made, reviewed, published, and measured.
- My role
- Lead for content operations and production
- Scope
- Curriculum roadmaps, production workflows, quality assurance, expert review, LMS publishing, reporting
- Tools
- Jira, Review 360, WorkRamp, LearnWorlds
What I put in place
- Roadmaps and templates
- Curriculum roadmaps that say what gets built and when, plus templates for quality checks and for briefing Marketing on a launch.
- A visual component library
- I built a library of reusable visual components and set multimedia production standards, to give the Academy's courses a shared look.
- Recording with experts, wherever they are
- A distributed recording program for subject matter experts spread across countries and time zones. The video below came out of it.
- Reporting leadership can read
- Academy performance reporting and executive dashboards that track registrations, enrollments, completions, and credentials earned.
Video with a subject matter expert
The course development workflow
I wrote this workflow and aligned the team on it. Every full-length course moves through seven stages, and each stage ends at a checkpoint that has to be true before the next one starts.
| Stage | What happens | Checkpoint |
|---|---|---|
| 1. Initiate | Open the project and draft the course outline. | Outline approved and a subject matter expert assigned. |
| 2. Plan | Set milestones and the timeline. Create the launch information page for Marketing. | Timeline agreed and Marketing briefed. |
| 3. Design | Turn the outline into an instructional approach: activities, assessments, and supporting materials. | Design ready to build. |
| 4. Develop and review | Build the course. Experts review for two weeks, then another content manager reviews for two to three business days. | Content reviewed and ready for the LMS. |
| 5. Prepare and test | Configure the course in the LMS. Test enrollment, navigation, scoring, prerequisites, and completion tracking. Technical trainers do a final review on a restricted link. | Final review done and issues fixed. |
| 6. Launch | Make the course public and update Marketing's launch page with final details. | Course publicly available. |
| 7. Maintain | Review learner feedback and course performance on a regular cadence. Update without disrupting learners in progress. | Assigned maintenance complete. |
Three principles hold it together. Each course has one owner who makes the day-to-day calls. Progress, blockers, and decisions live in one tracker. Marketing hears about a course as soon as its outline is approved, not after it's built.
The learning path: Crawl, Walk, Run
I defined what separates a 101, a 201, and a 301 course, so the team could decide where any topic belongs. All three levels teach skills, meaning what a learner can do. What changes is the complexity of the work, the independence expected, and the scope of responsibility.
| Dimension | 101: Crawl | 201: Walk | 301: Run |
|---|---|---|---|
| Relationship to the product | Understand it | Use it | Own and optimize it |
| Core question | What is this, how does it work, and when should I use it? | How do I correctly accomplish my work in the product? | How should the product be configured, governed, and maintained for our organization? |
| What learners do | Recognize, distinguish, interpret, classify, select | Create, connect, investigate, update, collaborate, produce | Design, configure, govern, automate, troubleshoot, optimize |
| Organizational rules | Understand them | Apply them | Define and maintain them |
| Success standard | Makes correct decisions about the product | Performs practitioner work competently and independently | Enables reliable, secure, effective use across the organization |
The boundary test I use to control scope: if the learner is applying established rules to get work done, the topic belongs in 201. If the learner is deciding or maintaining the rules other people work within, it belongs in 301. Using the platform is not the same as owning it.
Progression is defined by job performance and scope of responsibility. It isn't defined by seniority, job title, or how many features a learner has seen. Role-specific branches sit on top of the core levels, so not every learner needs every course.