School: Minister Destiny Testimony Schools Track: Adult Class: Certificate Topics — Year 1 (Foundations) · Home: Headquarters — the ministry content set Certificate behind this topic: "Presenting Technical Information with Stories" — LinkedIn Learning, earned by Minister Destiny Marie Morgan (May 27, 2025) Founded and presented by: Muslim Ordained Minister Destiny Marie Morgan
This lesson is educational information from Minister Destiny Testimony Schools. It teaches the public body of knowledge in this subject — the same ground Minister Destiny studied for her certificate — in this school's own words. It is not the original course, it does not award the original credential, and it is not legal or medical advice. If you are in danger right now, call 911.
Before you start
- This school never asks your name. Your progress is saved only in your own browser on this device — the school collects and keeps nothing. If you pass this unit's quiz (80% or higher, retakes allowed), you earn a downloadable certificate with a blank line — you write your own name on it after you save it. Quiz answers are not shown; if you miss a question, re-read the lesson and try again.
- This is a ministry content set topic, written for anyone who must explain systems, data, or law to people who did not study it — advocates, teachers, technicians, and neighbours alike.
- Minister Destiny earned this certificate in May 2025. This unit teaches the public craft behind it: story in the service of accuracy, never instead of it.
The lesson
Part 1. Why Stories Carry Information
Technical information fails in predictable ways: too many terms, no sense of why it matters, and nothing for memory to hold onto. Facts presented as a list are forgotten as a list. A story solves all three problems at once, because a story is how people naturally track cause and effect: someone wanted something, something stood in the way, something happened, and things changed. When the technical point rides inside that shape, listeners remember the point because they remember what happened.
This is not decoration and it is not dumbing down. A well-chosen story is a working model of the system you are explaining. The listener who remembers how one family's heating failed on the coldest night understands the inspection rule better than the listener who memorised the rule's number. Your job as presenter is translation with integrity: carry the real mechanism, the real numbers that matter, and the real limits — inside a form a non-specialist can hold.
Part 2. The Story Structure That Works — Person, Problem, Turn, Result
One structure carries most technical stories: a person, a problem, a turn, a result. Introduce a person (real, with permission, or a clearly typical composite you label as such) facing a concrete problem your subject addresses. Let the problem develop just enough that the listener feels what is at stake. The turn is the moment the technical idea enters: the test result, the rule applied, the step taken, the discovery made. The result shows what changed — including, honestly, what did not change or what it cost.
Keep the story lean. One person, one problem, one turn. Details earn their place only if they help the listener understand the mechanism or feel the stake. End the story by naming the principle out loud: "That is what a two-factor check does — it turned a stolen password from a disaster into an inconvenience." The audience should never have to guess why you told the story.
Part 3. Choosing the One Example That Teaches the Rule
Presenters often bury a good talk under twelve examples. Choose instead the one example that teaches the rule — the case where the general principle becomes visible. A teaching example has three qualities: it is typical (the rule works the same way in most real cases, not just this dramatic one), it is clear (each step of the mechanism can be pointed to), and it is complete (it shows the result, not just the setup).
If your best example is unusual, say so and give the typical picture too: "The flood case is dramatic; the everyday case is a slow leak, and the same sensor catches both." Keep a second example in reserve for questions, and let the rest go. Cutting examples is not cutting truth — it is choosing the clearest window onto the truth. Distorting an example, however — changing numbers, merging people without saying so, or hiding an inconvenient step — is cutting truth, and it is forbidden in this school. If you simplify, simplify the telling, not the facts.
Part 4. Analogy Without Distortion
Analogy is the presenter's bridge: "Think of encryption as a locked box whose key only the receiver holds." A good analogy maps the important relationships of the technical idea onto something familiar, and a responsible presenter states where the bridge ends: "The box picture helps with privacy, but digital copies behave differently from physical boxes — copying the locked box is easy; opening it is the hard part."
Test every analogy with two questions. Does it preserve the relationships that matter for the decision at hand? And do I tell the audience where it stops working? An analogy that hides a limit can mislead more than jargon does, because it feels understood. When no honest analogy exists, say the technical thing plainly and slowly instead — plain language is itself a skill: short sentences, everyday words for everything except the one or two technical terms you stop and define.
Part 5. Visuals That Explain
A visual earns its place only if it explains something words do badly: a trend over time, a comparison of sizes, the steps of a process, the parts of a system. The rules are simple and strict. One idea per visual. Labels a person in the back row can read. Numbers honest in their scaling — a chart whose axis starts partway up to exaggerate a change is a story that lies. Say what the visual shows before you discuss what it means, and give the room time to look before you talk over it.
Prefer showing the real thing where you can: the actual form, the actual device, the actual before-and-after. Remove any visual that merely repeats your words in bullet form — listeners read faster than you speak, finish your slide, and stop listening. If a visual would expose a real person's private information, recreate a fictional version and label it as an illustration. Explanation never justifies exposure.
Part 6. Layering Detail for Mixed Audiences — and Checking Understanding
Real audiences are mixed: a nurse and a neighbour sit in the same talk about the same clinic system. Layer your talk. Layer one, for everyone: the story, the point, and what to do. Layer two, for those who want mechanism: how it works, in plain steps. Layer three, offered but not imposed: the deep detail, in a handout, an appendix slide, or an offer to stay afterwards. Signal the layers as you go — "For everyone, the takeaway is… For those who manage these systems, the mechanism is…" — so nobody feels talked down to or abandoned.
Finish by checking understanding, because nodding is not evidence. Ask one question the audience can answer from the talk ("So if the letter gives you ten days, when does the clock start?"), invite the muddiest-point question ("What part should I explain differently?"), or run a thirty-second teach-back with a neighbour. What you hear tells you what to fix next time — and occasionally what to fix right now, before the room leaves with a misunderstanding you could have caught.
Words to know — Presenting Technical Information with Stories
- Teaching example — the typical, clear, complete case chosen to make a general rule visible.
- Turn — the moment in a story where the technical idea enters and the problem changes.
- Composite — a typical character built from several real cases; it must be labelled as a composite when used.
- Analogy — a familiar comparison that maps a technical idea's key relationships; its limits must be stated.
- Plain language — short sentences and everyday words, with the few needed technical terms defined.
- Layering — structuring a talk in levels: takeaway for everyone, mechanism for those who want it, depth on offer.
- Honest scaling — charting numbers so visual size matches real size; no truncated axes that exaggerate.
- Teach-back — asking listeners to explain the point in their own words to confirm understanding.
- Muddiest point — the part listeners found least clear, invited by name as a closing question.
Myths vs facts — Presenting Technical Information with Stories
- Myth: Stories are decoration for people who cannot handle real information. Fact: A story is a working model of cause and effect; listeners remember and correctly use information carried by a sound story.
- Myth: More examples always teach more. Fact: One typical, complete teaching example usually beats twelve partial ones; extra examples bury the rule.
- Myth: Simplifying means changing the facts a little. Fact: Simplify the telling, never the facts — no changed numbers, merged people, or hidden steps without saying so.
- Myth: A good analogy works without limits. Fact: Every analogy stops working somewhere; a responsible presenter says where.
- Myth: If the audience nods, they understood. Fact: Nodding is politeness, not evidence; check with a question, a teach-back, or the muddiest-point invitation.
Think it through — Presenting Technical Information with Stories
The situation: Priya must explain new court e-filing deadlines to a community group. Her first draft lists fourteen rules and six exceptions. A colleague suggests opening with "a scary story about someone who lost their case" that Priya heard second-hand and cannot verify. She asks what this unit would do instead.
Walk it through: (1) Reject the unverified scare story (Part 3): accuracy rules forbid it, and fear is not the mechanism she needs to teach. (2) Find the teaching example (Part 3): one typical filing — a neighbour with a response due — where the counting rule becomes visible step by step. Priya labels the neighbour as a composite, honestly. (3) Structure it (Part 2): person, problem (the letter arrives), turn (counting from the right start day, with the weekend rule), result (filed on time, with a day to spare). (4) Layer it (Part 6): takeaway for everyone — how to count; mechanism for those filing themselves; the six exceptions go to a handout and an offer to stay after. (5) Check (Part 6): she ends with one counting question the room answers together. The rule survives the evening because it arrived as a story and left as a skill.
Try this — Presenting Technical Information with Stories
- ☐ Take one technical point you explain often and write its person–problem–turn–result story in under 150 words
- ☐ Audit the story: every number verifiable, every person real-with-permission or labelled composite
- ☐ Write one analogy for the point, then write the sentence that states where the analogy stops working
- ☐ Redesign one visual to carry a single idea with readable labels and honest scaling
- ☐ Plan your layers: one-sentence takeaway for everyone, mechanism steps, and where the deep detail will live
Resources to keep — Presenting Technical Information with Stories
- TED — ted.com — free talks that model story-carried technical content; study how speakers introduce data inside a narrative.
- Exploring Public Speaking — LibreTexts (libretexts.org) — free open textbook with chapters on presentation aids, audience adaptation, and structure.
- Stand Up, Speak Out — Open Textbook Library (open.umn.edu) and LibreTexts (libretexts.org) — free textbook chapters on supporting ideas and presentation aids.
- Purdue OWL — Public Speaking and Presentations (owl.purdue.edu) — free guidance on organising information for listeners.
- Saylor Academy — Public Speaking (saylor.org) — free course units on supporting content and presentation aids.
What you earned / what's next — Presenting Technical Information with Stories
✅ Presenting Technical Information with Stories complete (quiz score 80% or higher): You can carry technical information inside a person–problem–turn–result story, choose one honest teaching example, use analogy with its limits stated, design visuals that explain, layer detail for mixed audiences, and verify understanding before the room leaves.
Your certificate
Minister Destiny Testimony Schools Certificate of Completion — Presenting Technical Information with Stories
This certificate is presented by Muslim Ordained Minister Destiny Marie Morgan
Awarded to: ______________________________ (write your name here after you download — your name is never collected or stored by this school)
Date completed: ______________
You learned to make hard things clear without making them false. That is a rare and needed gift — carry it to every room that needs understanding. — Minister Destiny Marie Morgan
This is a certificate of educational completion from Minister Destiny Testimony Schools. It is not a state license, a government certification, or the original course credential.
What's next: Return to the Certificate Topics for your next Year 1 Foundations topic.
Sources
- Exploring Public Speaking (Barton and Tucker) — LibreTexts (libretexts.org) — presentation aids, audience adaptation, and speech structure.
- Stand Up, Speak Out: The Practice and Ethics of Public Speaking — University of Minnesota Libraries Publishing, via Open Textbook Library (open.umn.edu) and LibreTexts (libretexts.org) — supporting ideas, arguments, and presentation aids.
- TED (ted.com) — talks studied as examples of narrative-carried technical presentation.
- Public Speaking and Presentations: Tips for Success — Purdue OWL, Purdue University (owl.purdue.edu) — organising information and using audiovisual aids wisely.
- Public Speaking — Saylor Academy (saylor.org) — supporting content and presentation-aid units.
Your Progress — On Your Device Only — Presenting Technical Information with Stories
- Learning outcomes: On completing this unit, the student can:
- explain why a story functions as a working model of cause and effect for technical content
- build a person–problem–turn–result story and state its principle out loud
- select one typical, clear, complete teaching example and cut or reserve the rest
- construct an analogy and state where it stops working
- design a single-idea visual with honest scaling and check understanding with a teach-back or muddiest-point question
- layer a talk into takeaway, mechanism, and offered depth for a mixed audience
- Study time: Approximately 1 hour — an estimate covering reading, activities, and the test. Students move at their own pace.
- Assessment: A 10-question test drawn only from this unit's lesson. 80% or higher passes and earns the unit certificate. Answers are not shown; your score is saved only in your own browser on this device, and retakes are allowed.
- Level: Certificate Topics — Year 1 (Foundations) · Adult school · working rank on completion path: Freshman → Sophomore.
- Version: Version 1.0 — October 2026.
Minister Destiny Testimony Schools — Adult. Educational information only. Help lines: 911 for emergencies · 988 Suicide & Crisis Lifeline (call/text 988).