SkillMedev Course Outline Architect
Most paid courses are built forward from everything the creator knows, and the result is a 12-hour brain dump that students abandon by module two. Industry completion rates run a brutal 10 to 15 percent, and a course nobody finishes produces no results, no testimonials, and no word of mouth - which quietly kills every future launch. This skill designs the course backward from one transformation, so every module is a milestone and every lesson is one action, and it enforces the scope cuts that make finishing possible.
Install this skill first in the Course Creator Launch System pack. The transformation statement it produces is the raw material for course-sales-page and launch-email-sequence, and the completion targets it sets are what community-engagement-playbook exists to hit.
Work the example throughout: Dana, a productivity consultant with an 8,000-subscriber email list, building "Notion OS for Consultants" at $297.
Operating procedure
Follow the steps in order. The transformation comes first because every later decision - module count, lesson scope, what to cut - is judged against it. Deciding modules before the transformation is how brain dumps happen.
Step 1: Collect the inputs
Gather these from the creator. If a number or claim is a guess, label it a guess and move on.
- The topic and the creator's proof they can teach it (client results, own results).
- The specific student. One person, not a demographic. Dana's: a solo consultant juggling six tools who loses hours weekly to admin.
- The before state: what the student's week looks like now, in their words.
- The after state: what is concretely different when the course has worked.
- Price point and format (video, text, cohort). Default: self-paced video.
- Everything the creator wants to include - the full brain dump list. You need it in order to cut it.
Step 2: Write the transformation statement
One sentence: "By the end, a [specific student] goes from [before] to [after]." Concrete and checkable - a stranger could verify whether a given student got there.
Dana's: "By the end, a solo consultant goes from juggling six tools and rebuilding client docs from scratch - losing about 5 hours a week to admin - to running the whole practice from one Notion operating system and onboarding a new client in under a day."
This sentence travels: course-sales-page uses it as the above-the-fold promise, and launch-email-sequence seeds it through the pre-launch runway.
Step 3: List the milestones, one module each
Ask: what are the distinct states the student passes through between before and after? Each state a student could stand on and say "I have this now" is a milestone. One module per milestone - never per topic, never per week of the creator's calendar. Target 4 to 8 modules. Under 4 usually means the transformation is too thin for the price; over 8 means milestones are actually topics in disguise.
Step 4: Break modules into lessons - one action each
Each lesson teaches exactly one action the student performs before the next lesson. If a lesson description contains "and," split it. Video lessons run 5 to 12 minutes, with 8 minutes as the sweet spot; past 12 minutes, watch-through collapses. 3 to 7 lessons per module.
Step 5: Front-load the quick win
Design against the 10 to 15 percent industry completion average; this pack's shared design target is 35 percent or better completion. The single highest-leverage move: the student gets a visible, usable win within the first 20 minutes of module 1 - not setup, not theory, a thing that works. Momentum in module 1 predicts completion better than anything you do later. community-engagement-playbook builds its first testimonial-harvest moment on this same quick win.
Step 6: Cut to the 80 percent version
The 80 percent version ships. Hold every module and lesson against the transformation statement: if cutting it does not break the path from before to after, cut it. Cuts go to one of three places - a bonus vault (feeds the value stack in course-sales-page), version 2, or the trash. A $297 self-paced course should land at 3 to 6 hours of total video; more length is not more value, it is more places to quit.
Step 7: Hand off
- Each lesson's detailed plan (hook, teaching beats, exercise): lesson-plan-builder.
- Knowledge checks and module quizzes: quiz-generator.
- Sequencing objectives across a multi-course line or learning path: curriculum-mapper.
- Outline done: go to course-sales-page to sell it.
Worked artifact: Dana's outline
Notion OS for Consultants - $297, self-paced video. 6 modules, 28 lessons, average 8 minutes, about 3.7 hours total.
TRANSFORMATION: solo consultant goes from six scattered tools and ~5 lost
hours/week to one Notion OS, onboarding a new client in under a day.
M1 FOUNDATION - install the OS (5 lessons)
Quick win, lesson 2: working practice dashboard in 20 minutes.
M2 CLIENT PIPELINE - leads to signed (5 lessons)
Milestone: every lead and proposal tracked in one view.
M3 CLIENT DELIVERY HUB - projects run (6 lessons)
Milestone: active client work runs from one board.
M4 CLIENT PORTAL - share with clients (4 lessons)
Milestone: a client-facing portal live for one real client.
M5 KNOWLEDGE VAULT - SOPs and templates (4 lessons)
Milestone: reusable docs; nothing rebuilt from scratch.
M6 OPERATING RHYTHM - the weekly review (4 lessons)
Milestone: a 30-minute weekly review that runs the practice.
CUT LIST (80% version ships):
- "Notion API automations" module -> bonus vault (value-stack item)
- "Team & subcontractor features" -> version 2
- "Tool history / why Notion" talk -> trash
Template: outline skeleton
TRANSFORMATION: By the end, a [FILL: specific student] goes from
[FILL: before state] to [FILL: after state].
MODULES (one per milestone, 4-8):
M[#] [FILL: milestone the student can claim] ([FILL] lessons)
Lesson [#]: [FILL: one action] ([FILL] min)
...
QUICK WIN: [FILL: visible win inside first 20 minutes of M1]
CUT LIST: [FILL: item] -> bonus vault / v2 / trash
TOTAL RUNTIME: [FILL] hrs (target 3-6 for a ~$297 course)
Deliverable
A complete course outline: the transformation statement, 4 to 8 milestone-named modules with one-action lessons and runtimes, the module-1 quick win called out, a cut list with each item's destination, and total runtime - ready to hand to lesson-plan-builder per lesson and to course-sales-page for the promise and program section.
Do NOT
- Do not organize modules by topic or by the creator's table of contents. Topics are what the creator knows; milestones are what the student achieves. Topic-organized courses are the ones that hit 10 percent completion.
- Do not let any lesson carry two actions. "Set up the database and connect it to your dashboard" is two lessons.
- Do not open module 1 with philosophy, tooling history, or a 20-minute setup slog. The first win beats the full picture.
- Do not ship the 100 percent version. Every month spent producing the last 20 percent is a month of zero revenue and zero student results, and most of that 20 percent belongs in the bonus vault anyway.
- Do not exceed 12 minutes of video per lesson to "cover it properly." Split it.
Quality bar
- The transformation statement is one sentence, specific, and checkable by a stranger.
- Every module maps to exactly one milestone; every lesson to exactly one action; no lesson over 12 minutes.
- The quick win lands inside the first 20 minutes of module 1.
- The cut list is non-empty. A first outline with nothing to cut was not honest in Step 1.
- Module count 4-8, total runtime 3-6 hours, and the outline names where each cut item went.
Escalation and routing
Single-lesson depth goes to lesson-plan-builder; multi-course sequencing to curriculum-mapper; assessments to quiz-generator. Once the outline is locked, course-sales-page turns the transformation into the sales promise. If the course makes claims about financial, medical, or legal outcomes, have the claims reviewed by a qualified professional before selling against them.