The three-question test for cutting a course module
Use three questions to decide whether a lesson earns its place in the curriculum.

You are halfway through recording a course when you notice the problem: one module explains an interesting idea, but you cannot say what the learner will do differently afterwards. Another repeats an earlier lesson in more detail. A third is useful only if someone already understands the rest of the course. Cutting any of them feels risky because you have spent time making them. The risk, though, is asking learners to spend time on lessons that do not move them towards the finished result.
Start with the promised result
Before judging individual modules, write the course outcome in one sentence. Make it observable: “By the end, you can plan and publish a four-email launch sequence” is more useful than “You understand email marketing.” The observable version gives you something to test. Each module should contribute to a decision, action, or piece of work that makes the outcome more likely.
This is also where you catch a course that has grown beyond its promise. If the curriculum now covers tools, theory, history, advanced variations and three adjacent skills, learners may not know which parts matter. Keep the original result visible while you review. A lesson can be accurate and well made yet still be wrong for this particular course.
Question one: what does this module make possible?
- 1Write the answer as a learner action: “choose a topic”, “set up the file”, “write the first draft” or “check the result against these criteria”.
- 2Connect that action to a later step. If the learner does not use it in a task, decision or submission, mark the module for closer review.
- 3Separate knowledge from performance. Knowing five ways to structure a lesson is not the same as producing a usable lesson structure.
- 4Look for the smallest useful version. If ten minutes of explanation enables the same action as forty minutes, keep the shorter path and move the detail elsewhere.
The question is not whether the module is interesting. It is whether removing it makes a later action harder, less accurate or impossible. For example, a lesson on choosing a target reader may feel like preparation, but it earns its place if the next exercise requires the learner to make specific choices about language, examples and scope.
Question two: what breaks if you remove it?
| If removing the module means… | Likely decision |
|---|---|
| The learner cannot complete a required task | Keep it, then make its connection to that task explicit |
| The learner can continue but will repeat a common mistake | Keep a shorter version, checklist or worked example |
| The learner loses useful background but can reach the result | Move it to optional reference material |
| Nothing changes except the course becomes shorter | Cut it |
Run this test in both directions. A module may look unnecessary early on but provide a foundation later. Conversely, a late lesson may repeat a skill already practised. Trace the dependency: where is the idea first introduced, where is it practised, and where is it needed? If the same explanation appears in three places, keep the clearest introduction and replace the repetitions with links, reminders or a single reference sheet.
Question three: where will the learner use it?
A module is easier to justify when it has a visible practice point. That might be a worksheet, a draft, a decision, a quiz with a meaningful answer, or a task inside the learner’s own project. Place the practice as close as possible to the explanation. If someone watches a lesson on writing a product description and only writes one three modules later, the connection may disappear.
For each module, add a line that tells the learner what to do next: “Pause here and choose one audience”, “Use this checklist on your draft”, or “Upload the version you would actually publish.” If you cannot write that line without inventing an extra activity, the module may be information without a job. You can either add the practice or reduce the lesson to a short note that supports a later task.
Decide what to cut, combine or relocate
Do not treat the decision as keep or delete only. There are four useful homes for course material: the core path, a shorter lesson, optional reference material, and nowhere. Combining two lessons works when they support one action and the learner benefits from seeing them together. Relocating works when the information is helpful but not required for the promised result.
When you cut a module, check the transitions on either side. Remove claims such as “as we covered earlier” if the earlier explanation has gone. Add a sentence that supplies any missing context. Then walk through the course as a learner, completing the exercises rather than merely reading the outline. A curriculum is only shorter if the learner’s route is shorter and still complete.
Make the revised course easy to finish
Once the curriculum is stable, put the work in a format that supports the way people will use it. If you sell a hosted course, store.fan’s online courses feature can keep lessons and course video in one storefront rather than sending learners through a collection of separate links. That does not fix a crowded curriculum, but it removes one source of friction between the next lesson and the next practice task.
You can also use a short description for each module: the outcome, the practice, and the condition for moving on. Keep those three items consistent. If you sell the course through store.fan, the storefront can sit at store.fan/username, while the course itself carries the fuller learning path. The free plan is link-in-bio only; paid plans start with a 14-day trial. Store.fan takes 0% of sales, although Stripe’s own processing fee still applies, and money goes directly to your Stripe account.
There is no useful target length by itself. Keep enough explanation and practice for the learner to reach the stated result. A longer module can be appropriate when it contains a complete task; a short module can still be wasteful if it introduces an idea that is never used.
Usually, separate it from the core path rather than deleting it immediately. If beginners need it to complete the promised result, keep a simpler version. If it supports optional improvement, label it as reference or an extension so it does not interrupt the main route.
Keep your original notes or recording privately and watch for a repeated need. If the request connects to a real task or a common obstacle, add a focused resource rather than restoring the whole module. You can also turn the material into a separate download, workshop or future course.
Put your revised course in a storefront your learners can return to.
Start on store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



