How to Turn Technical Notes into a Short Presentation

Start with the audience’s question, then sort your notes by what they need to answer it. Build the spoken explanation from those essentials. Working notes are a record for you; a presentation needs a route that another person can follow.

Keep the source notes intact

Make an outline separately so you do not lose important references while editing. Technical notes may contain dates, assumptions, caveats and unfinished questions. Those details help you verify what can be said. Do not turn a provisional note into a settled claim simply because it fits neatly on a slide.

Write the audience’s decision or task

For a fictional report on a room-booking system, managers may need to decide whether to authorize a trial. Staff may need to learn how to request a room. These require different selections from the same notes. Choose the actual assignment before deciding what to retain. If the request is vague, clarify it with the organizer.

Sort facts by the job they do

Identify the main conclusion, the evidence or explanation needed to support it and the conditions that affect it. Set aside internal history and details useful only to specialists. A condition such as “requires approval from the venue” may be essential. A long list of discarded layout options may not be. Preserve the distinction between simplifying language and changing meaning.

Build a route through one concrete case

For a user demonstration, follow a single fictional booking from request to confirmation. For a recommendation, explain the problem, the available choice and why you recommend it. Put definitions close to the first place people need them. Avoid beginning with a glossary so large that the audience has forgotten the purpose before you reach the example.

Turn the route into speaking notes

Write clear headings and specific reminders. Keep exact figures, names and necessary wording available. Script the opening and ending if that helps. You do not need to read your source document paragraph by paragraph. If a full script works better for this assignment, write it as a spoken explanation and preserve a reliable way to find your place.

Check the result against both sources and time

Rehearse aloud, including any visuals. Then compare the explanation with the original notes: have you lost a condition, overstated a result or changed the sequence? Correct those issues before polishing the design. If the talk runs long, narrow the audience task or move optional detail to a reference. Accuracy and a usable route should survive the cut.

More help for your next talk

If you want a practical guide to preparing, delivering and recovering during a talk, Speaking for People Who Don't Speak brings those skills together. Get the paperback on Amazon.

Next: How to Explain Technical Information to a Nontechnical Audience · How to Decide What Belongs in a Short Talk.

Browse practical speaking help · Ask Michael about a workshop for your team