Course curriculum outline: work backwards from the change.

One sentence decides the whole curriculum.

Outlines go wrong at the first line, not the fiftieth. Start with a topic and you get a syllabus — an organised tour of what you know. Start with a change of state and you get a course.

Write the end state before anything else, and write it in a shape that can be falsified. Every later decision in this guide — which modules exist, which lessons are required, what order they run in, when the course is finished — is settled by reference to this sentence. If it is vague, every one of those decisions becomes a matter of taste, and taste is what produces a twenty-hour course nobody completes.

Then write who it is not for

The second sentence nobody wants to write is the one that keeps the course finishable. Naming the adjacent audience you are not serving lets you decline, in advance, every lesson they would have needed — the beginner module for a course aimed at practitioners, the enterprise variant, the other platform. Without it those lessons arrive later, one at a time, each with a reasonable justification.

Write the day-one assumptions too: what a student must already have, know or be able to access. Anything on that list is a prerequisite you can state on the sales page instead of a module you have to teach — and an unstated prerequisite is the single most common reason a student stalls and blames themselves.

Modules are milestones, not chapters.

A chapter groups related information. A milestone moves a student from one state to the next. The difference is invisible in the table of contents and decisive in the completion rate.

Build the module list backwards. Ask what has to be true immediately before a student can do the thing in your end-state sentence. Then what has to be true before that. Keep going until you arrive at the state they are in on the day they buy — then read the list forwards. Those are your modules, and they are in the right order because you derived them from dependencies rather than from habit.

Give each one a milestone sentence of its own, in the same shape as the end state: by the end of this module the student can do a smaller specific thing, and the evidence is that something now exists which did not before. The test is blunt and worth applying without mercy — if you cannot write that sentence, the module is a topic, and topics are why courses feel long and finish empty.

What the math usually produces

A first course tends to land between four and eight modules. That is not a target and not a benchmark — it is what happens when you decompose one transformation honestly. Fewer than four usually means the transformation was small enough to be a workshop; more than eight usually means the last three modules serve a different person than the first three, which is a second course and often a better one.

An illustrative structure, purely to show the shape — a course that takes someone from never having run a paid workshop to having run one:

Notice that every right-hand entry is a thing, not a feeling. “Understands positioning” is not evidence. “A one-sentence promise and a named audience, written down” is — and it is also the thing module two needs as an input, which is how you know the sequence holds.

The distinction that decides the length.

Nearly every over-long course was built by somebody applying the wrong standard with good intentions. Both standards sound like diligence. Only one of them produces a course people finish.

The removal test

Go through the outline line by line and ask one question of every lesson: if this were removed, would the student still reach the end state? If the answer is yes, it is not a required lesson. That does not make it worthless — it makes it a resource, an appendix, a bonus or the seed of a future course. Move it off the required path instead of deleting it, and you keep the work while losing the weight.

The reason this is hard is that the material you most want to keep is usually the material you are proudest of, and pride is not correlated with necessity. It is much easier to apply the test to a bulleted line in an outline than to eleven minutes of finished video, which is the entire argument for doing this before you record.

Keep a written cut list with a reason beside each entry. Cuts made without a stated reason reappear three weeks later as a new module with a reasonable justification, and you will not remember why you removed it the first time.

One lesson, one idea, one action.

Lesson length is the wrong unit. The unit is the idea — and once you size lessons by ideas, the running times sort themselves out and stop being a thing you manage.

The fastest diagnostic is the title. If a lesson title needs an “and”, it is two lessons wearing one name. Splitting them costs nothing at outline stage and buys the student two completions instead of one unfinished session — which matters more than it sounds, because visible progress is what brings somebody back on a Tuesday evening.

Resist both directions of padding. Do not stretch a four-minute idea to eleven minutes because eleven feels more valuable; students experience the extra seven minutes as filler, and they are right. Do not compress two real ideas into six minutes to keep the course tight, either — that produces the lesson everybody rewatches, which is the most expensive kind of short.

What every lesson line should contain

The action is the part most outlines skip and the part that separates a course from a playlist. Write it as an instruction — “write the promise sentence for your workshop and paste it into the worksheet” — rather than a suggestion. Lessons you cannot write an action for are worth a second look: sometimes they are context that belongs inside another lesson, and sometimes they are the thing you wanted to include rather than the thing they need.

Build it in the order where mistakes are cheap.

Every stage of building a course is more expensive to redo than the one before it. Reordering a title costs seconds; rewriting a script costs an hour; re-recording a module costs a week. Work outward from the cheap end.

1. 01The end-state sentence. One sentence, three parts: who, the capability, the observable evidence. Everything else in the outline is downstream of it, so it is the only thing worth agonising over.
2. 02Module milestones, in reverse. Start at the end state and ask what has to be true immediately before it. Then before that. Stop when you reach the state a student is in on the day they buy. Read the list forwards — those are your modules.
3. 03Lesson titles only. No content, no notes, no length estimates. Titles are the cheapest possible draft of a course, and reading fifty of them in order will tell you within a minute whether the sequence works.
4. 04One line per lesson: the idea. The single thing this lesson teaches, written as a sentence. Any lesson where you cannot write one is either two lessons or none.
5. 05One line per lesson: the action. What the student does before moving on. This pass is where padding becomes visible — a lesson with no plausible action is usually a lesson you wanted to include rather than one they need.
6. 06Only now: scripts, slides, recording. The skeleton is the course. Once it holds together on one page, building it is production work rather than design work — and production work is much easier to delegate, batch and finish.

The rule that makes this work: nothing gets recorded until the whole skeleton exists on one page and survives being read top to bottom. One page is not a formatting preference — it is a constraint that forces you to see the sequence as a whole rather than as a series of modules you were happy with individually.

When the skeleton holds, the rest is production rather than design — which is why it is also the point where the work becomes delegable, batchable and finishable. How to record course videos picks up here.

Order is the part students feel and never name.

Nobody has ever written “the sequencing was poor” in a refund request. They write that it was overwhelming, or that they got busy, or that it was not what they expected — all of which are frequently sequencing.

1. 01Nothing depends on something taught later. Walk the outline once looking only for forward references. Every time a lesson quietly assumes a concept from three lessons ahead, you have a student who concludes they are the problem — and students who conclude that stop.
2. 02Module one produces something real. The most common way to lose a cohort is to open with context, history and mindset. Whatever your subject, find the smallest genuine result available in week one and put it there. Momentum in a self-paced course is the entire mechanism.
3. 03Setup work is a tax — move it or make it the win. Accounts, installs, configuration and paperwork are the least rewarding work in any course and they usually sit in module one because they come first logically. Either push them to the point of need, or frame the setup itself as the first milestone so finishing it feels like progress.
4. 04Hard things belong in the middle. The beginning needs momentum and the end needs a finish line. The middle is where students are committed enough to push through something difficult, which is exactly where the difficult thing should be.
5. 05Alternate the effort. Two demanding lessons back to back will lose people who would have completed either one alone. Follow a heavy lesson with a short, concrete, immediately satisfying one — pacing is a design decision, not an accident of how much you had to say.
6. 06The last lesson delivers the evidence. The final required lesson should end with the student holding the thing your end-state sentence promised. Not next steps, not a recap, and not an offer. Finish the course you sold; the next offer can be a separate screen.

The first two rules do most of the work. Prerequisite chains protect the student who is trying; the early win protects the student who is deciding whether to keep trying. A course that opens with three lessons of background before anybody does anything has already lost the people who bought it at eleven at night with real intent and a narrow window.

Sequencing pressure differs by format. A cohort carries a student through a hard module because everyone hits it in the same week and says so out loud; a self-paced student hits it alone on a Sunday. Cohort versus self-paced covers which one you are designing for, and it changes how much you can ask of any single module.

Fill in the brackets, in the order they appear.

Everything above, as one page you can paste into a document and work through. The bracketed placeholders are the decisions; the structure between them is the method.

Work top to bottom and resist the urge to jump to the lesson lists. The end state, the not-for line and the day-one assumptions take twenty minutes and remove roughly half the arguments you would otherwise have with yourself in the module blocks.

Three reads before anything gets recorded.

The outline is done when it survives being read three different ways. Each read catches a different class of problem, and all three together take under an hour.

1. 01The titles-only read. Hide everything except the lesson titles and read them in order. You should feel a student getting steadily more capable. Flat stretches are usually chapters that survived the milestone test by looking busy.
2. 02The stranger read. Give the outline to somebody in the audience — not a peer, not a friend who is being kind — and ask them to tell you what they would be able to do afterwards. If their answer is not your end-state sentence, the outline is not saying what you think it says.
3. 03The removal read. Walk every required lesson and ask whether the end state survives without it. Anything that survives moves to the resource library. Expect to move more than feels comfortable; that discomfort is the method working.

Then use the checks below as the gate between outlining and recording. They are deliberately mechanical — the point of a checklist is that it works on the day you are too close to the material to have judgement about it.