When you’d need it

You need to teach how something works — a product, an architecture, a process — to a room that doesn't have your context. A feature list won't land; you need a concept, then a model, then proof.

Key decisions

• It leads with the concept before the mechanics, so the audience has a mental model to hang details on.
• Worked examples follow the model, because people believe a system once they see it do something.
• Text and visual frames alternate, keeping an explanatory deck from turning into a wall of words.
• Five frames — an explainer earns understanding, and understanding comes from focus, not volume.

When to copy vs. adapt

Copy for onboarding, internal training, or a technical overview. For a deeper technical audience, ask Toft to add architecture diagrams and data flows; for execs, cut to concept, one example, and implications.