Updating a course without rebuilding it

A course launched two years ago contains screenshots of an interface that has changed, a pricing tier that no longer exists, and a recommended tool that has been acquired. The instructor knows, and updating means re-recording a video in which the outdated detail is spoken aloud at minute fourteen.

So it does not get updated, and the course quietly loses credibility while continuing to sell.

For a concrete example of how ordinary collaboration software exposes activity signals, this guide explains what Microsoft Teams can record.

Separate the durable from the volatile

The core insight is that content ages at very different rates, and mixing the two is what makes updating expensive.

• Durable — concepts, principles, why things work the way they do. Good for years.
• Semi-durable — process and method. Changes when practice changes, every few years.
• Volatile — interface screenshots, menu paths, prices, version numbers, specific product names.

Put the volatile material where it can be edited cheaply: text, a linked reference sheet, an appendix. Keeping it out of recorded video is the single decision that determines whether a course can be maintained.

For broader evidence-based guidance on teaching and course design, the Carnegie Mellon Eberly Center publishes university teaching resources.

Record so that segments can be replaced

Short, self-contained recordings can be swapped individually. A single long take, with continuous narration and references backwards and forwards, cannot be edited without redoing the whole thing.

Consistent framing, lighting and audio setup matter for the same reason: a replacement segment recorded eighteen months later should not be visibly different, or learners will notice the patch and start doubting everything around it.

Keep a defects list from day one

Every cohort produces corrections: a broken link, a step that no longer works, an ambiguous instruction, a question that reveals a gap. These arrive one at a time and are individually forgettable.

A single running list, added to immediately, turns them into a work queue. Without it, the next revision starts with someone trying to remember what was wrong, and most of it is not remembered.

Schedule the review

Updating by intention does not happen. A dated review — twice a year for volatile material, annually for the whole course — puts it in the calendar as work with a start and an end.

The review does not have to result in changes. It has to result in a decision, recorded, about each item on the defects list: fix now, fix at the next major revision, or accept.

Tell learners what changed

A visible changelog is unusual in online courses and is worth having. It tells prospective buyers the course is maintained, it tells existing learners what to revisit, and it makes the maintenance work visible rather than invisible.

It also imposes a useful discipline: a course with a public changelog that has not been updated in two years is obviously stale to everyone, including its owner.