Presenting technical findings to senior managers means helping people use your evidence to make a decision. They may need to approve a trial, choose between options, understand a risk or decide that no action is needed yet.

You still need accuracy. The challenge is choosing an order that makes the meaning clear before you explain the detail. Start by completing this sentence: “At the end of this briefing, I need the audience to decide, understand or do…”

Find out what this meeting needs from you

A progress update, an investment request and a discussion about a safety concern need different presentations. If the brief is vague, ask the organiser what decision is expected, who will be present, how long you have and whether questions are included in your time.

Consider what the listeners already know. Seniority does not tell you someone’s technical background. Explain unfamiliar terms briefly, and offer more detail when it helps the decision.

For a broader approach to audience-friendly explanations, use the guide to explaining complex technical ideas to non-specialists.

Use five parts: recommendation, reason, evidence, limits and request

  1. Recommendation: state your proposed action, or the conclusion the audience needs to understand.
  2. Reason: explain why it matters now. Connect it to the actual problem, such as reliability, workload, cost, quality or customer experience.
  3. Evidence: present the few findings that support the recommendation. Keep the method available for questions.
  4. Limits: explain what the evidence does not establish and what could change your conclusion.
  5. Request: specify the decision, owner and next checkpoint you are proposing.

This is a useful starting structure, not a fixed script. If your role is to present options rather than recommend one, say so. You can still make the trade-offs and the decision needed clear.

A worked example: asking permission for a wider trial

This is an invented teaching example, not a description of a Tailored Guidance client or a real research project.

Imagine that a team has tested a simpler process for handling routine requests. A chronological presentation might begin with the software configuration, every change tested and the order of the measurements. The audience must then work out why any of it matters.

A more useful opening could be:

“I recommend a limited trial of the revised process with a second team. In our initial test, median handling time fell from six minutes to four. That suggests a possible improvement, but we have only tested routine requests with one team. We have not yet measured unusual cases or long-term error rates. I’m asking for approval to test those conditions before we consider a wider rollout.”

The numbers are illustrative. The useful pattern is the connection between the result, its limitation and the proposed next step. A measured reduction in handling time is not automatically a cash saving or evidence that the process will work everywhere.

Choose evidence that answers a management question

For each figure or chart, ask: “What question does this help the audience answer?” A detailed graph belongs in the main presentation when interpreting it matters to the decision. Otherwise, put it in supporting material you can bring up if asked.

  • Show the comparison or baseline so the number has meaning.
  • Keep units, time periods and sample sizes visible where relevant.
  • Distinguish an observed result from a forecast or assumption.
  • Explain a limitation beside the finding it qualifies.
  • Use a slide heading that states the point you can support.

For example, “Initial trial reduced routine handling time” is more informative than “Results”. It is also more careful than claiming the process has solved delays across the organisation.

Prepare for questions without inventing certainty

Think through the questions your recommendation naturally creates: What did you compare? What would this cost? What happens if we wait? Which risks remain? What would make you change your recommendation?

Prepare a short answer and a deeper explanation. If you do not know something, separate what you can answer from what needs checking:

“We measured handling time, but we have not yet assessed the effect on errors. I would include that in the next trial before recommending a full rollout.”

Do not commit another person to a deadline without checking. If you offer to follow up, be clear about the information you will verify and agree a realistic time.

Rehearse the opening and the final request together

Practise your first sentence and your closing request back to back. Do they point to the same decision? Then rehearse the whole presentation out loud, including pauses and time for questions.

If your slot is short, use the five-minute technical presentation structure. For a fuller preparation routine, follow the five-pass rehearsal guide.

Before you present

  • I can describe the purpose of the briefing in one sentence.
  • My recommendation follows from the evidence I show.
  • I have separated results, assumptions and uncertainties.
  • My listeners can understand the significance of the main figures.
  • I finish with a specific request or agreed next step.

For your practice run, use the rehearsal checklist in the free public speaking cheat sheets. Ask a colleague to listen to your first and last sentences, then tell you what decision they think you need.

Would feedback on your next technical briefing help?

Work with Timothée Grillon, Founder of Tailored Guidance and public speaking consultant, on your message, explanation and delivery. Explore communication consultancy for STEM professionals.

Book a free 15-minute consultation about your presentation. Tell me who you will be speaking to, what they need to decide and when the presentation is due.