Session 5: Course & Lesson Structure

A course is not a list of topics; it is a sequence in which each part makes the next one possible. That distinction is the whole design problem. Most courses are assembled by listing everything worth knowing and ordering it by subject — which is how the software's menus are organised, or how a textbook is divided — and the result is a sequence that makes sense to an expert and defeats a beginner.

So design from the end. Write the thing a graduate can do that they could not do before, then ask what they must be able to do just before that, and keep asking. The sequence that falls out is ordered by dependency rather than by taxonomy, and it usually begins somewhere different from where you would have started. A course built this way has the property that a student who completes week one can actually do something, which is what keeps them through week four.

Then scope honestly. The temptation is to include everything you know, and a course that tries to cover a whole profession in four weeks teaches none of it properly. An introductory practical course promises a specific, achievable competence — 'you will be able to build and publish a working site' — and delivers it, rather than promising mastery and producing confusion. Narrow and complete beats broad and shallow every time, and students can tell the difference from the first lesson.

A module is a coherent unit with its own deliverable — typically three to five lessons, ending in something the student has made. The deliverable is what makes a module feel like progress rather than a stretch of content, and it is what a graduate can point to afterwards.

Each module should be self-contained enough to be useful on its own. A student who completes module one and stops should still be able to do something real, not hold a fragment waiting for module three to make sense. This is both good teaching and practical reality, because people do stop, and a course where nothing works until the end produces people who abandon it halfway with nothing to show.

Then the spiral rather than the line. Return to earlier ideas at a higher level rather than treating them as finished. A concept introduced in module one and used again in module three with more complexity is learned far more reliably than one covered once and assumed retained. Most people do not learn a thing by being told it; they learn it by meeting it three times in different contexts.

A ninety-minute online lesson has a shape that works, and it is not ninety minutes of teaching. Open — five minutes: what today achieves and why it matters, connected to what they did last time. Demonstrate — fifteen: show the finished result, then how, narrating the reasoning. Guided practice — twenty: they do it with you watching, interrupting, correcting.

Independent practice — twenty-five: they do a variation alone while you move between people. Review and feedback — fifteen: look at what people produced, name the common error, correct it together. Close — five: what they can now do, what is next, what to do before the next session. The proportions matter more than the exact minutes, and the part most often sacrificed is independent practice, which is the part where learning happens.

The online-specific adjustment is that attention online decays faster than in a room. Nobody is physically present, the phone is in their hand, and the cost of drifting is zero. So change the mode every fifteen minutes or so — from watching to doing, from listening to typing, from you to them. A ninety-minute lecture delivered online loses most of the room by minute twenty, however good the material is.

The common mistake is treating these as sequential segments — twenty minutes of slides, then a demonstration, then an exercise. It produces a lesson in three disconnected parts, and the student does not see how the explanation relates to the thing they are about to do.

Instead, interleave them around one task. Show a slide with one idea, demonstrate that idea immediately, have them do it immediately, then move to the next idea. The cycle is short — five to ten minutes — and it means the explanation is never more than a few minutes from the action it explains. This is slower to prepare and much faster to learn, because nothing has to be held in memory waiting for its turn.

Then match the tool to the job. Slides carry structure, vocabulary and anything they will need to refer to later. Demonstrations carry process and judgement. The whiteboard carries explanation that has to be built in response to confusion. Exercises carry the learning itself. Using slides to explain a process, or a demonstration to convey a definition, wastes both.

Feedback belongs at specific points, and putting it in the wrong place wastes it. During guided practice it is immediate and individual — a quiet correction to one person while others work. In the review segment it is collective: the error three people made, shown and fixed for everyone, which is worth more than three private corrections because the two who did not make it learn to avoid it.

On submitted work it is individual and written, using the three-part structure — what was right, what was wrong, what to do next. At the end of a module it is summative and about the deliverable, telling the student what they can now do that they could not before, which is the information that keeps people enrolled.

The principle underneath all of it is that feedback is only useful while it can still change something. Feedback on the last assignment of a course changes nothing; feedback on the first exercise of lesson two changes everything after it. Design the course so the checking happens early and often, because a course whose only assessment is at the end is a course that discovers its failures too late to fix them.