Start with the finished project, not the first lesson
Build your course backwards from the result students should be able to demonstrate.
You open your course outline and see twelve lesson titles, three bonus videos and a welcome module. It looks substantial. But you cannot yet answer the question a prospective student will ask: what will I be able to do when I finish? Start there. Define the finished project, then build only the lessons that help students complete it.
Name the result before the curriculum
“Understand email marketing” is a topic. “Write and schedule a five-email welcome sequence for a new subscriber” is a result. The second version gives you something to assess, and gives the student a clear reason to continue. Try describing the finished project as an object, a performance or a decision they can show someone else.
- 1Write one sentence beginning with: “By the end, you will have…”
- 2List the visible parts of that result. A welcome sequence might include its audience, promise, five subject lines, five email drafts and a sending plan.
- 3Choose the conditions that make the result acceptable. For example, each email may need one purpose, one call to action and a clear next step.
- 4Decide how students will demonstrate it: upload it, present it, publish it, run it or explain the choices behind it.
Turn the result into a backwards map
Once the finished project is defined, ask what must be true immediately before it can be completed. Then ask what must be true before that. This is a dependency map, not a list of topics. If students need to publish a landing page, they may first need a clear promise, a defined reader and a way to collect payment. Those dependencies determine the lessons.
| Finished-project requirement | Student must be able to | Lesson or practice |
|---|---|---|
| Clear promise | State who the project is for and what changes | Compare weak and specific promises |
| Usable structure | Arrange the main parts in a sensible order | Create a short project outline |
| Completed draft | Produce each part without waiting for more theory | Draft one section, then get feedback |
| Ready-to-use version | Check, publish or present the work | Run a final quality checklist |
The map also exposes lessons that do not earn their place. A history of your field may be interesting, but it is not automatically useful. Keep it only if it helps students make one of the required decisions or avoid a likely mistake. For a practical course, the outline is not the curriculum until practice appears.
Make every lesson move the project
Give each lesson a job. A job might be choosing, making, testing, revising or publishing. At the beginning, show students which part of the finished project the lesson will change. At the end, ask them to produce that change. This creates a visible chain between watching the lesson and completing the result.
- Begin with the decision or action, not the background information.
- Show one worked example, including a reasonable mistake or trade-off.
- Give students a task they can complete with the tools and time they actually have.
- Specify what they should bring to the next lesson.
- End with a check: what has changed in the project, and what still blocks progress?
You do not need to force every lesson into the same length. A short decision may need ten minutes; a guided build may need longer. The useful measure is not runtime. It is whether the student can point to a new, finished part of the project.
Design practice before recording
Write the student task before you write the script. If you cannot describe what they will do, the lesson may still be explanation rather than instruction. Put the task into the outline beside the teaching point, then record only the explanation needed to help them complete it.
A useful sequence is: show the target, explain one principle, demonstrate it on an example, set the task and give a check. Repeat that pattern until the project is complete. When you package the result as an online course, the same structure can guide your modules, lesson names and completion criteria.
Check the course against the finished result
Before publishing, take the finished-project checklist and trace every item back to a lesson or supported practice. If an item has no owner, students will discover the gap while trying to finish. If several lessons point to the same item without adding a new decision, combine them or remove the repetition.
You can also use the project as the course sales promise. Describe what students will make, who it is for and what they need before starting. On store.fan, you can sell and deliver the course from your own storefront, with money going straight to your Stripe account. If you later need to promote the course to people who are not ready to buy, email marketing can support a separate sequence without changing the curriculum.
Make it large enough to demonstrate the core transformation and small enough to finish with the time, tools and experience your students have. Remove optional polish first. A complete basic result is a stronger foundation than an ambitious unfinished one.
Keep one shared outcome, then offer a simpler starting route or optional extension. State the assumed knowledge before lesson one. You can also provide examples at different levels, as long as the required version remains clear.
Remove a lesson temporarily and ask whether students can still complete the next required part of the project. If they can, the lesson may be optional, combined with another lesson or better placed in a reference library. Check the result with a small number of real learners before recording replacements.
Build a storefront for the course your students can actually finish.
Start on store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.
