Skip to main content

Course Modularization Model

1. The LEGO Philosophy​

Our courses are not monoliths. They are assemblies of AKUs. This allows us to update a single AKU and have that change propagate across multiple courses, marketing assets, and support docs.

2. Hierarchy Structure​

Level 1: The Course (The "Product")​

  • Example: "The Ultimate Hiring System"
  • Component: A container of Modules.

Level 2: The Module (The "Chapter")​

  • Example: "Module 2: Interviewing"
  • Component: A container of Lessons.

Level 3: The Lesson (The "AKU")​

  • Example: "How to conduct a Screening Call"
  • Component: This IS an AKU.
    • Video: Derived from AKU Script.
    • Worksheet: Derived from AKU Template.
    • Quiz: Derived from AKU Key Takeaways.

3. Dependency Mapping​

  • Master Copy: The AKU in System 05.
  • Slaves:
    • LMS Lesson Page.
    • Support KB Article.
    • YouTube Video Description.

4. Updates & Depreciation​

When an AKU is updated (e.g., "Screening Call scripts changed"):

  1. Update the Master AKU.
  2. Check the "Used In" metadata.
  3. Trigger tasks to update:
    • LMS Video (Re-record if critical).
    • LMS Handout (Update PDF).
    • Support KB (Instant update).

Related Documents: