If you have a growing list of courses but rarely use what they teach, the next step is not necessarily to find a better course. It is to connect one thing you have already learned to a real task. Watching a lesson gives you exposure to an idea; being able to explain it shows some retention; using it appropriately in a task is application. These are different outcomes, and finishing more content does not guarantee the last one.
You do not need to abandon courses or feel guilty about the ones you have not finished. Instead, treat learning resources as tools for solving a current problem. Choose a task, find the smallest relevant lesson, try one technique, and review what happened. That shift makes it easier to see what you can use now—and what you still need to learn.

Measure learning by what you can do, not what you have watched
Course platforms make completion visible: there are modules to finish, quizzes to pass and progress bars to fill. Those markers can be useful, but they mainly show that you interacted with the material. They do not, on their own, show that you can use the skill in a different setting. Replace the next purchase with a practice session that fits the time available.
It helps to separate three stages:
- Exposure: You watched, read or listened to an explanation.
- Retention: You can recall or explain the main idea without simply looking at the lesson.
- Application: You can use the idea appropriately in a task that matters to you.
For example, watching a lesson on giving feedback is exposure. Explaining its main principles from memory is a sign of retention. Preparing and delivering feedback on an actual draft is an attempt at application. The attempt may go well or reveal something you need to practise; either way, it tells you more about your current ability than another completed video does.
This distinction is not a reason to dismiss courses. Instruction can introduce useful concepts and show what good practice looks like. It simply means that learning content and developing a usable skill are not the same activity. If your aim is to write clearer proposals, make a presentation, build a budget or code a small feature, your learning plan should eventually include that kind of work.
Start with a problem that is already in front of you
A course can feel like progress even when its connection to your everyday life is vague. A current problem gives learning a clearer purpose and helps you decide what is relevant. Rather than asking, “What would be useful to know?”, ask, “What am I trying to do that I cannot yet do well?”
Make the problem specific enough to act on. “Get better at communication” is broad. “Give a colleague clear feedback on the draft they sent me” points to a task. “Learn coding” can become “write a script that renames these files,” if that is appropriate to your experience and the project. “Improve my finances” might become “make a simple monthly budget and compare it with my recent spending.”
Then identify what is getting in the way. Perhaps you do not know how to structure feedback, which spreadsheet formula to use, or how to organise the opening of a presentation. You may not need a complete course on the subject. A short explanation, a chapter, a worked example or one relevant module may be enough to help you make a first attempt.
This is also a useful filter before enrolling in another course. Try to name the specific gap it would address and the task where you expect to use the material. If you cannot name either, you may be browsing for a sense of direction rather than seeking instruction for a defined need. That is not a failure; it is a reason to clarify the problem before adding more content.
Take one usable idea from a lesson
When you do choose a resource, avoid making “finish the whole course” the only acceptable outcome. Look for one idea, process or example that could change how you handle the task you identified. Write it in your own words and note when it might be useful.
For instance, after a lesson on presentations, your usable idea might be to state the main point before adding supporting detail. After a lesson on budgeting, it might be to separate fixed costs from flexible spending before deciding what to adjust. In a coding lesson, it could be a particular way to test a function with a small example. Keep the idea narrow enough that you can try it soon.
Before looking back at your notes, try to recall the idea or explain the method from memory. Then check the lesson and fill in what you missed. This kind of retrieval practice—bringing information to mind rather than only rereading it—has strong support as a learning technique. A review by Dunlosky and colleagues rated practice testing and distributed practice among the more useful techniques they assessed, while rereading and highlighting alone received weaker support (Dunlosky et al., 2013). For material you have already studied, check what you can retrieve before reopening the explanation.
Recall is not a test of whether you are talented or suited to the subject. It is a way to find out what you can currently bring to mind without prompts. If you cannot remember a step, that gives you a precise reason to revisit it. If you can explain the idea but are unsure how to use it, the next step is a practical attempt, not necessarily another round of note-taking.
Plan a small attempt in a real setting
Choose an attempt that is limited enough to do soon and similar to the situation where you want the skill to be useful. If you are learning to give feedback, practise on a real piece of work rather than only summarising a feedback framework. If you are learning to write, revise one paragraph for clarity. If you are learning to code, apply the concept to a small part of an actual project or a realistic exercise.
It can help to specify the attempt with an if–then plan: “If I finish my Monday team meeting, then I’ll use the feedback technique on the next draft.” Or: “When I sit down to prepare the presentation, I’ll write the main point before building the slides.” This format links a particular situation to an intended action. Research on implementation intentions supports if–then planning as a general aid to goal achievement; using it to apply course material is a practical adaptation, not evidence that it specifically solves course collecting (Gollwitzer and Sheeran, 2006).
Make the first attempt small, but not so artificial that it avoids the skill you want to develop. A useful plan identifies:
- The situation: When and where will you try it?
- The action: What will you do, in observable terms?
- The output: What will exist when you finish—a draft, a conversation, a tested piece of code or a completed budget?
- The support needed: Do you need an example, a colleague’s feedback, suitable software or expert supervision?
Plans cannot create a worthwhile opportunity or supply missing resources. If your task depends on access you do not have, or you need instruction before attempting it safely, deal with that constraint rather than treating a missed plan as a lack of discipline.
Get feedback and decide what the result tells you
After trying the technique, look at the result. Did it help with the task? What felt unclear? What would you change next time? If possible, ask someone who understands the work to respond to the output, not just to the amount of effort you put in. A specific question is more useful than asking whether it was “good”: “Was the main recommendation clear?” or “Does this code handle the case I missed?”
Keep the first attempt in perspective. A weak result does not prove that the lesson was useless or that you cannot learn the skill. It might show that you misunderstood a step, chose a task that was too difficult, need more practice, or would benefit from better feedback. Conversely, feeling confident after a lesson—or passing a quiz—does not by itself demonstrate that you can perform well in a real situation.
Research on retrieval practice includes findings about transfer to some new tasks, but transfer is not automatic. A meta-analysis by Pan and Rickard found benefits across varied measures of transfer, supporting the idea that testing what you have learned may help beyond simple recall. It does not establish that a generic online course will improve performance at work or that recalling a concept guarantees you can use it well (Pan and Rickard, 2018). Practice that resembles the intended use, followed by feedback where available, is a more grounded way to assess application.
Keep a simple record of behaviour or output rather than course consumption. “Used the framework in two client proposals” or “completed a draft and received feedback” tells you what you tried. “Watched three modules” tells you what you watched. You do not need a detailed tracker: a short note about the task, what you used and what you learned from the result may be enough.
Revisit the material instead of starting from zero
Once you have made an attempt, return to the key idea later. First try to recall it without opening your notes; then check what you missed. Spacing those brief retrieval attempts across time is different from reviewing the material repeatedly in one sitting. Research reviews support distributed practice, but there is no single review interval that suits every subject, learner or purpose. The timing depends partly on what you need to remember and for how long.
You can make the review practical by asking yourself questions tied to the work: “What was the sequence I used to prepare the feedback?” “What did I test before changing the code?” “Which assumption did my budget depend on?” If you cannot recall a detail, look it up and use it again when a suitable task comes along.
MIT’s overview of self-regulated learning describes a broad cycle of planning, monitoring and evaluating learning strategies. That is a useful way to think about the process: set a goal, notice what happens as you work, and adjust the next attempt (MIT Teaching + Learning Lab, “Self-regulation”). The point is not to build an elaborate system around every course. It is to let experience shape what you learn next.
Choose the next course only when it fills a real gap
After an attempt, you have better information than you did while browsing. Perhaps the technique worked and you want to practise it again. Perhaps you found a specific gap that needs more instruction. Or perhaps the task was unclear, the conditions were unsuitable, or you need someone with relevant expertise to guide you.
Before buying or starting another course, ask:
- What task am I trying to do?
- What specific knowledge or skill is missing?
- Does this resource address that gap, or is it simply related to the broad topic?
- How will I try what it teaches?
If you have a clear answer, a new resource may be a sensible next step. If you do not, you could postpone the decision while you try the material you already have. That pause is an optional decision aid, not a proven treatment for course-buying habits. There is no need to set an arbitrary limit on courses or assume that collecting them reflects a clinical problem.
Some abilities also require more than individual practice. High-stakes work may call for qualified instruction, supervised experience, safe conditions or formal credentials. In those cases, a self-directed exercise is not a substitute for the guidance and standards the task requires. The practical aim is not to learn everything alone; it is to make each resource serve a clear next step.
To get more from what you learn, keep the cycle modest: name a current problem, choose one relevant idea, try it on a suitable task, and use the result to decide what comes next. The course can introduce the method. Your attempt shows what you can do with it.