Most courses are treated as products that are finished at launch. They are not โ they decay, quietly, and learners notice long before the creator does.
Deciding in advance how you will maintain it is what separates a course that earns for years from one that quietly stops selling.
What ages fastest
- Software interfaces โ screens that no longer match what the learner sees.
- Prices, tools and services mentioned by name.
- Statistics and current examples.
- Rules and standards in regulated areas.
- Links โ a steady share break every year.
- Your own thinking โ after a couple of years you usually teach it better.
What ages slowly: principles, reasoning, judgement, and the reasons behind a method. Build the course so those carry the weight.
Structure it for updating
Decisions made once, at build time, that save years of work:
- Separate stable content from volatile content into different lessons, so you can replace one without touching the other.
- Keep tool-specific walkthroughs in their own short lessons.
- Avoid saying dates and current events in evergreen lessons.
- Put links, prices and references in a downloadable resource you can edit in a minute rather than in the video.
- Keep your source files organised โ project files, scripts, assets โ so re-recording one lesson does not mean rebuilding the set.
- Record with a consistent setup so a replacement lesson matches the rest.
A maintenance routine
- Check links quarterly โ the cheapest fix with the most visible impact.
- Read learner questions monthly. Repeated questions mark where the course is unclear or out of date.
- Review the whole course annually, even if nothing obvious changed.
- Watch a few lessons as a learner would, on a phone. You will notice things you cannot see in the editor.
- Keep a running list of small fixes and batch them rather than doing them one at a time.
Deciding when to re-record
Re-recording is expensive, so use a threshold:
- Re-record when the content is now wrong, not when it is merely imperfect.
- Re-record when the interface shown no longer matches reality enough to confuse people.
- Consider a short addendum lesson instead โ recording one three-minute update is far cheaper than redoing a section, and learners accept it readily.
- Add a text note on the lesson for small corrections.
- Do not re-record because you have improved as a presenter. Learners came for the content.
Communicating changes
- Tell existing learners when you update โ it is one of the few genuinely welcome emails you will send.
- Say what changed and where so people who finished know whether to revisit.
- Say whether updates are included in what they bought โ this should already be in your terms.
- Date your updates visibly so buyers can see the course is maintained. This raises conversion more than most sales-page changes.
Using learner questions as your update list
Your best source of what to fix:
- Log every question you receive, even the ones you answer quickly.
- Questions asked repeatedly mark a gap โ either a missing lesson or an unclear one.
- Questions about how to do something you covered mean the coverage did not work.
- Add a short lesson rather than a long answer, once you have answered the same thing three times.
- Ask people who finished what was missing โ they know, and few creators ask.
Version drift and course sprawl
- Adding without removing is how courses become bloated. Every addition should have a place, not just be appended.
- Remove lessons that no longer serve the outcome. Learners rarely complain about a shorter course; they complain about a padded one.
- Watch the total length โ a course that has grown by half since launch may no longer be the course you are advertising.
- Keep the sales page accurate as content changes. Mismatch here causes refunds.
Retiring a course
Sometimes the right decision:
- When updating would cost more than rebuilding.
- When the subject has moved on and the approach is no longer sound.
- When you no longer stand behind it.
- Give existing learners notice and, where you can, download access.
- Stop selling before you stop supporting.
- Be straightforward about why โ retiring a course honestly costs far less reputation than letting it rot while still charging for it.
One thing worth remembering
The difference between a course that earns for five years and one that fades in eighteen months is rarely the original quality.
It is whether anyone kept looking at it after launch.
FAQ
What ages fastest in a course?
Software interfaces, named tools and prices, statistics, rules in regulated areas, and links. Principles and reasoning age slowly, so build the course so those carry the weight.
How do I structure a course to make updating easy?
Separate stable content from volatile content into different lessons, keep tool walkthroughs short and self-contained, and put links and prices in an editable resource rather than in the video.
When should I re-record a lesson?
When the content is now wrong, not when it is merely imperfect. Often a three-minute addendum lesson is far cheaper and learners accept it readily.
What is the best source of update priorities?
Learner questions. Anything asked repeatedly marks a gap โ and once you have answered the same thing three times, add a short lesson instead.
When should a course be retired?
When updating would cost more than rebuilding, when the approach is no longer sound, or when you no longer stand behind it โ give notice and stop selling before you stop supporting.