How to Develop a Training
A methodology for breaking down any complex skill into a teachable, layered course
The Methodology
When you watch a master trainer deliver a training, the end result looks complex and polished. But it didn't start that way. Every great training is built the same way: by breaking the complex skill down into its smallest components and then teaching each one individually using a structured format.
The Three Principles
1. Chunk Down
Take the end-state skill (e.g., “deliver a professional training”) and decompose it into its smallest individual components. Each component should be something a student can isolate and practice on its own.
2. 4-MAT Each Component
For every component, cycle through the 4-MAT system: Why (motivation and context), What (the concept and content), How (a hands-on exercise isolating that one skill), and What If (debrief, iterate, expand). The exercise is the heart — it's where learning happens.
3. Layer Iteratively
Start with the most foundational component and have students practice it. Then introduce the next component and have them practice it on top of what they already learned. Layer after layer, the student builds up the full skill — and because each layer was small and manageable in isolation, the end result feels natural rather than overwhelming.
The key insight: by the end, the student hasn't just learned abstract concepts — they've built something real. Each layer was practiced in the context of their own presentation, their own project, their own work. When you stack all the layers together, it becomes a full-fledged, polished result.
Steps to Build Any Course
- 1Identify the end-state skill. What does the student look like when they're done? What's the polished result?
- 2Break it into smallest components. What are the individual skills that make up that polished result?
- 3Order from foundational to advanced. Which components must come first? Which build on others?
- 4Identify prerequisites. What does the student already need to know before each component? Teach prerequisites first, or verify they're already in place.
- 54-MAT each component. Create a Why, What, How (exercise), and What If for each one. The exercise should isolate that single skill.
- 6Layer the exercises. Each exercise adds to the previous ones. The student applies the new skill on top of everything they've already practiced, building toward the full end-state.
- 7Teach meta-tools separately. Tools like the 4-MAT system itself, the Milton Model, or other frameworks get their own 4-MAT cycle — then students immediately apply them to improve their own work.
Course: Public Speaking & Train the Trainer
Based on the ACME Trainers Training methodology — how Gina builds professional trainers layer by layer
Trainer State
1hWhy (10 min)
Everything starts with presence. If you can't hold still and be centered, every other skill falls apart. The audience reads your state before they hear your words.
What (20 min)
Trainer state is the foundation of all delivery. It means standing with stillness, centered posture, no unconscious fidgeting — just pure presence.
How (Exercise) (20 min)
Stand and look out at the room for 2 minutes with no unconscious movements. Keep hands still, maintain posture. Just be present.
What If (10 min)
Do it again, but this time a partner points a finger whenever they see a movement. This opens up peripheral awareness without focused attention on specific body parts.
Deliver Content from Trainer State
Requires: Trainer State50mWhy (5 min)
Trainer state in isolation is practice — now we connect it to real delivery. Can you maintain presence while actually saying something meaningful?
What (10 min)
Deliver your story, metaphor, or presentation content while maintaining trainer state — no hand motions, just voice and presence.
How (Exercise) (25 min)
Deliver your story or opening metaphor from trainer state with no hand movements. Focus on maintaining stillness while speaking.
What If (10 min)
Debrief: What was hard? Where did you notice yourself wanting to move? What changed about your delivery when you couldn't rely on gestures?
Eye Contact & Connection
Requires: Deliver from Trainer State50mWhy (5 min)
You can be perfectly still and perfectly centered, but if you're not connecting with individuals in the room, you're performing — not communicating.
What (10 min)
Intentional eye contact: pick one person, deliver a complete thought to them, then move to another. Don't scan. Don't look over heads. Each person you lock eyes with becomes an ally. The whole room feels connected because you connected one at a time.
How (Exercise) (25 min)
Re-deliver your content from trainer state. This time, lock eyes with one person per sentence or thought. Complete the thought before moving to the next person. No scanning.
What If (10 min)
How did it feel to hold someone's gaze for a full thought? Did the audience respond differently? Where did you feel the urge to look away?
Vocal Anchors
Requires: Eye Contact1hWhy (10 min)
Your voice is a powerful tool for creating emotional states in the audience. Specific vocal patterns can anchor specific responses — but only if used intentionally.
What (15 min)
Vocal anchoring — using tone, volume, pace, and pitch shifts to associate specific vocal qualities with specific states or concepts. The pause is your most powerful tool.
How (Exercise) (25 min)
Re-deliver your content with trainer state + eye contact, now adding intentional vocal anchors. Mark specific moments with distinct vocal shifts. Use at least one deliberate pause of 3+ seconds.
What If (10 min)
What did you notice about the audience response? Where did the vocal shifts land? What felt natural vs. forced? How did the pause feel?
Word & Phrase Anchors
Requires: Vocal Anchors55mWhy (5 min)
Beyond vocal tone, specific words and phrases can be anchored to create consistent responses. This is the verbal precision layer.
What (15 min)
Phrase anchoring and word anchors — selecting and repeating key words or phrases that become associated with specific states or concepts throughout a presentation.
How (Exercise) (25 min)
Re-deliver your content with all previous layers, now adding deliberate word and phrase anchors. Choose 2-3 key phrases to anchor throughout.
What If (10 min)
Did the audience pick up on the anchored phrases? How did layering word anchors on top of vocal anchors change the impact?
Satir Hand Movements
Requires: Word & Phrase Anchors1h 5mWhy (10 min)
Now that you can deliver with vocal precision and verbal anchors, we add the visual channel back — but intentionally, not as unconscious fidgeting.
What (20 min)
Satir categories of hand movements — specific, purposeful gestures that communicate congruently with your verbal message. Each gesture type has a distinct meaning and impact (leveler, blamer, placater, computer, distracter).
How (Exercise) (25 min)
Trainer demos each Satir category. Then re-deliver your content with all previous layers, now adding intentional Satir hand movements.
What If (10 min)
How did adding gestures back feel after practicing without them? What's the difference between these intentional movements and the unconscious ones from before?
Stage Anchors
Requires: Satir Hand Movements + Anchoring (prerequisite)1h 15mWhy (10 min)
The stage itself is a resource. Where you stand changes what the audience feels. You can move someone from one state to another just by moving to a different spot.
What (20 min)
Stage anchoring — using physical locations on stage to anchor different states, concepts, or resources. Builds on knowledge of anchoring and chaining anchors.
How (Exercise) (30 min)
Map out your stage with specific anchor points. Re-deliver your full presentation using all previous layers plus intentional stage movement.
What If (15 min)
How did the spatial component change the audience experience? Could you feel the anchors activating as you moved?
Storytelling & Metaphor Craft
Requires: Stage Anchors1h 15mWhy (10 min)
You've been delivering a story this whole time — but have you crafted it? The difference between a good trainer and a great one is the quality of their stories.
What (20 min)
Story structure for trainers: sensory-rich language (see/hear/feel), nested loops (open a story, teach, close the story), strategic placement of metaphors within 4-MAT, and matching stories to teaching points. Every story should create an internal representation in the listener.
How (Exercise) (30 min)
Take your opening story/metaphor and rewrite it using story structure principles. Add sensory language. Build a nested loop. Practice delivery with all previous layers.
What If (15 min)
Compare before and after. Did the audience's state shift more deeply? Could you feel the nested loop landing? What stories from your life could serve each teaching point?
Audience Calibration
Requires: Storytelling55mWhy (5 min)
Even the best-crafted presentation fails if you can't read the room and adjust in real time. The audience is always giving you feedback — most speakers just aren't looking for it.
What (15 min)
Reading audience state: skin color shifts, posture changes, breathing patterns, eye focus/defocus, energy level. Knowing when to speed up, slow down, insert an exercise, tell a story, or take a break. Using sensory acuity on a group level.
How (Exercise) (25 min)
Deliver your presentation to the group. A coach watches the audience and signals you (thumbs up/down) on whether the room is with you. Adjust in real time based on the signals.
What If (10 min)
What signals did you notice on your own? Where were you so focused on content that you lost the room? How do you build audience reading into your delivery habit?
The 4-MAT System (Meta-Tool)
1h 15mWhy (10 min)
You need a structure for organizing any presentation. 4-MAT gives you a universal framework that works for any topic.
What (20 min)
The 4-MAT system: Why (motivation), What (content), How (exercise), What If (integration). Every topic you teach goes through this cycle.
How (Exercise) (30 min)
Take your presentation and restructure it using 4-MAT. Identify your Why, What, How, and What If for each section.
What If (15 min)
Review each other's 4-MAT structures. Are the Whys compelling? Are the Hows truly experiential?
Milton Model (Meta-Tool)
Requires: 4-MAT System1h 20mWhy (10 min)
Your 'Why' sections need to move people emotionally, not just logically. The Milton Model gives you language patterns that bypass resistance and create openness.
What (25 min)
Milton Model language patterns — artfully vague language, embedded commands, presuppositions, metaphor, and other hypnotic language patterns used in persuasive communication.
How (Exercise) (30 min)
Take your 'Why' sections and rewrite them using Milton Model patterns. Practice delivering the updated versions.
What If (15 min)
Compare before and after. How did the Milton patterns change the feel of your Why? What patterns felt most natural to you?
Giving & Receiving Feedback
Requires: All delivery skills50mWhy (5 min)
Tomorrow you'll present and give feedback to each other. Feedback is a skill — bad feedback destroys confidence, good feedback accelerates growth.
What (15 min)
Feedback structure: what worked (specific, observable), what to develop (one thing, actionable), overall impact (how it felt as an audience member). Focus on the 12 skills you've learned — trainer state, eye contact, vocal anchors, word anchors, Satir movements, stage anchors, story craft, audience calibration, 4-MAT, Milton patterns.
How (Exercise) (20 min)
Watch a demo presentation. Practice giving structured feedback using the framework. Each person gives feedback on a different skill layer.
What If (10 min)
How was structured feedback different from 'that was good'? What did you notice when you had specific skills to look for?
Training Day Schedule
Presence & Voice
10:00 AM – 7:00 PMStories, Milton Model patterns, trance work — set the state for the day.
Teach presence and stillness. Exercise: stand for 2 min with no unconscious movement. Iterate with partner pointing at movements.
Deliver story/metaphor with no hand motions. Debrief what changed.
Teach intentional eye contact. Re-deliver with one person per thought. No scanning.
Teach vocal anchoring and the power of the pause. Re-deliver with intentional vocal shifts.
Layer word/phrase anchors on top of vocal anchors. Practice with 2-3 key phrases.
Demo Satir categories. Re-deliver with all layers plus intentional gestures.
Debrief the day. Six layers stacked. What landed? What shifted? Future pace tomorrow.
Structure, Craft & Calibration
10:00 AM – 7:00 PMStories, Milton patterns, trance work. Callback to Day 1 — re-anchor trainer state.
Teach stage anchoring. Map anchor points. Full delivery with all 7 layers stacked.
Story structure, sensory language, nested loops. Rewrite and re-deliver your opening story.
Reading the room in real time. Practice delivering while a coach signals audience state.
Teach 4-MAT framework. Restructure your presentation into Why/What/How/What If. Peer review.
Teach Milton patterns. Rewrite your Why sections with hypnotic language.
Teach feedback structure. Practice giving specific, layered feedback on a demo.
Tomorrow is presentation day. Tonight: finalize your presentation with all 12 layers. You're ready.
Final Presentations & Coaching
10:00 AM – 7:00 PMStories, trance work — create a peak state. This is performance day. Anchor confidence and presence.
Quick run-through in pairs. Final adjustments. Shake out nerves. Get into trainer state.
First half of students deliver their full presentation. Video recorded. Full audience. Real stakes.
Second half of students deliver. Video recorded. Everyone presents today.
Watch key moments from each presentation on video. Self-assessment first, then structured peer feedback, then trainer coaching. Focus on the 12 skill layers.
One-on-one time with the trainer. Personal strengths, development areas, next steps for each presenter.
Anyone who wants to re-deliver a section incorporating feedback. Immediate application of coaching.
Celebrate the transformation. Compare Day 1 presence to now. You built a professional presentation layer by layer. What's next for you as a trainer?
The End Result
By the end of this course, every student has built and delivered a complete, professional presentation — with trainer state, eye contact, vocal anchors, word anchors, Satir hand movements, stage anchors, crafted stories, audience calibration, 4-MAT structure, and Milton Model language. They've seen themselves on video, received structured coaching, and had the chance to immediately apply feedback. Each piece was learned in isolation, layered on, and the final delivery is polished, intentional, and their own.
Course: AI Mastery
Taking someone from basic ChatGPT usage to building real projects on their own server — layered the same way
Using AI in the Browser
55mWhy (10 min)
AI is already changing how people work, create, and solve problems. Everyone has access to tools like ChatGPT and Claude — but most people barely scratch the surface.
What (15 min)
Introduction to conversational AI. What ChatGPT and Claude are, what they can do, how they work at a high level. The browser is your starting point.
How (Exercise) (20 min)
Use ChatGPT or Claude to solve a real problem you have right now — a work task, a creative project, a question you've been stuck on. Experience what's possible.
What If (10 min)
What surprised you? What worked better than expected? What didn't work? Where did you feel the limits?
Prompt Engineering
Requires: Using AI in the Browser1h 15mWhy (10 min)
The quality of what you get out of AI is directly proportional to the quality of what you put in. A well-crafted prompt can be the difference between useless output and something genuinely valuable.
What (20 min)
Prompt engineering fundamentals — how to give context, specify format, use role prompts, chain prompts, iterate on results, and get consistently better outputs.
How (Exercise) (30 min)
Take the problem you worked on in Step 1 and re-approach it with structured prompts. Compare the results. Refine until you get something you'd actually use.
What If (15 min)
What changed when you prompted more deliberately? What patterns gave you the best results? Share your best prompt with the group.
Voice-to-Text
Requires: Prompt Engineering45mWhy (5 min)
Typing is a bottleneck. The fastest way to get your thoughts into AI is to speak them. This dramatically increases your speed and changes how you interact.
What (10 min)
Voice-to-text tools and workflows — using dictation to compose prompts, capture ideas, and have more natural conversations with AI. Speak naturally, refine after.
How (Exercise) (20 min)
Re-do your previous exercise, but this time use voice-to-text for your prompts. Speak your thoughts naturally, then refine the output.
What If (10 min)
How did it feel different? Were you faster? Did speaking change what you asked for? What's your preferred workflow now — typing, speaking, or a mix?
AI Tools Beyond Chat
Requires: Voice-to-Text1h 10mWhy (10 min)
ChatGPT and Claude are just the beginning. There's a growing ecosystem of specialized AI tools that can handle specific tasks better — meeting notes, research, writing, and more.
What (20 min)
Survey of AI tools: Granola (meeting intelligence), Perplexity (research), AI writing assistants, image generators, and other purpose-built tools. When to use what.
How (Exercise) (25 min)
Pick one new tool (like Granola) and use it for a real task this week. Document what it did better than a general chatbot and where it fell short.
What If (15 min)
Share your findings. Which tools earned a permanent spot in your workflow? Which were overhyped? How do they complement each other?
AI Limitations & Critical Thinking
Requires: AI Tools Beyond Chat55mWhy (10 min)
AI is powerful but it's not magic. It hallucinates, it's confident when wrong, and it can reinforce biases. If you don't know the failure modes, you'll trust it when you shouldn't.
What (15 min)
When AI gets it wrong: hallucinations, confident fabrication, outdated information, bias amplification, context window limits. The skill of verification — checking AI output against reality before acting on it.
How (Exercise) (20 min)
Give AI a task where you know the right answer. See where it gets it right and where it goes wrong. Try to make it hallucinate. Learn what overconfidence looks like.
What If (10 min)
How does knowing the failure modes change how you use AI? What's your verification workflow? When do you trust and when do you check?
From Browser to IDE
Requires: AI Limitations1h 15mWhy (10 min)
The browser is great for conversations, but real building happens in a development environment. An IDE is where you go from asking AI questions to building things with AI.
What (20 min)
What an IDE is (Integrated Development Environment), why it's valuable (file management, code execution, AI integration), and how tools like Cursor or VS Code with AI extensions change what's possible.
How (Exercise) (30 min)
Install an IDE. Open it. Create your first file. Get comfortable with the interface — files on the left, editor in the middle, terminal at the bottom.
What If (15 min)
What feels different about working here vs. the browser? What's intimidating? What's exciting? What could you build here that you couldn't in a chat window?
First Projects
Requires: From Browser to IDE1h 30mWhy (10 min)
The best way to learn is to build something real. Not a tutorial — something you actually want to exist. When it's yours, the motivation is built in.
What (15 min)
Project planning basics — scoping something small enough to finish but meaningful enough to care about. File structure, saving, running your work.
How (Exercise) (45 min)
Pick a project: a simple website, a script that automates something tedious, a tool that solves a personal problem. Build the first version with AI assistance.
What If (20 min)
Demo your project to the group. What did you learn by building? What would you do differently next time? What do you want to add?
Claude Code in the IDE
Requires: First Projects1h 25mWhy (10 min)
Now that you can build things, you can bring AI directly into your development workflow. Claude Code works right in your terminal — it reads your files, writes code, runs commands, and builds alongside you.
What (20 min)
Claude Code — how it works, how it reads your project context, how to give it tasks, how to review and guide its work. The difference between chatting with AI and collaborating with AI.
How (Exercise) (40 min)
Take your project from Step 7 and extend it using Claude Code. Add a feature, fix a bug, or refactor something — working collaboratively with the AI in your actual codebase.
What If (15 min)
How was this different from copy-pasting code from a chat window? What did Claude Code do that surprised you? Where did you need to step in and guide it?
Project Memory & CLAUDE.md
Requires: Claude Code55mWhy (5 min)
Every time you start a new conversation with AI, it forgets everything. Project memory fixes that — it gives AI persistent context about your project, your preferences, and your conventions.
What (15 min)
CLAUDE.md files — how they work, what to put in them (project structure, commands, conventions, preferences). Memory systems that let AI remember across sessions. Building a 'second brain' that makes AI more useful over time.
How (Exercise) (25 min)
Create a CLAUDE.md for your project. Include: what the project does, how to run it, key decisions you've made, your preferences. Test it — start a new Claude Code session and see how much better it understands your project.
What If (10 min)
What changed when Claude Code had context? What else should go in your CLAUDE.md? How does this change your workflow for future sessions?
VPS & Remote Development
Requires: Project Memory1h 35mWhy (10 min)
Your laptop is limited — it sleeps, it's local, it's one machine. A VPS gives you a persistent, always-on environment where your projects live and run 24/7.
What (25 min)
What a VPS is, how to set one up, how to connect via SSH, and how to run your IDE and Claude Code on a remote server. Your projects gain persistence, memory, and availability.
How (Exercise) (45 min)
Set up a VPS. SSH into it. Clone your project. Run Claude Code on the server. Get your project running remotely.
What If (15 min)
What changes when your projects live on a server instead of your laptop? What can you build now that you couldn't before?
Automation & Cron Jobs
Requires: VPS55mWhy (5 min)
The real power of a server is that it works while you sleep. Automation turns your projects from things you run into things that run themselves.
What (15 min)
Cron jobs, scheduled tasks, background processes, webhooks. How to make your AI-built tools run on a schedule, respond to events, or stay always-on. Monitoring — knowing when something breaks.
How (Exercise) (25 min)
Take your project and add automation: a cron job that runs daily, a web endpoint that's always available, or a background process that monitors something. Make it do work without you.
What If (10 min)
What just changed? Your project runs 24/7 now. What else could you automate? What problems in your life or work could a persistent, automated tool solve?
Training Day Schedule
Foundations — From Chat to Craft
10:00 AM – 7:00 PMStories about AI transformation. Milton patterns about possibility and change. Trance work — future pace what they'll be able to do by end of course.
Intro to ChatGPT/Claude. Exercise: solve a real problem right now. Debrief surprises and limits.
Teach structured prompting. Re-approach the same problem with better prompts. Compare results.
Teach voice workflows. Redo exercise using dictation. Debrief speed differences.
Survey Granola, Perplexity, image gen, etc. Pick a tool and use it for a real task.
Failure modes, hallucinations, verification. Try to make AI fail. Build a checking habit.
What an IDE is. Install it. Create first file. Get comfortable with the interface.
Debrief the day. You went from chatting to an IDE. Homework: think about what you want to build.
Building — From IDE to Server
10:00 AM – 7:00 PMStories about building and creation. Milton patterns about capability and identity shift. Trance work — who you're becoming as a builder.
Complete IDE setup. Run a file. Comfortable with files, editor, terminal.
Scope a real project. Build first version with AI assistance. Get something working.
Teach Claude Code. Extend your project using AI as a collaborator. Add a feature or fix a bug.
Create a CLAUDE.md for your project. Test persistent context across sessions.
Set up a VPS. SSH in. Clone project. Start running Claude Code on the server.
You built something real and it lives on a server. Tomorrow: automation, polish, and demos.
Automation, Polish & Final Demos
10:00 AM – 7:00 PMStories about systems and leverage. Your project runs while you sleep. Trance work — the builder identity is yours now.
Complete VPS setup. Get project fully running remotely. Troubleshoot any issues.
Add a cron job, webhook, or always-on process. Make your project work without you.
Open build session. Improve your project using everything you've learned. Add features, fix bugs, make it yours. Trainer circulates for 1:1 help.
Each student demos what they built — running on their VPS, automated, persistent. Show the group what you made and how it works.
Where do you go from here? Project ideas, learning paths, communities. Each person shares their vision for what they'll build next.
Three days ago you were chatting with AI in a browser. Now you have your own server running your own automated projects. You're a builder now.
The End Result
By the end of this course, every student has gone from basic ChatGPT usage to running automated projects on their own server with AI as a collaborator. They understand prompt engineering, voice workflows, AI limitations, IDE development, Claude Code, project memory, VPS infrastructure, and automation. Each step was small and practiced with something real. The final result looks advanced, but it was built one layer at a time.