Oral reports are often a form of advertising--either internally, within a company, where people from different departments see projects displayed by their creators, or externally, where a company presents something to people from outside the company in an attempt to sell it. Oral presentations are often an opportunity for people who read your reports--senior engineers, managers, sales staff--to see who you are and how you work. This means they're as interested in you, and how you handle yourself, as in the material you present. Therefore, present a problem and a solution with just enough technical detail to make your point. What you want to do is let these people know how competent you are, and what sorts of work you do. You will be showing them your thinking style, your working patterns, and your problem-solving ability. With this in mind, try to put on the most professional, persuasive, confident display of your project that you can.
Your oral report is a presentation of the material covered in your final written report. You will have seven minutes to present your report. You may use less time, but you may not exceed the limit. In industry, oral reports are often given before consultants, who charge extravagantly for their time; therefore, you must learn to budget the time allotted you and not exceed it. You will know in advance precisely when, day and time, to the minute, you will be expected to give your report. Be ready to go as soon as you stand up--don't waste time with preparatory goofing around.
Rehearse your talk ahead of time. Practice turning transparencies, writing on the blackboard, or using whatever visual aids you choose.
Read Chapter 19 (Oral Presentations) of Huckin and Olsen. They give some good basic advice on planning and presenting an oral report.
Oral reports are not the best nor the easiest way to present technical information, because the information is difficult to assimilate, often full of statistics, numbers, equations, and so forth, which are hard to follow when given verbally. Therefore, using transparencies, charts, tables, graphs, diagrams, and illustrations can help a great deal. Don't hesitate to use them.
Overhead projector transparencies are commonest in computer science and computer engineering for giving presentations to audiences with fewer than 100 people. There will be an overhead projector available in the classroom for your use.
Here are some tips on using visual aids and notes:
Practice presenting your report at least once before presenting it in class. Time your talk so you know exactly how much material you can fit in, and how to pace the material. Don't just read your notes to yourself--stand up and give the talk the way you will to the class. You will find it very difficult to speak clearly at your normal silent reading speed.
You will probably find, if you are like most people, that you have too much material. If possible, practice presenting your report in the room where you are going to present it formally. Learn to fill the room with your voice, as described in lecture. Concentrating on the sound of your voice will also help you not to be nervous when you are presenting the report. Nervousness may make you speak faster or slower than in your rehearsal. Be prepared with a little extra material, in case you speak too fast.
If English is not your native language, and you find speaking without a prepared text difficult, or if you are overwhelmingly nervous about speaking publicly, it is all right to write your presentation out verbatim and memorize it. However, you must treat memorizing a report in the same way you would treat memorizing a play script. This means that you must memorize it with normal pauses, emphasis, and intonation, and take special care not to speak faster than the normal speech rate. If humanly possible, don't do your report by memorizing a speech--it is not the best way. Huckin and Olsen have some advice and exercises for helping non-native speakers with pronunciation and intonation [HO91, Chapter 38]. Confidence in your understanding of your material, and taking your time will make up for a lot of awkward English and hyper-nervousness. So will substantial practice presenting your report.
Get enough sleep the night before. I have seen someone present a paper at a professional conference after running on adrenalin for a few days, then pass out and fall off the platform when he was asked a question.
Above all, remember that in an oral presentation, you must make each major point in several ways. The old saying about this is, ``First you tell 'em what you're going to tell 'em, then you tell 'em, and then you tell 'em what you told 'em.'' Of course, using exactly the same words each time does not help comprehension--what you are trying to do is to find the explanation that works for each member of the audience, and different people in the audience will understand different explanations.
You will be evaluated on the basis of what may be generally called ``professional behavior''. This means being prepared, being dressed appropriately for your audience, speaking clearly and loudly enough, making eye contact with your audience and maintaining it, handling questions with grace, using equipment and displays skillfully, and generally making your audience comfortable.
Note that being dressed appropriately for a presentation to fellow students or engineers is quite different from being dressed appropriately for a presentation to venture capitalists or the Board of Directors for a large company. You may choose what style of presentation you wish to give in class, but let us know, so that we may judge it by the appropriate standards.
Content means having a well-organized presentation, presenting enough information to make your point but not overwhelming your audience with irrelevant detail, and being accurate about what you say. Many speakers, in their rush to get as much information as possible into their talk, lose their audiences almost immediately, and end up conveying no useful information. Pace your material to the rate at which your audience can understand it.
Some people have been taught that it helps to ``soften up'' your audience with a joke. Humor is valuable when it is relevant, that is, if the point you are trying to make can be illustrated with a short joke, go ahead and use it. Be careful not to waste any time on irrelevant jokes--you're not auditioning for a job as a stand-up comic, you are trying to convey as much information as possible in a short time.
The oral presentations will be given during the last two weeks of class. You will sign up in advance for your day and time.
We will have ten speakers a day, seven minutes each. This means that two-person projects will have fourteen minutes, and we expect the time to be divided roughly equally between speakers. We may need to use the final examination period.
Because class periods are only 70 minutes long, the first person will have to start on time, and we'll have to keep a strict schedule. There will be no room for running overtime, and no time for setting up between talks.
Please come every day, even when you are not speaking--on those days you are the audience! Don't let your classmates down. We will be especially attentive about attendance during oral presentations.
The best thing is to do your presentation as early as possible, rather than as late as possible, because you will have the benefit of having done the presentation when you make final revisions in you final project. Also, being human, we tend to judge the presentations against the ones we have heard previously, so we are going to expect more of the later presentations.
The following article is a column by Jim Blinn from IEEE Computer Graphics and Applications containing suggestions about presenting technical material to a large audience [Bli88], reprinted with the permission of the publisher.
No, I'm not going to talk about flying logos or glass balls. I am going to talk about that special form of performance art known as Giving a Technical Presentation. These ideas apply to speakers in panels and tutorials as well. I realize that the direct audience for this subject is somewhat small, but others of you might be able to use this information in your own talks elsewhere. Also, you should expect this from presentations you hear at SIGGRAPH. SIGGRAPH sends out a lot of stuff about how to prepare visuals, etc. There is no good excuse for not reading it, although from what I see, not many do. The following ideas are just my own personal biases. I will phrase many of them as things not to say or do, because let's face it, it's a lot easier to complain.
A technical talk is just one facet of a multimedia event built on your work. An adventure story appears different in the film version and the book version. Likewise, different things are more appropriate for the spoken version of your paper than for the printed version. A much more conversational style is best for the talk. Tell a story about what got you interested in the problem in the first place. Briefly relate some routes that you tried that turned out to be dead ends. But please don't read your paper verbatim. We are people out here in the audience; we're all your friends; just talk to us. The only exception to this rule is if you are not a native English speaker. If you are not fluent in English, it is probably best to have your words already prepared.
The most important part of your talk is the visuals; this is SIGGRAPH after all. I am sometimes amazed at how many illegible slides are shown, most especially by representatives of organizations (who shall remain nameless) that sermonize about high-quality imaging. Here are some things that have disturbed me most about slides I have seen.
Many of you are involved in the microcircuit revolution and tend to think this also applies to the text on your slides. It doesn't . My personal rule is to put no more than six lines of text on any one slide. And while you're at it, use the biggest font you can that will fit on the slide. Six lines of teeny-weeny text with gigantic borders is still not readable. But, you may ask, what if I have more than six lines? Well, just use more than one slide. See? Simple. A good check for readability of slides is to hold them at arm's length and see if they are still readable. (That is what I do, and my arms are probably longer than yours.) Believe me, that is how small they look from the back of the room. In fact, I make all my slides on my animation system, which has only video resolution. This may seem to be a disadvantage, but it's not. It forces me to keep the slides simple enough to be legible from a long distance. One effect of this restriction concerns equations. You simply can't have a complex equation on a slide. Even if you shrink its many terms down so they will fit, it will look like grey noise from the back of the room. Recast your equations into simpler chunks and give each chunk its own name. Make one master slide with the basic equation in terms of these names. Then make a separate slide to define each chunk. Don't put more than one equation on a slide unless it is fantastically necessary. Use separate slides for each equation to focus attention while you are talking and give you more room for each one.
Another design issue concerns colors and contrast. Your best bet is to use some dark background (like a dark blue) with very light color text (like white or yellow) on it. In any event the main idea is to keep high contrast between the text and the background. Even then, I have seen some terrible slides that use black letters on a white background. Even though the letters were big, the slides were illegible because the lines were too thin. Light areas seem to expand visually, so dark lines tend to get eaten up by a white background. If you must use light backgrounds, use a much thicker line width for the dark lines to compensate for this phenomenon. If you want to emphasize some items on the slide, make them in a lighter color than the rest (not just in a different color).
The audience is not going to want to read a lot of text while simultaneously trying to pay attention to what you are saying. Text on slides should consist of just section headings. If you have a section of your talk that you don't have any obvious graphics for, don't feel compelled to put the text you are reading on a slide just to have something there. The days of silent movies are over. If you must have something, try showing a picture of a pretty waterfall. And remember, folks, no overhead transparencies allowed. There is a reason for this: They look terrible no matter what you do.
No, I'm not saying this because I'm tall. I mean that speakers should look straight out at the audience instead of burying their noses in their notes. I know it looks like a black hole out there, what with the dim house lights and the spotlight on you. You can't really see the audience, but there are people there. If you look down all the time, all that people will see is the top of your head. This is so important that I'll say it again. Look up at the audience; it looks a lot better for the TV cameras. Furthermore, don't turn around to admire your face on the big TV screen. It just won't work. All people will see is the back of your head. Likewise, don't turn around and look at your slides all the time (except maybe for a brief glance to make sure you are on the one you expect). People really are traditionally more used to seeing the front of people's heads than any other side.
You are hereby warned: You have only about 15 minutes to do your brain dump (for a talk in the technical session). The time you have is well known to you in advance. You must use it wisely. About all you can expect to do in this amount of time is give an overview of your paper and inspire those in the audience to read the paper itself for details. Plan to spend most of your time talking about your new ideas. I have seen talks where the speaker spends 13 minutes giving a review of the field and a justification for why the specific problem is interesting. Then--what do you know--there's no time left for the meat of the talk. I think you can safely assume that most everyone in the audience thinks computer graphics is a good idea and that, in fact, the specific problem you are addressing is worth solving. You can probably do fine with about two minutes introduction before getting to the good stuff. Don't go into enormous detail in derivations of the math; just give the basic assumptions and the results. This simplification process goes hand in hand with the simplification of your equation slides. The gist of the math should be describable without going into a lot of fine details that people will best get out of the paper. If you have a videotape, time it and make sure it doesn't eat up the whole time for the talk. Speaking from experience, I know it is very embarrassing for a session chairman (whose main duty is time police) to have to interrupt a nifty tape because there's no time left.