The Course Nobody Finishes

Two hundred and forty bought it. Thirty-one reached module three.

Picture the dashboard. Module one has a healthy green bar. Module two, about half. Then there’s a cliff. And module four, which holds the best work you’ve ever made, has been seen by almost nobody.

The easy explanation is that people are busy and don’t follow through. Some are. But two hundred and forty people didn’t all independently develop a motivation problem in the same week, at the same module. That’s a pattern, and I’d say patterns come from design.

Stop blaming the buyer

“They’re not motivated” isn’t a diagnosis. It’s where the thinking stops.

Put a room of teenagers in front of a badly sequenced lesson, and they’ll all drift at roughly the same point: the moment the task got too big without enough support. Put a couple of hundred adults through a badly sequenced course and you get the same shape, just in a dashboard a few weeks later. It’s the same cause. The learners aren’t the thing that changed.

Where they stop tells you what broke

The point where people drop off is useful information. I’d read it the way a teacher reads a test.

Where they stop	What it usually means
Partway through module one	They were promised an outcome and got housekeeping, a welcome video and your origin story.
Straight after the setup module	You made them do the boring admin before anything felt worth it.
Right before the first task needing judgement	You taught steps and never modelled a decision, so the first real choice feels like a trap.
After a two-week gap	There was no way back in. Opening the course meant admitting how far behind they were.

Each of those lines up with one of the fixes below.

Every fix starts with a symptom you can already see

1. Module one has to produce something real. Symptom: strong views on the first lesson, and a collapse by lesson four. Cause: your first module is context, housekeeping and credentials. Fix: give them an early win. By the end of module one, the buyer should be holding something finished and usable. Their actual headline, rewritten. Their real pricing page, audited. Small is fine, but it needs to be real. Move the welcome, the origin story and the platform tour into an optional “before you start” section outside module one, or cut them.

2. Cut the load to one idea per lesson. Symptom: they watch the whole video and still can’t do the task. Cause: too much at once. We can only hold a small amount of new information at a time, and a lesson that introduces a concept, a tool and a template all together spends most of that on the interface. Fix: separate the concept from the tool. Teach what a good client brief contains, and then, separately, show where to type it. Anyone who’s watched a class try to learn the maths and the calculator in the same lesson has seen how that goes.

3. Show a worked example before asking for independent work. Symptom: lots of people finish the videos, but hardly anyone submits work. Cause: you explained the method and then asked for the finished thing, and that gap is exactly where people stop. Fix: show one fully worked example with your reasoning attached. Not the polished sample, but the one with the second draft still in it and a note about why you cut the third paragraph. Then give them a second one where they finish the last third. Then they do one on their own. Teachers call this gradual release, and people who see worked examples first tend to get further with a lot less frustration. It costs you one extra recording. Get It Out of Your Head uses the same sequence to hand a process to someone on your team, and Why Your Team Won’t Use It uses it to roll out a new tool.

4. Make the next action very small and very specific. Symptom: they stop between lessons, not during them. Cause: “Now go and map your client onboarding” is a project, not an action. Fix: name the first physical move. “Open your last five client emails. Copy the first sentence of each into one document. That’s the whole task.” A task you can picture yourself starting is a task that actually gets started.

5. Getting it back out of their head beats adding more content. Symptom: by module five, they’ve clearly forgotten module two. Cause: they watched it once, and watching isn’t the same as learning. The instinct to add a recap video is understandable, but it’s more watching. Fix: ask them to pull it back out of their own memory. Two quick questions at the start of each lesson, answered before the video plays, with the answers shown afterwards: “Name the three things a brief has to include.” It feels harder for the learner, and that effort is a big part of why it sticks.

6. Show progress that means something. Symptom: the progress bar says 40% and they still feel like they’ve achieved nothing. Cause: a percentage measures how much of your content they’ve been through, not what they can now do. Fix: show them what they can now do and what they now have. “You’ve written your offer, your headline and three emails. Next up: the pricing page.” Keep a visible list of what they’ve made. Things they hold will always feel like more progress than things they watched.

7. Design for the person who missed a fortnight. Symptom: a long tail of people who stop and never come back. Cause: coming back feels awkward, and it isn’t clear where to start. Fix: build in ways back. A one-line “where you were up to” at the top of every module, and a short catch-up path that says exactly what to skip. Teachers do this constantly, because someone is always away, and the aim is to get them back into the work without making a thing of having fallen behind.

Re-entry block: paste at the top of every module

WHERE YOU WERE UP TO
Last module you finished [X]. By the end of it you had [the actual
artefact].

IF IT'S BEEN A WHILE
The two things you need from last time:
1. [one line]
2. [one line]
That's all. Don't rewatch anything.

START HERE
[One small, specific, physical first action. Under five minutes.]

Module one decides whether anyone sees module four

Run through this with your first module today:

1. Cut everything that comes before the first thing they do. Welcome, origin story, platform tour: out.
2. Name the outcome in one sentence: “By the end of this module you’ll have ___.”
3. Choose the smallest real version of that thing.
4. Show a worked example of it, thinking out loud as you go.
5. Give them a half-finished one to complete.
6. Set the task, sized in minutes, and phrased as a physical action.
7. Finish by naming what they now have, and add one line about what’s next.

When not to bother

If your course is an hour of information and it sells for eighty dollars, low completion probably isn’t costing you much. I’d leave it.

If you’re two weeks out from a launch, do fixes one and three and nothing else. A rebuild you half-finish is worse than the version you already have.

And the honest one. Sometimes a completion problem is really a promise problem. If people buy, open module one and leave straight away, the course probably isn’t what the sales page led them to expect, and no amount of retrieval practice will repair that. Read your refund emails and your first-week drop-offs before you redesign a single lesson, because fixing the wrong problem beautifully is still a month you won’t get back.

What you’ve got now

A way to read your drop-off point as a diagnosis instead of a verdict. Seven fixes, each with the symptom that tells you it applies. A module one rewrite you can do in one sitting, and a re-entry block you could have in every module by lunch.

Pick the fix that matches where your cliff is. Change one module, and watch that bar for a fortnight.