📊 Lesson 7.2: Project — A Lesson / Training Deck

🎓 Teaching Is Not Presenting

When you pitch, you want the audience convinced by the end. When you teach, you want them able to do something by the end — which is a much higher bar. People don't learn by being told; they learn by understanding, seeing an example, trying it, and reviewing it. A training deck that just tells is a lecture people forget by lunch. A training deck built around how learning works actually sticks.

The through-line still holds — Message → Structure → Design — but the structure is different. A teaching deck is paced for absorption, not speed. It's fine, even good, for a lesson slide to pause on one concept while you explain it, ask a question, and let people think. The design should be calm and consistent so the content, not the slides, carries the cognitive load. And crucially, the slide is still a visual aid, not your script — but now the "script" in your notes is a facilitator script: what to say, what to ask, when to pause, and how long each part should take.

🌀 The Training Arc

Effective lessons follow a reliable rhythm. State what they'll learn, explain the idea, show it in action, let them try it, then recap. Each stage prepares the next; skip one and learning leaks out. Here's the arc.

Read across: tell them what they'll be able to do, explain it, show a concrete example, give them a chance to try, then recap and check. The dotted arrow matters — if a check reveals confusion, loop back to explaining before moving on. This arc maps cleanly onto slides, and it's a great backbone whether your topic is a software feature, a company process, a scientific concept, or a life skill.

🎬 Progressive Reveal & Embedded Video

Two tools make a teaching deck genuinely better at teaching. Both come straight from earlier modules — here you're applying them with intent.

Progressive reveal

When you put five bullets on a slide, learners read all five instantly and stop listening to you explain the first. Progressive reveal — using a simple "appear" animation so each bullet or element shows up on click — keeps the room with you. You reveal one idea, discuss it, then reveal the next. This is the animation feature earning its keep: not decoration, but pacing. It's the single most useful animation in a teaching deck. Keep the effect plain (appear or fade), consistent, and on-click so you control the rhythm.

Embed a short video

Some things are far easier to show than to describe — a physical technique, a software workflow, a real example. Embedding a short video (from Google Drive or a linked source) lets you play it right inside present mode without leaving your deck or hunting for a browser tab. Keep it short and purposeful: a 1–2 minute clip that demonstrates one thing, teed up with a note in your script about what to point out. A video is a demo you don't have to perform live — great for reliability.

🗂️ Sections for a Longer Deck

A pitch is ten lean slides; a lesson can easily run 10–14 or more, and a long flat list of slides gets hard to navigate — for you while building, and for learners following along. The fix is sections (Section Header slides as dividers, as in Lesson 2.1 — Slides has no separate Sections panel). Group your slides into a few clear chunks — for example Warm-up · Core idea · Practice · Wrap-up — with a section-header slide announcing each. Section headers give learners a mental map ("we're moving into practice now") and give you clean signposts to jump between while presenting.

This is also where the slide master pays off again: a distinct Section Header layout, styled once in the master, makes every section break look intentional and consistent. Sections turn a daunting long deck into a handful of digestible parts — the same reason this course is split into modules rather than one wall of 24 lessons.

🗣️ Notes as a Facilitator Script

In a pitch, speaker notes hold the sentences you'll say. In a lesson, they become a full facilitator script — a richer tool. For each slide, note not just what to say but what to ask, when to pause, what task to set, and roughly how long the slide should take. That turns your deck into something you (or a colleague) could deliver smoothly even on a tired morning, and it keeps a multi-part lesson on time.

A simple, reliable pattern for each slide's notes:

• Say: the one or two sentences that explain this slide
• Ask: a question to engage the room or check understanding
• Do: any task, demo cue, or "play the video here"
• Time: a rough number of minutes so the whole lesson stays on track

Then present using presenter view, which shows your notes and the next slide on your screen while learners see only the clean slide. That's the payoff of keeping words off the slide all along: the audience gets a calm visual aid, and you get your full script exactly where you need it.

🎯 Project: Build Your Training Deck

Now build a complete teaching deck on a topic you know well enough to teach — a software tip, a recipe technique, a work process, a hobby skill, a concept from your field. Knowing the topic lets you focus entirely on the teaching design. Aim for 10–14 slides organized into a few sections, following the training arc.

My Training Deck (~10-14 slides)

Outcome: "By the end, learners will be able to ___."

Section 1 — Warm-up
  1. Title
  2. Objectives ("you'll be able to...")

Section 2 — Core idea (Explain)
  3-6. One idea per slide, progressive reveal

Section 3 — See it (Demo)
  7. Worked example
  8. Embedded video (1-2 min, play on click)

Section 4 — Practice
  9. A clear task + whitespace

Section 5 — Wrap-up
  10. Recap (mirrors objectives)
  11. Next steps + share link

Notes on every slide:
  Say / Ask / Do / Time

⭐ Best Practices for Training Decks

✅ Do's

• Design backward from the outcome. Start with "learners will be able to ___" and the recap; the middle writes itself.
• Build in practice. A slide where they try the skill beats three more explanation slides.
• Use sections and progressive reveal. They give a longer deck structure and pace it for absorption.

❌ Don'ts

• Don't lecture at the slides. Ask questions, set tasks, and let learners do — teaching isn't telling.
• Don't paste your script onto the slides. Keep it in the notes; share the deck afterward if learners need the words.
• Don't over-animate. One consistent reveal effect is plenty; fancy motion distracts from the content.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built a complete teaching deck designed around how people actually learn — objectives up front, explanation paced with progressive reveal, a demo and embedded video, real practice, a recap, all organized into sections and backed by a facilitator script. That's a genuinely hard thing to do well, and you now have a deck you could stand up and deliver to a class or team, plus a repeatable process for the next one.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 7.3: Project — A Visual Portfolio & an Infographic One-Pager — we go image-led. You'll build a visual portfolio deck with consistent grids, captions, and cropping, and a single infographic-style one-pager that tells a data story with shapes, icons, and big numbers, then export it as an image or PDF for sharing.

✅ Before the Next Lesson

• Finish your training deck and rehearse at least one section in presenter view
• Gather a handful of images or examples of work you're proud of — you'll build a visual portfolio next
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• slides.google.com — build your deck
• Google Slides Help Center (Google Support)
• Google Slides on Google Workspace — overview