π½οΈ Lesson 7.2: Project β A Lesson / Training Deck
A pitch persuades in a few minutes; a training deck teaches, and that changes everything about how it's built. Here the audience isn't deciding whether to say yes β they're trying to learn something and carry it away, sometimes with you in the room and sometimes watching a recording at midnight. In this lesson you'll learn the conventions of the teaching genre β objectives up front, chunked sections, worked examples, checks for understanding, and a clean recap β and build a short multi-section training deck designed for reuse (as a template) and for async viewing (exportable to video). Along the way you'll get your first real taste of accessibility, which becomes its own lesson in 8.2.
π What You'll Learn
By the end of this lesson, you will be able to:
- Structure a lesson deck with objectives up front, chunked sections, and a recap
- Use Section Header layouts and consistent content layouts to make a long deck navigable
- Build worked examples and checks for understanding that make learning stick
- Write speaker notes as a facilitator script and use animation reveals sparingly to pace ideas
- Design the deck for reuse as a template and for async export to video, with accessibility in mind
β±οΈ Estimated Time: 60 minutes
π― Project: Build a short, multi-section training deck on a topic you know well β objectives, two or three teaching sections with a worked example and a check each, and a recap.
In This Lesson
How Teaching Decks Are Different
The pitch deck you built last lesson had one goal β a yes β and every slide bent toward it. A training deck has a subtler, harder goal: change what someone knows or can do, and make it stick after they leave. That difference reshapes almost every design decision. A pitch hides detail to keep momentum; a lesson often needs the detail visible, because the learner will refer back to it. A pitch is delivered once, live, at full energy; a lesson is frequently reused, handed to a colleague, or watched asynchronously at the viewer's own pace. And a pitch audience is captive for five minutes, while a learner may be forty minutes in and fading β so pacing and structure matter enormously.
The teaching genre has its own hard-won conventions, and they mirror the very course you're reading right now: state the objectives up front so the learner knows where they're going, break the material into digestible chunks with clear section markers, show worked examples rather than just telling, pause to check understanding, and recap at the end so the key points consolidate. These aren't decoration β they're how human memory actually works. People learn in chunks, remember what they had to retrieve, and forget what they only heard once without a summary. A good training deck is built around that reality.
Crucially, a training deck is also usually infrastructure, not a one-off. You build the onboarding deck once and run it for every new hire; you build the workshop once and give it four times a year; you record it once and let a hundred people watch on demand. That means two design goals a pitch never has: it should be easy to reuse and update (which is exactly what the Slide Master and layouts give you), and it should stand on its own without you when exported to video or shared as a file. Design once, teach many β that's the training-deck philosophy, and it's the course's "design once via the theme and master" idea taken to its natural conclusion.
π§ Mindset
Design for the learner who is tired, distracted, and half-remembering the last section β because that's your real audience by slide twenty. Every objective you state, every section marker, every recap is a handrail for that person. If a stranger could open your deck cold and follow it without you narrating, you've built something durable. That's a higher bar than a pitch, and clearing it is deeply satisfying.
The Anatomy of a Training Deck
A training deck has a predictable skeleton, and leaning on it makes both building and learning easier. Here's the structure, section by section, and what each part is for:
| Part | Slides | What it does for the learner |
|---|---|---|
| Title & framing | Title, "why this matters" | Sets the topic and gives a reason to care before the work begins |
| Objectives | "By the end you'll be able toβ¦" | Tells learners exactly where they're going β a map for the journey |
| Section 1β¦N | Section header + teaching slides | One concept per chunk, each marked and self-contained |
| Worked example | One per section | Shows the idea in action, not just in theory |
| Check for understanding | One per section | Makes the learner retrieve the idea, which is how it sticks |
| Recap | Summary + next steps | Consolidates the key points and tells them what to do next |
The single most important structural tool here is the Section Header layout from
Lesson 2.2. Each time you start a new chunk, a full-screen section-header slide ("Section 2: Formatting
Cells") gives the learner a mental breath and a clear signal that one idea has finished and another has
begun. In a long deck those markers are the difference between a journey and a blur. PowerPoint's
Sections feature (right-click a slide thumbnail > Add Section) also lets
you group slides in the thumbnail pane, so a twenty-slide training deck stays organized while you build
and reuse it.
Notice that the objectives at the front and the recap at the back are mirror images: the objectives promise what the learner will be able to do, and the recap confirms they now can. Writing the recap first, right after the objectives, is a great trick β if you can't recap it, you haven't decided what you're really teaching. Here's the whole flow as one picture:
what you'll be able to do"] --> B["π Section 1
concept"] B --> B2["π οΈ Worked example"] B2 --> B3["β Check for understanding"] B3 --> C["π Section 2
concept"] C --> C2["π οΈ Worked example"] C2 --> C3["β Check for understanding"] C3 --> D["π Recap & next steps"] D -. "loops back to" .-> A
π¬ The rule of chunks: if a section has more than one big idea in it, split it. Learners consolidate one concept at a time, and a section header between two ideas costs you one slide but buys the learner a clean mental filing cabinet. When in doubt, more sections with less in each.
Worked Examples & Checks for Understanding
Telling someone a fact and showing them the fact in action are worlds apart. The two techniques that turn a deck from "information shown" into "skill learned" are the worked example and the check for understanding. Every teaching section wants both.
The worked example
A worked example takes the concept you just explained and demonstrates it on a concrete, specific case β start to finish, with the steps visible. If you're teaching how to write a strong email subject line, don't just list the rules; show a weak subject line, then rebuild it into a strong one, narrating each choice. The learner's brain latches onto the concrete instance far more readily than the abstract rule, and the example becomes the mental template they reuse. Screenshots, a step-by-step build, or a before/after pair all work well. This is where PowerPoint's images and shapes (Module 3) earn their keep: a labeled screenshot or a simple before/after layout teaches faster than a paragraph.
The check for understanding
Memory research is unambiguous on this: people remember what they had to retrieve, not what they merely re-read. A check for understanding is a slide that makes the learner actively recall or apply what you just taught β a quick question, a "spot the mistake," a "what would you do here," a short prediction before you reveal the answer. It doesn't need to be graded or fancy; even pausing on a question slide for the room (or the video viewer) to think before you advance to the answer does the job. The retrieval is the learning. Place one at the end of each section, right before the next section header, so each chunk closes with the learner proving to themselves they've got it.
π‘ The reveal pairing
A check for understanding pairs naturally with a two-slide (or animated) reveal: the question slide, then the answer. Show the question, let it breathe, then show the answer β never both at once, or you've skipped the retrieval. This is one of the few places where a tasteful animation reveal genuinely aids learning rather than just decorating, which brings us to pacing.
β Pro Tip
Write your checks for understanding first, before the teaching slides. If you know exactly what you'll ask the learner to do at the end of a section, you know precisely what that section has to teach β and you'll ruthlessly cut anything that doesn't serve the check. Backward design like this is the single biggest upgrade most training decks need.
Notes as a Facilitator Script; Reveals for Pacing
Two delivery tools do most of the work in a training deck, and both are ideas you've met before β used here with a teacher's intent.
Speaker notes as a facilitator script
In a pitch, speaker notes hold the few sentences you'll say. In a training deck they become a full facilitator script β not word-for-word, but a genuine guide: the explanation for this slide, the question to ask the room, the common misconception to head off, the timing ("spend 3 minutes here"), and a note for whoever reuses this deck after you. That last part matters because training decks get handed around: a colleague inheriting your onboarding deck can run it well only if your notes tell them how. Rich, generous speaker notes are what make a training deck teachable by someone other than its author β a core part of "designed for reuse." They also become the narration script if you export the deck to video.
Reveals for pacing, used sparingly
Animation in a teaching deck has exactly one honest job: to control the pace of information
so the learner isn't reading ahead while you're still on point one. Revealing a bulleted list one item at
a time (Animations > Appear or Fade, sequenced) keeps attention where you
want it; revealing an answer after a check keeps the retrieval intact. That's it. Every other animation β
spinning titles, bouncing images, letters flying in β actively harms learning by stealing attention from
the idea. The test is always "does this reveal help the learner take in the material at the right
moment?" If not, cut it. Sparing, purposeful reveals; never a show. (The full Animation Pane and motion
paths are a desktop / Microsoft 365 strength, but simple sequenced reveals work on the free web app too.)
β οΈ Important Note: A training deck lives or dies on restraint. It's tempting to make a teaching deck "fun" with lots of motion, but a tired learner reads a busy, animated slide as noise. The clearest teaching decks look almost plain β consistent layouts, calm reveals, one idea per slide β and let the content and your voice carry the energy. Plain and clear beats lively and confusing every time.
Built for Reuse, Async & Accessibility
Three qualities separate a professional training deck from a one-off: it can be reused as a template, it works on its own when watched asynchronously, and it's accessible to everyone. Each is a design decision you make while building, not an afterthought.
Reuse: build it like a template
If you'll give this training more than once β or hand it to a colleague β build it so it's easy to
update. That means the look lives in the Slide Master (change the accent color once and
the whole deck follows), the structure lives in real layouts and placeholders (so
swapping in next quarter's numbers doesn't break the design), and the deck is organized with
Sections so someone can find and revise "Module 3" without scrolling through everything.
A training deck built this way can be saved as a .potx template (a desktop-app
save; on the web, keep a tidy "master" copy in OneDrive and duplicate it, as Lesson 8.1 shows) and reused
as the starting point for the next one. This is "design once, apply everywhere" applied to a whole
curriculum.
Async: it should teach without you
Much training is now watched on demand, so your deck should stand on its own. Because the detail a
pitch would hide is often exactly what an async learner needs, teaching decks can carry a bit more text β
and your rich speaker notes become the narration. PowerPoint can export to video
(File > Export > Create a Video; on a Mac, File > Export > MP4) or record a slideshow with narration and
timings (Slide Show > Record), turning your deck into a self-contained lesson
anyone can watch β the async callback to Lesson 5.3. Recording and full export-to-video are strongest in
the desktop / Microsoft 365 app; the web app's options are lighter, so this is a place to note the
platform difference.
Accessibility: teach everyone
A lesson that some learners can't perceive isn't finished. Two habits cover most of it, and they're a
preview of Lesson 8.2. First, alt text: every meaningful image, chart, and SmartArt
graphic needs a short text description (right-click > View Alt Text β labeled Edit Alt Text in some versions β or the
Review > Check Accessibility tool) so screen-reader users and anyone viewing without images
still gets the point. Second, contrast and type size: dark text on a light background (or
the reverse), large enough to read, with color never the only way you signal meaning β because
some learners can't distinguish red from green. The built-in Review > Check Accessibility
flags problems for you. Building accessibly from the start is far easier than retrofitting, and it makes
the deck clearer for everyone, not only those who need it.
β οΈ Reuse cuts both ways
A deck you'll reuse is a deck you'll forget the details of. If your speaker notes say "the figures on slide 8 are from Q1 β update every quarter," future-you (or a colleague) will actually keep it accurate. Undocumented reused decks quietly go stale, presenting last year's numbers as if they were current. Write the maintenance notes now, while you still remember what needs updating.
π― Project: Build Your Training Deck
Now teach something. Pick a topic you genuinely know β a skill, a tool, a process, a hobby, part of your job β and build a short training deck that could actually teach it to someone else. Keep it small and complete: objectives, two or three teaching sections each with a worked example and a check, and a recap. This is the genre that most often becomes a real, reused asset, so build it like one.
ποΈ Build a multi-section training deck
Objective: Teach a topic you know in a reusable, accessible deck β objectives, chunked sections with examples and checks, a recap, and a facilitator script in the notes.
Topic ideas if you're stuck: "How to write a clear status update," "Getting started with [a tool you use]," "The basics of [your hobby]," "Our team's process for [a task]." Pick something you could explain to a friend without notes β then teach it with a deck.
Instructions (about 45 minutes):
- (4 min) Write a title slide and an objectives slide: three or four "By the end you'll be able toβ¦" statements. This is your promise and your map.
- (3 min) Write your recap slide next β the key points a learner should leave with. If you can't recap it, you haven't decided what you're teaching. (You'll place it at the end.)
- (6 min) Plan 2β3 sections, one concept each. Add a Section Header layout slide before each, and use
Add Sectionin the thumbnail pane to group them. - (10 min) For each section, build teaching slides (one idea per slide, consistent layouts) plus one worked example β a concrete before/after, screenshot walk-through, or step-by-step.
- (6 min) Add one check for understanding per section β a question slide, then an answer slide (or a sequenced reveal). Write the check before finalizing the teaching, so the section serves it.
- (6 min) Write speaker notes as a facilitator script for each slide: what to say, what to ask, timing, and any "update this later" maintenance notes.
- (4 min) Add sparing reveals only where they aid pacing (bullets one at a time; answer after a check). Set the look once via the theme /
View > Slide Master. - (6 min) Make it accessible and reusable: add alt text to images, run
Review > Check Accessibility, verify contrast, and save a copy as a template you could reuse. Optional: tryFile > Export > Create a VideoorSlide Show > Record.
π‘ Hint β a training-deck skeleton
TRAINING DECK β slide-by-slide skeleton
1. TITLE Topic + who it's for
2. WHY IT MATTERS One reason to care
3. OBJECTIVES "By the end you'll be able to: 1... 2... 3..."
--- SECTION 1 (section-header slide) ---
4. Concept 1 One idea, big and clear
5. Worked example Before -> After, or step-by-step
6. Check Question slide -> Answer slide
--- SECTION 2 (section-header slide) ---
7. Concept 2
8. Worked example
9. Check Question -> Answer
10. RECAP The key points to leave with
11. NEXT STEPS What to do / practice now
FOR EACH SLIDE
- Speaker notes = facilitator script (say / ask / timing / update-later)
- Alt text on every meaningful image
- Reveals only to pace information; consistent layouts throughout
Two sections is plenty for a first training deck. Depth beats breadth β teach two things well rather than five things vaguely.
β Project Completion Checklist
- Objectives up front and a matching recap at the end
- 2β3 chunked sections, each with a Section Header slide
- Each section has a worked example and a check for understanding
- Speaker notes read as a facilitator script (say / ask / timing / update-later)
- Reveals used only to pace information; consistent layouts throughout
- Alt text added;
Review > Check Accessibilityrun; contrast verified - Saved in a reusable form (template and/or grouped with Sections)
π― Quick Quiz
Question 1: Why does a check for understanding help learning stick?
Question 2: In a training deck, what is the honest job of animation reveals?
Question 3: Which design choice best supports reusing a training deck later?
Best Practices for Training Decks
β Do's
- State objectives up front and recap at the end. Tell learners where they're going, then confirm they arrived.
- Chunk with Section Header slides. One concept per section; a marker between each gives the learner a breath.
- Show worked examples, then check understanding. Concrete beats abstract; retrieval beats re-reading.
- Write generous facilitator notes. They make the deck teachable by someone else and narratable as a video.
- Add alt text and check contrast as you go. Accessible from the start beats retrofitted later.
β Don'ts
- Don't over-animate. A tired learner reads busy motion as noise; reveals are for pacing only.
- Don't cram two ideas into one section. Split them; memory consolidates one concept at a time.
- Don't hand-decorate slides. A reusable deck's look belongs in the Slide Master, not slide by slide.
- Don't skip the notes. A deck with no facilitator script can't be reused or exported to video well.
π‘ Pro Tips
- Write the checks and the recap first. Backward design tells you exactly what each section must teach.
- Save the finished deck as a
.potxtemplate (desktop; on the web, a tidy "master" copy) so your next training starts half-built. - Record one narrated pass early β hearing yourself teach reveals the slides that are too dense.
π Learning Journal
Keep a learning journal as you work through this course β a separate document, a note, or even a slide at the end of the deck you're building. After each lesson, take a few minutes to write down:
- Key concepts you learned
- Techniques that clicked for you
- Questions or confusion points to revisit
- Ideas you want to try in your own decks
- Your progress and feelings about learning this β including where your confidence grew
βοΈ This lesson's prompt: Think about the topic you chose to teach. Writing the checks for understanding first β what would you actually ask a learner to do β did that change what you thought the lesson was about? Where were you tempted to add motion or detail that would have helped you perform rather than helped them learn? Noticing that pull is the beginning of teaching well.
π Lesson Summary
π Key Takeaways
- A training deck teaches, so it's built differently from a pitch: objectives up front, chunked sections, worked examples, checks for understanding, and a recap β the way memory actually works.
- Section Header layouts and Sections keep a long deck navigable; one concept per chunk, with a marker between each.
- Worked examples make ideas concrete and checks for understanding force retrieval β the two techniques that turn "shown" into "learned."
- Speaker notes become a facilitator script, and animation reveals are used sparingly, only to pace information.
- Design it for reuse (Slide Master, layouts, Sections, a template), for async (export to video / record narration), and for accessibility (alt text, contrast β a preview of 8.2).
π What You've Accomplished
You built a genuine teaching asset β a structured, reusable, accessible training deck that could stand on its own as a live workshop or an exported video. You practiced the discipline that makes learning stick (examples and retrieval), wrote notes that let someone else run your deck, and made your first accessibility decisions. Where the pitch deck taught you to persuade, this taught you to transfer knowledge β one of the most valuable and durable skills there is.
β Common Questions at This Stage
How much text is okay on a training slide β isn't that against "the slide isn't your script"?
Training decks can carry a bit more text than a pitch, because the learner may refer back to the slide and because async viewers don't have you narrating live. But the principle still holds: put the key point and the worked example on the slide, and your full explanation in the notes. The test is whether a slide is a clear reference the learner could return to β not a paragraph you'd read aloud word for word. When in doubt, split one dense slide into two clearer ones.
Can I really turn my deck into a video on the free web app?
Partly. The full Create a Video export and Record with narration and timings are strongest in the desktop / Microsoft 365 app; the web app's recording and export options are lighter and change over time. But everything that makes a deck ready to become a video β objectives, chunked sections, rich facilitator notes as a narration script, sparing reveals β you can do entirely for free. Build it well now, and record it wherever you have the fuller tools.
Why write the recap and checks before the teaching slides?
Because it's backward design, and it's the biggest upgrade most training decks need. If you decide up front exactly what the learner should be able to do (the check) and remember (the recap), every teaching slide has a clear job, and you'll cut anything that doesn't serve it. Building forward from "everything I know about the topic" is how decks become bloated and unfocused. Start from the finish line.
π Looking Ahead
In the next lesson β Lesson 7.3: Project β A Visual Portfolio & an Infographic One-Pager β we go image-forward. You'll build two things: a visual portfolio where consistent framing and minimal captions let the work speak, and a single-slide infographic one-pager packed with shapes, icons, and aligned sections at a custom poster size, exported to PNG or PDF. The alignment and object tools from Lesson 3.3 finally get to shine, and you'll see how far you can push PowerPoint as a design tool, not just a slide tool.
β Before the Next Lesson
- Finish your training deck, add alt text, and run the Accessibility Checker
- Save a reusable copy (a template and/or grouped with Sections) to OneDrive
- Write your Learning Journal entry for this lesson
π Additional Resources
- PowerPoint Help & Learning (Microsoft Support)
- Turn your presentation into a video (Microsoft Support)
- Make your PowerPoint presentations accessible (Microsoft Support)
π Encouragement for the Journey
Teaching well is generosity made into a skill β you've just built something that can help another person get better at something, again and again, even when you're not in the room. That's a rare and valuable thing to be able to make. Next, we let images do the talking and turn PowerPoint into a design studio. π½οΈ