Skip to content

Professional Development

Rehearse a short technical briefing for people outside your field

A useful rehearsal tests what listeners understand, not just whether you finish on time. Build a short technical briefing around a decision, an explanation and its limits.

A woman explains a small bridge and wind turbine model to a colleague.

You have a few minutes to explain a technical finding to colleagues who do not work in your field. You know the methods and qualifications, but the audience needs to understand what the finding means for its work. Rehearsal can expose that gap before the meeting.

Test three things separately: whether the explanation fits the available time, whether a listener understands the intended meaning and whether the simplified account remains technically accurate. Fluent delivery is useful, but it cannot substitute for the other two.

Start with the audience’s next decision

Write down who will be listening, what they already know and what they need to decide or do. A project sponsor considering a trial has different needs from a specialist checking the method. Ask the meeting organizer about the actual decision if the invitation is vague.

For example, an analyst explaining a new duplicate-record check might want approval to test it on a limited set of records. The immediate task is to explain what it flags, how people will verify the flags and what would justify continuing. A history of every algorithm considered can wait for questions or supporting material.

Brittney Borowiec’s 2023 PLOS science-communication guidance begins with goals and audience, then a clear headline message. It is practitioner guidance rather than a trial of workplace briefings, but it provides a useful starting discipline: decide what the audience should take away before drafting the explanation.

Draft the spoken argument

Build a short sequence around four elements: the issue, the finding, the implication and the limit. Use familiar words for the relationship you need people to understand. Define an essential technical term once, in context, rather than surrounding it with several new terms.

In the duplicate-record example, the central sentence might be: the check identifies entries that may refer to the same request, so a person can review them before any records are changed. This preserves the difference between a flag and a confirmed duplicate.

A 2020 experiment by Shulman and colleagues involved 650 participants and found that jargon disrupted processing of scientific information even when definitions were supplied. It examined written science communication, not a live business briefing. The relevant caution is that a glossary alone may not solve an unnecessarily technical explanation.

Keep one concrete example and the evidence needed to support the proposed next step. If you use a comparison or analogy, identify where it stops being accurate. Do not remove a limitation merely because it complicates the story.

Run a timed rehearsal with a listener

Say the briefing aloud using the actual slides or notes. Time the complete version, including transitions and any explanation of a visual. When it overruns, remove a secondary point instead of speeding through the important qualification.

Next, rehearse with someone who resembles the intended audience. Ask them to respond before showing your intended takeaway:

  • What problem were we trying to address?
  • What does the finding support us doing next?
  • What does it leave uncertain?
  • Which term or step needed more explanation?

Listen for a specific misunderstanding. If your listener thinks the duplicate check deletes records automatically, revise the explanation of human review. If they understand the process but cannot identify the decision, make the request clearer. Treat the response as feedback on the briefing rather than a test of the listener.

Check accuracy after simplifying

Ask a knowledgeable colleague to review the revised version. Have you changed a tentative association into a causal claim, hidden an important condition or made a preliminary result sound established? Check the final spoken words, not only the detailed source document.

Carnegie Mellon’s 2019 account of Baruch Fischhoff’s research on evaluating science communication emphasizes collaboration between subject experts and communication practitioners, including the limits of what research supports. For a small briefing, this suggests a practical division: one person checks understandable meaning and another checks fidelity to the evidence.

Finish by rehearsing the likely first question and a truthful response when information is unavailable. State what you know, what needs checking and how the question will be followed up. Keep supporting detail ready without inserting all of it into the opening.

Your final preparation should leave you with a brief argument you can deliver calmly, a clear request and evidence that another person understood both the implication and its boundary. That is a more useful rehearsal result than simply reaching the last slide on time.

More to read

Browse insights