There are two ways to design a course. Forward: start with the topic, list everything about it, arrange it into a day. Backward: start with what people should be able to do afterwards, and only include what serves that.

Backward is harder to do and produces a much better course.

Step 1: Write the outcome as a sentence

“By the end of this session, participants can build a monthly dashboard that answers one clear question.” Specific, observable, tied to real work. If you can’t write this sentence, you’re not ready to design the course.

Step 2: List what someone actually needs to get there

Break the outcome into the handful of capabilities it depends on. For the dashboard example: choosing the right chart, shaping the data, laying out for one question, presenting the result. Four things. Not everything about spreadsheets — four things.

Step 3: Design practice for each capability

For every item on that list, what will participants do to build it? This is where most of the day goes. If a capability has no practice attached, it won’t stick.

Step 4: Add only the context that’s needed

Now go back and add the minimum “why” and background required for the practice to make sense. Usually far less than a forward-designed course includes.

Step 5: Cut anything that didn’t make it

Everything you know about the topic that doesn’t serve the outcome is a distraction. It goes in a handout, or it goes nowhere.

The result

A shorter course that does one thing well, with most of the time spent on people doing the work. Participants leave able to do the sentence from step one — which is the only thing you promised.

Designing a course backwards from "what should people be able to do"