OE1-1.5 Meetings & Technical Presentations

Standard technical communication practice — written September 2026

What this is and why it exists

Meetings and presentations are where most engineers communicate badly, and both fail for the same reason. The preparation that would have fixed it happens before anything visible is produced.

An agenda before a meeting and three answered questions before a slide are the two highest-return habits in this whole course.

The vocabulary

  • Agenda — the list of items a meeting will cover, circulated beforehand.
  • Chair — the person running the meeting.
  • Minutes — the record of what was decided and by whom.
  • Action item — a decision with a named owner and a date.
  • Memorandum — a short internal document with a fixed, scannable format.
  • Purpose, audience and locale — the three things to settle before preparing a talk.
  • Outline — the structure of a talk, made before any slide.
  • Visual aid — anything shown that carries what speech carries badly.

The mental model

The agenda decides whether a meeting is useful, and circulating it in advance is the highest-return habit in this topic. It tells people what will be discussed, so they arrive prepared. It tells them what will not be discussed, so the meeting stays finite. And writing one forces you to ask what the meeting is for, which occasionally reveals that it is not for anything.

Chairing is rarely taught and engineering graduates are handed it early. The job is to keep the meeting on the agenda and to make sure the quiet people are heard. Each item ends with a decision, or an explicit note that it is unresolved. A meeting that discusses six things and decides none of them has consumed everyone's morning for nothing.

Minutes are a record of decisions and owners, not a transcript. That single reframing makes them both shorter and far more useful. Nobody needs to know who said what during the discussion. Everyone needs to know what was decided, who is doing it and by when. Write those and the discussion can be a sentence.

The memorandum is the short internal document, and its conventions exist to make it scannable. Who it is to, who from, the date, and a subject line that says the subject. It is the ancestor of the email you will write ten times a day, and the same conventions still apply. A subject line saying update tells the reader nothing and costs them a click to find out.

Three event types are worth distinguishing, because they change how you prepare. A seminar is one person presenting to an audience. A workshop expects the participants to do something. A conference is many sessions with an audience that moves between them. Preparing for one as if it were another is a common mistake.

Now presentations, and three questions come before anything else is made.

What is the purpose? Not the topic, the purpose. What should the audience know, believe or do afterwards that they did not before?

Who is the audience? What do they already know, and what do they care about? The same work is presented differently to your team, to a customer and to a review panel.

What is the locale? A small room with a whiteboard, a large hall, or a video call. Each changes what will be legible, what interaction is possible, and how long attention lasts.

Skipping those three is why so many presentations are aimed at nobody in particular. They cost ten minutes and they determine everything after.

Then the outline, before any slide is made. Decide the sequence of points and the argument connecting them. The test is whether it survives being read aloud: if you cannot talk through the outline coherently, slides will not save it.

Visual aids should carry what speech carries badly. A diagram, a trend, a photograph, a table of numbers to compare. Speech handles narrative and argument well, and it handles a spatial relationship or a set of numbers poorly. Put those on the screen and say the rest.

The standard failure is the slide crammed with sentences the speaker then reads aloud. The audience reads faster than you speak, so they finish, get bored, and stop listening to you while you are still on line two. The slide is competing with the speaker, and the slide wins.

Delivery is the half that cannot be prepared on paper. Voice and posture carry more of the message than most engineers expect. Varying pace and volume marks what matters. Pausing after an important point lets it land, and it feels far longer to you than to the audience. Facing the audience rather than the screen keeps the connection that makes people listen.

What you should now be able to explain or do

Prepare and circulate an agenda, and say what writing one reveals. Chair a meeting to a decision on each item. Write minutes as decisions, owners and dates. Answer the three questions before preparing a talk. Build an outline that survives being read aloud, and say what a visual aid should carry and why a text-heavy slide fails.

Check yourself

What the meeting is for. Occasionally it reveals that the meeting is not for anything, which saves everyone the hour.

Decisions, owners and dates. The discussion that led to them can usually be one sentence.

What the audience should know, believe or do afterwards; who they are and what they already know; and where the talk happens.

The audience reads faster than you speak. They finish, stop listening, and the slide competes with the speaker rather than supporting them.

What speech carries badly. A diagram, a trend, a photograph or numbers to compare. Narrative and argument are better spoken.

Go deeper

We haven't checked most of these for screen reader use yet.

Back to Meetings & Technical Presentations: work through the checklist