Assignment Type

How to Give an Academic Presentation in STEM

How to structure a technical talk, design slides that make data readable, explain equations clearly and handle questions with confidence.

Updated October 2026 · 5 min read

An academic presentation in STEM explains your work clearly in limited time, often to an audience with mixed backgrounds. The goal is one clear message, supported by a few well-chosen results.

This page sets out a structure that works for project talks, lab presentations and seminar slots, then covers slide design, equations, timing, demos and questions, with a sample slide plan and a checklist.

The Six Parts of a Clear Technical Talk

Open with the problem, state your objective, explain the key idea of your approach, show two or three main results, say what they mean and their limits, then close by restating your message.

Plan roughly one minute per slide, and less content than you think you need. Most talks overrun because they try to show everything.

Structure of a Technical Presentation

PartWhat it coversShare of the time
ProblemWhy this matters, in terms the audience cares aboutAbout 10%
ObjectiveWhat you set out to find, build or testAbout 5%
ApproachThe key idea of your method, not every stepAbout 20%
ResultsTwo or three main findings, shown clearlyAbout 35%
Meaning and limitsWhat the results show and what they do notAbout 20%
ConclusionThe message again, and next stepsAbout 10%

These shares are a starting point. A design project may need more time on the approach; a research talk may need more on results.

How to Prepare, Step by Step

  1. Write your message in one sentence. For example: "The new controller halves settling time without increasing overshoot." Every slide should support it.
  2. Pick your strongest results. Two or three clear findings beat ten rushed ones. Move the rest to backup slides.
  3. Draft slide titles first. Write each title as a sentence stating that slide's point. Read the titles in order; they should tell the whole story.
  4. Build the figures. Redraw graphs for the screen with large labels rather than pasting report figures.
  5. Write speaker notes. Note what to say for each slide, especially how to read each graph.
  6. Rehearse aloud with a timer. At least twice, and cut until you finish a minute early.
  7. Prepare for questions. List the five most likely questions and make backup slides for the hardest ones.

Designing Slides for Data

Slides in STEM talks live or die on their figures. A graph that works in a printed report is often unreadable on a projector.

  • One message per slide, stated in the title as a sentence, such as "Gain rises by 6 dB with the new antenna".
  • Axis labels with quantities and units, in a font large enough to read from the back of the room.
  • Highlight the part of the graph that matters with color or an annotation.
  • Use color-blind-friendly palettes and avoid relying on red against green.
  • Keep text minimal. Say the explanation; do not write it on the slide.

When you show a graph, guide the audience through it: "The horizontal axis is time in seconds, the vertical axis is temperature in kelvin, and the key point is this plateau."

Explaining Equations and Code

Show only the equations your argument depends on, and explain each term in words. An equation the audience cannot read in five seconds should go in a backup slide.

The same applies to code. Show a short, highlighted extract of the key idea, not a full listing, and describe what it does before revealing it. Put detailed derivations and full code in your report or an appendix.

Example Slide Plan for a 10-Minute Project Talk

Project: a low-cost air quality sensor for classrooms.

  1. Title slide: project name, your name, module.
  2. "Classroom CO₂ often exceeds recommended levels": the problem, with one clear chart.
  3. "Aim: a sensor costing under a set budget that alerts teachers": the objective.
  4. "An NDIR sensor and a microcontroller with a traffic-light display": the design in one diagram.
  5. "Calibration against a reference meter": the method, one photo and one sentence.
  6. "Readings agree with the reference to within the sensor's stated accuracy": result one, a scatter plot.
  7. "CO₂ climbs within minutes in a closed room": result two, a time series with the alert threshold marked.
  8. "Limits: one room, one season, no humidity correction": honest limitations.
  9. "Next: a wider trial and a humidity-compensated version": conclusion and next steps.
  10. Questions slide, with backup slides ready on cost, calibration and power use.

Read the titles alone and the whole story comes through. That is the test of a well-structured talk.

Timing, Demos and Delivery

Speak to the audience, not the screen. Know your first and last sentences by heart, because nerves peak at the start and timing slips at the end.

A live demo can be the highlight of a project talk, but test it in the room first, keep it short and have a recorded video ready as a backup. If the demo fails, switch to the video calmly and carry on.

If you run short of time, skip a backup-level slide rather than rushing every slide. A clear conclusion matters more than one extra result.

Handling Questions

  • Listen to the whole question, and repeat it if the room is large.
  • Answer briefly and directly, then stop.
  • If you do not know, say so and explain how you would find out.
  • Use backup slides for expected questions on method, limitations and alternatives.

Examiners often ask about limitations to see whether you understand your work's boundaries. A calm, honest answer scores better than a defensive one.

Posters and Audiences

A poster follows the same story as a talk: problem, approach, results, meaning. Use a large title stating the finding, a few clear figures and little text, and prepare a two-minute spoken summary.

Adjust detail to the audience. A lab group wants method detail; an assessment panel wants the aim, the evidence and the conclusion; a general audience wants why it matters.

Presentation Checklist

  • One-sentence message written and supported by every slide.
  • Slide titles are sentences that tell the story in order.
  • Every graph has readable axis labels with units.
  • Equations and code limited to what the argument needs.
  • Limitations stated honestly.
  • Rehearsed aloud at least twice, finishing early.
  • Backup slides ready for likely questions.
  • Demo tested, with a recorded fallback.

How STEM Donkey Helps with Academic Presentations

Send your project report or results, the time limit, any template your department requires and notes on your audience. A writer matched to your subject prepares custom slides with screen-ready figures and speaker notes, plus backup slides for likely questions.

Use them as a reference to rehearse from and adapt in your own voice. The price is shown before you pay, and free revisions within the scope of your original request are available.

Want Slides and Notes You Can Rehearse From?

Send your project report, results and time limit. You get custom slides with clear data figures and speaker notes written for your talk.

Order Your Presentation

Free revisions · Full refund if late · Written from scratch for your order

Frequently Asked Questions

How many slides should a 10-minute technical presentation have?

Usually 8 to 12, depending on how much data each slide carries. Data-heavy slides can take two minutes each.

Should I put equations on slides?

Only the essential ones, explained term by term. Put full derivations in backup slides or your report.

How do I present complex results simply?

State the message in the slide title, show one clear figure, highlight what matters and walk the audience through the axes.

What if my demo fails?

Switch to a recorded video of it working and carry on. Always test the setup beforehand and keep the demo short.

How do I stop running over time?

Rehearse with a timer, cut until you finish a minute early, and mark slides you can skip if needed.

Can you prepare speaker notes as well as slides?

Yes. Notes are written for each slide, including how to explain each figure, so you can rehearse and adapt them.