How to Take Notes on an Online Course

Online courses fail at a rate that would be scandalous anywhere else. Large-scale analysis of MOOC data has put completion in the single-digit percentages, and the pattern holds across platforms and subjects.

Note-taking is not the whole reason, and it is genuinely part of it. The format hands you two things a lecture hall never did — a pause button and no deadline — and both work against you in ways that are easy to miss.

What the pause button does

In a live lecture you cannot stop the speaker, so you are forced to compress: you decide what matters, write it briefly, and keep listening. Compression is where understanding happens.

With a pause button, you can transcribe everything. So people do. The result is a complete, tidy, useless record produced without a single act of judgement — and the strong feeling of having studied. This is the illusion of competence with better production values.

The second effect is worse. Pausing every twenty seconds turns a forty-minute lecture into two hours, which makes the course feel enormous, which is how it gets abandoned in week three.

The method

Watch a segment. Then pause and write from memory.

Not while watching. After. Five to ten minutes of video, then stop and write what you understood without scrubbing back.

This inverts the usual approach and it is the whole technique. You are retrieving rather than transcribing, which is what makes material stick — the testing effect is among the most robust findings in the learning literature, and this is the cheapest possible way to apply it.

The gaps you find are the point. If you cannot reconstruct a step, you did not understand it, and you now know exactly which thirty seconds to rewatch. Transcribing hides that; retrieving exposes it.

Expect to write less than half what you would otherwise, and to remember considerably more.

Do not take notes on everything

Most online courses contain a lot of material that does not need notes: setup instructions, things you already know, the instructor's anecdotes, anything in the documentation.

Worth writing:

  • The mental model. How the pieces fit — usually stated once, briefly, and it is the thing that makes everything else make sense.
  • What surprised you. Where the subject did not work how you expected.
  • The gotchas. "This fails if X." These are what you will need later and are rarely in the docs.
  • Your questions. Things unexplained, which become the list you look up afterwards.

Not worth writing: syntax, commands, API details, anything the reference material already covers permanently. See how to take programming notes for the same principle in more depth.

Speed and retention

Watching at 2x feels efficient. It reliably reduces how much you retain and, more relevantly here, how much you notice is worth noting.

A defensible compromise: 1.5x for material you half-know, 1x for anything genuinely new, and if a course is only worth 2x it probably does not need notes at all — which is a legitimate conclusion, not a failure.

The thing that actually decides completion

Notes are a supporting act. The variable that predicts whether a course changes anything is whether you build something with it.

A course watched produces nothing. A course applied to a real project produces both a reason to continue and the retrieval practice that makes the material stick. The notes then have a job — they are what you consult while building, which is also the only reliable test of whether they were any good.

So the practical structure is:

  1. Decide the project before starting the course.
  2. Watch a section, write from memory.
  3. Apply it to the project immediately, before the next section.
  4. Note what broke, because that is where the real learning is.

Step three is what most people skip, and it is the difference between finishing and drifting away in week three.

Handling the backlog

A specific failure worth naming: buying courses in sales and accumulating a library you feel guilty about. The guilt makes you less likely to start anything, not more.

Treat it as an antilibrary — a map of things you might learn — rather than an obligation. Then pick one, with a project attached, and ignore the rest until it is done. One finished course is worth more than nine half-watched ones, and the arithmetic there is not close.

Afterwards

The course ends and, without a deadline or an exam, nothing forces consolidation. Two small habits carry most of the value:

  • One page from memory, the day after finishing. What this was about, what I can now do, what I still cannot. See how to write a summary.
  • Revisit once a few weeks later. Not rewatching — testing yourself against your own notes. See spaced repetition.

Where ClairMind fits

The useful thoughts about a course rarely arrive during it. They arrive later — the connection to a problem at work, the realisation of what the instructor actually meant, the thing you want to try. Those are lost by default because the course is closed and you are somewhere else.

Clair Mind is built for that: one gesture to capture it, connected to the rest of your notes so it resurfaces when the relevant problem comes round.

More in how to take notes from a video, how to study from your notes, and how to take notes.

More in How-to Guides

62 more notes on this branch.