Level 1 is the Content Engine: the repeatable workflow that takes a raw idea and turns it into a complete lesson package (script + visuals plan + publish-ready assets). In your outline, it starts by anchoring everything to a clear theme—business architecture—so you’re not creating random pieces, you’re building a connected body of work.
3) Draft the session script (before you worry about production)
With the research captured, you draft the session script and then use AI to polish it.
Practically, this means: define the learning outcome, outline the progression (hook → core idea → worked example → recap), and write the spoken version—short sentences, clean transitions, and explicit cues for where visuals will appear.
4) Choose the “voice format” (solo or dialogue)
If the lesson benefits from friction and clarification, you use your Meg-and-Baz dialogue format: you generate the script in a defined style using Claude or ChatGPT, and the dialogue becomes the teaching scaffold. This keeps the content human: one voice pushes forward, the other asks what the audience is thinking.
1) Theme → question → lesson shape
You begin by choosing one theme and framing it as a question worth answering (the “hook”). Then you decide the teaching container: course lesson, workshop segment, or podcast companion. This single decision prevents scope creep later because every asset you create must serve that one teaching moment.
2) Research capture (make the messy readable)
Next, you research the topic and store the material in NotebookLM so it becomes searchable and reusable—not just for this lesson, but for future content iterations. At this step you’re collecting the “raw clay”: references, quotes, examples, stories from practice, and the one or two diagrams that will do the heavy lifting.
5) Design the visuals from the script (not the other way around)
Once the script is stable, you extract image prompts for Midjourney and infographic prompts for Gemini (“Nano banana”) to generate keypoint charts and flow-style visuals, with your style presets already configured. The key move here is that visuals are evidence and explanation, not decoration: each visual must correspond to one sentence or one transition in the script.
6) Package for publishing (marketing + learning delivery)
Finally, you prepare the publishable bundle. You upload selected Midjourney images and supporting copy to WordPress for marketing (hosted on Bluehost), and you load the actual lesson content into Thinkific, including landing pages and workshop uploads.
In parallel, you can create a podcast version in NotebookLM and attach it inside the LMS as a companion resource.
By the end of Level 1, learners don’t just “have an idea.” They have a complete Lesson Kit: a teachable script (solo or dialogue), a mapped set of visuals (hero image + keypoint/flow chart), and a publish-ready upload checklist for website + LMS. Everything after this—automation, studio capture, switching, editing—gets dramatically easier because the meaning is already engineered.
Release Schedule
The Four Levels Pathway
This series is being released as a four-level pathway, because building a content and production capability isn’t something you “learn once” — it’s something you layer. Each level gives you a complete, usable capability on its own, and each release adds the next layer of power without forcing you to rebuild what you already have.
The schedule is designed around a simple idea: different people are starting from different places. Some of you already have a website, a course platform, and an audience — your constraint isn’t motivation, it’s throughput. You don’t need a studio tour; you need a faster, cleaner way to turn your thinking into publishable assets, using AI and workflow design.
Others want the opposite: you already have content ideas, but you want to deliver with confidence — a setup that lets you run workshops, record modules, and switch between camera, slides, demos, and examples like it’s normal. And some of you want the whole machine: content that’s coherent, production that’s reliable, and a publishing system that compounds week after week.
So the release schedule is staged in the same sequence the capability is built: