How to Give a Good Talk Bonnie Dorr.

Slides:



Advertisements
Similar presentations
Terrible Presentations (…and how to not give one)
Advertisements

COMMON MISTAKES IN PRESENTATION SLIDES DESIGN Made by Matukhin D.L. Associate Prof. EEI TPU TOMSK POLYTECHNIC UNIVERSITY.
Making a Presentation Pertemuan 11 Matakuliah: PSYCHOLOGY PEMERIKSAAN Tahun: 2009.
BAD PRESENTATIONS (and how not to give one..) Adopted from Katherine Compton Dept. of ECE UW-Madison Mark L. Chang Dept. of ECE Olin College of Eng.
Public speaking: the basics
How to Give a Good Talk Bonnie Dorr. The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads.
Electronic Visualization Laboratory University of Illinois at Chicago Giving Good Presentations Electronic Visualization Laboratory University of Illinois.
Giving Talks. Seminars are important They provide a way to communicate about your research – They are a key element to getting jobs – As your career progresses,
EGR 105 Foundations of Engineering I Fall 2007 – week 11 Presentation Tips.
Terrible Presentations (…and how to not give one) Mark L. Chang Dept. of ECE Olin College of Eng. Katherine Compton Dept. of ECE UW-Madison
Terrible Presentations (…and how to not give one) Mark L. Chang Dept. of ECE Olin College of Eng. Katherine Compton Dept. of ECE UW-Madison
Making a Presentation Discussion Points Masters-Doctoral Seminar.
1 PowerPoint Presentation Design Wednesday, September 02, 2015Ms. Wear Info Tech 9/10.
Horrible Presentations - How to Guide for Physicists & Engineers W. J. Wilson Dept. of Engineering & Physics University of Central Oklahoma cyberphysics.org/wwilson.
Some tips to make your presentations presentable Basic Power Point Guidelines.
Academic Communication Lesson 4 Please pick up two handouts from the front desk. You will also need the previous handouts “Typical Organization of …”
Capstone Presentation Guideline March 2014 Middletown High School Middletown Public Schools 2014 Presentation Overview.
Orna Farrell Presentation Skills Orna Farrell
DVCon Presentation Template and Information You may add your company logo to this page, ONLY by.
Guidelines for Paper Presentation Mei-Chen Yeh 03/30/2010.
Effective PowerPoints. This: Do not attempt to put all the text, code, or explanation of what you are talking about directly onto the slide, especially.
Making PowerPoint Slides Adopted from Mary Westervelt, University of Pennsylvania.
How to NOT make a powerpoint. Development Research Shows Parent Involvement in Education Important To Student Success.
TECHNICAL WRITING November 30 th, Today Gestures. Making effective PowerPoints.
How to do it right….  Enhance Understanding  Add Variety  Support Claims  Have a Lasting Impact.
Research talk 101 Jim Miles California State University, Long Beach 9/9/15.
Studio 2 Guidelines for Good Presentations JANUARY GE105 Introduction to Engineering Design College of Engineering King Saud University.
TECHNICAL WRITING November 29, Today Gestures. Making effective PowerPoints.
Terrible Presentations (…and how to not give one) Mark L. Chang Dept. of ECE Olin College of Eng. Katherine Compton Dept. of ECE UW-Madison.
Making a Research Presentation
Presenting Research.
Title of your paper Name of author(s).
PowerPoint Tips For Presentations.
About this Template This is a template for presentations at the 2016 EOS/ESD Symposium It’s optimized for use with PowerPoint 2010 (Office 2010) Do not.
Giving Technical Talks
Guidelines for Preparing the Seminar Presentation
Title of your poster here: if you have a really long title,
Visual Aid Etiquettes: For Effective Presentation
Studio 2. Guidelines for Good Presentations
How to Create a PowerPoint Presentation
About this Template This is a template for presentations at the 2016 EOS/ESD Symposium It’s optimized for use with PowerPoint 2010 (Office 2010) Do not.
GIVING PRESENTATIONS.
10 top tips for designing and presenting great slide shows
Second Grade ABC Book of Wisdom
TAKING CORNELL STYLE NOTES
Happy April Fool’s Day Your job is to plan a good presentation and create a good slideshow. A sample will not help you succeed in that task nearly as.
Session # - Session Name
10 top tips for designing and presenting great slide shows
A Few Things to Think About
IEEE CONECCT 2018 Title of your paper
Title of your poster here: if you have a really long title,
Hints for Giving Presentations (B) Dos and Don’ts of Technical Talks
Studio 2. Guidelines for Good Presentations
About this Template This is a template for presentations at the 2018 EOS/ESD Symposium It’s optimized for use with PowerPoint 2010 (Office 2010) Do not.
Title of your paper Name of author(s).
Studio 2. Guidelines for Good Presentations
About this Template This is a template for presentations at the 2018 EOS/ESD Symposium It’s optimized for use with PowerPoint 2007 (Office 2007) Do not.
Title of Paper or Topic you are Teaching
Public speaking: the basics
Effective Presentation
“Enter your Track Name Here”
Recitation Presentation Format
Capstone Presentation Guideline
Cornell Notes Note-taking strategy that will improve your study skills and your grades!!
Studio 2. Guidelines for a Good Presentation
Research Presentation Tips
Lecture 1: General Communication Skills
Title of Paper or Topic you are Teaching
Title of your paper Name of author(s).
Presentation transcript:

How to Give a Good Talk Bonnie Dorr

The speaker approaches the head of the room and sits down at the table. 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) With five minutes left in the session, the speaker suddenly looks at his/her watch. S/he announces -- in apparent surprise -- that s/he'll have to omit the most important points because time is running out. S/he shuffles papers, becoming flustered and confused. 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) With five minutes left in the session, the speaker suddenly looks at his/her watch. S/he announces -- in apparent surprise -- that s/he'll have to omit the most important points because time is running out. S/he shuffles papers, becoming flustered and confused. (You do too, if you're still awake.) 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) With five minutes left in the session, the speaker suddenly looks at his/her watch. S/he announces -- in apparent surprise -- that s/he'll have to omit the most important points because time is running out. S/he shuffles papers, becoming flustered and confused. (You do too, if you're still awake.) S/he drones on. Fifteen minutes after the scheduled end of the talk, the host reminds the speaker to finish for the third time. The speaker trails off inconclusively and asks for questions. 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) With five minutes left in the session, the speaker suddenly looks at his/her watch. S/he announces -- in apparent surprise -- that s/he'll have to omit the most important points because time is running out. S/he shuffles papers, becoming flustered and confused. (You do too, if you're still awake.) S/he drones on. Fifteen minutes after the scheduled end of the talk, the host reminds the speaker to finish for the third time. The speaker trails off inconclusively and asks for questions. (Thin, polite applause finally rouses you from dreamland.) 21/02/62

The speaker approaches the head of the room and sits down at the table The speaker approaches the head of the room and sits down at the table. (You can't see him/her through the heads in front of you.) S/he begins to read from a paper, speaking in a soft monotone. (You can hardly hear. Soon you're nodding off.) Sentences are long, complex, and filled with jargon. The speaker emphasizes complicated details. (You rapidly lose the thread of the talk.) With five minutes left in the session, the speaker suddenly looks at his/her watch. S/he announces -- in apparent surprise -- that s/he'll have to omit the most important points because time is running out. S/he shuffles papers, becoming flustered and confused. (You do too, if you're still awake.) S/he drones on. Fifteen minutes after the scheduled end of the talk, the host reminds the speaker to finish for the third time. The speaker trails off inconclusively and asks for questions. (Thin, polite applause finally rouses you from dreamland.) [Paul Edwards on “How to give a talk”] 21/02/62

What’s wrong with this picture? Reading Sitting No visual aids Small print, busy slides No moving about Monotone Mumbling Facing downward Lost in details Running overtime No conclusion Ignoring audience Talk Stand Diagrams, graphs Large print Move Vary pitch Speak loudly/clearly Eye contact Focus on main points Finish on time Summarize, conclude 21/02/62 Respond to audience

What will I talk about today? How to give GOOD presentations: Part I: Presence Attitude Voice Mannerisms Part II: Slide style Understandable Interesting Will show examples of what NOT to do 21/02/62

Giving a Good Talk: It’s important! [Tamara G. Kolda, 2002] You want people to: Understand your work Be INTERESTED in your work Think you’re great! What happens if you give a bad one? Few pay attention They may fall asleep Might think your work is not important 21/02/62

Part I Keep audience interested Keep them with you Things that can affect this Topic, topic depth Attitude/Presence Mannerisms 21/02/62

Preparation Know what your surroundings will be like: size of room, microphone, equipment, etc. Know your audience and tune your message to that audience Organize your slides so that they effectively deliver your central message Answer questions skillfully 21/02/62

Where are you presenting? 21/02/62

Know Your Topic Be prepared to get questions! Be able to recover from interruptions Know what to skip if you’re running late Don’t just talk faster! 21/02/62

Who is your audience? 21/02/62

Know your Audience [Tamara G. Kolda, 2002] One of the biggest mistakes speakers make is not knowing their audience! Will your audience include … Specialists in your sub-field? In your field? Researchers in the computer/mathematical sciences Engineers and scientists? Faculty and postdoctoral researchers? Graduate students? Undergraduates? 21/02/62

Know Your Location Need to bring a laptop? Need to bring a CD, or email a PPT in advance? Need to print transparencies? How far is audience from screen? Can you point with your hand, or do you need a laser pointer? 21/02/62

Dead Man Talking Are you hiding behind the podium? Are your hands/face motionless? Are you staring… at your advisor/boss? at your laptop? at the screen? at the ceiling? Is your back to the audience? IF SO… you’re probably BORING! 21/02/62

I Drank A Case Of Mountain Dew! Sometimes nerves make for fast talking Calm down. It’s not a race People need time to absorb information Take a bottle of water if necessary Bottles if you can work a cap (spillage) Glass if you’re using a laser pointer 21/02/62

Where are your hands? You have a set of “moves” that repeat during your talk Make sure they aren’t silly looking Don’t point with your middle finger Do a practice for friends Make sure they’re not too nice You want real feedback! 21/02/62

Look Ma, I have a L-A-S-E-R! If necessary, get a laser pointer Will depend on your talk Get it a few weeks before your talk Play with it. Circle things. Make shapes. Be comfortable Get a second one for backup, or make sure session chair/host has one 21/02/62

Common Laser Pointer Moves The circle The underline The back-handed flick The epileptic-seizure inducer DO NOT POINT AT EVERYTHING Not everything is equally important Your voice can provide emphasis too 21/02/62

Right Here. See? Don’t point at your laptop screen They can’t see it 21/02/62

Ummmm… The… Uh… Yeah. Practice makes perfect Warning!!: OVER practicing can be bad… Do not read your slides like a script Most people lose 20 IQ points in front of an audience 21/02/62

Part II: Slide Design Goals: Avoid: Convey the necessary information Be readable/understandable Be interesting (enough) Avoid: Over stimulation Booooring 21/02/62

Logos We know you had support Don’t need to list all of them every slide If on first slide, don’t obscure title/authors Maybe save it for last slide 21/02/62

README.TXT Do not attempt to put all the text, code, or explanation of what you are talking about directly onto the slide, especially if it consists of full, long sentences. Or paragraphs. There’s no place for paragraphs on slides. If you have complete sentences, you can probably take something out. If you do that, you will have too much stuff to read on the slide, which isn’t always a good thing. Like the previous slide, people do not really read all the stuff on the slides. That’s why it’s called a “presentation” and not “a reading” of your work Practice makes perfect, which is what gets you away from having to have all of you “notes” in textual form on the screen in front of you. Utilize the Notes function of PowerPoint, have them printed out for your reference. The audience doesn’t need to hear the exact same thing that you are reading to them. The bullet points are simply talking points and should attempt to summarize the big ideas that you are trying to convey If you’ve reached anything less than 18 point font, for God’s sake, please: Remove some of the text Split up the text and put it on separate slides Perhaps you are trying to do much in this one slide? Reading a slide is annoying. You should not simply be a text-to-speech converter. 21/02/62

Font Size You are close to your monitor Your audience is far from the screen Tahoma 32 pt 28 pt 24 pt 20 pt 18 pt 16 pt 14 pt 12 pt 10 pt TNR 32 pt 28 pt 24 pt 20 pt 18 pt 16 pt 14 pt 12 pt 10 pt Courier 32 pt 28 pt 24 pt 20 pt 18 pt 16 pt 14 pt 12 pt 10 pt Comic 32 pt 28 pt 24 pt 20 pt 18 pt 16 pt 14 pt 12 pt 10 pt Lucida Sans 32 pt 28 pt 24 pt 20 pt 18 pt 16 pt 14 pt 12 pt 10 pt 21/02/62

Squint City If you find yourself saying “you probably can’t read/see this, but…” Then you probably have a BAD SLIDE! There are exceptions, but very few Test on real screen in conference room Not just your computer screen 15” away. 21/02/62

This is a really long title for this single slide, I should have just summarized Hard to read Many people don’t read the title anyway Should have been “Long Slide Titles” 21/02/62

Know Slide Boundaries People can’t read text that runs off the side of the slide 21/02/62

Bullets Aren’t Everything How many Levels of Hierarchy do You think You need * To express - Your point? 21/02/62

Speelchick How samrt will poeple thikn yuo are? Watch for: there/their/they’re too/to/two its/it’s 21/02/62

Picture This There are exceptions, but in general Don’t have only text on most of your slides Try to draw diagrams wherever applicable (Well-drawn) pictures easier to understand System Architecture There’s a CPU, a RAM and an FPGA and they’re all connected - The FPGA connects to the CPU’s data cache - The bus is 32 bits wide - Blah blah blah blah You have to visualize it yourself System Architecture CPU FPGA data cache memory main 32 21/02/62

Example Diagrams Compute-intensive sections on hardware wwwwwwwwwww wwwwwwwww wwwwwwwwwwwwwww wwwwwwwwww wwwwwwwwwwwwww w wwwwwwwwwwwww wwwwww Compute-intensive sections on hardware Hardware reconfigured for each FPGA Source code 21/02/62

Example Diagrams Compute-intensive sections on hardware wwwwwwwwwww wwwwwwwww wwwwwwwwwwwwwww wwwwwwwwww wwwwwwwwwwwwww w wwwwwwwwwwwww wwwwww Compute-intensive sections on hardware Hardware reconfigured for each FPGA Source code 21/02/62

Usually can’t read this… I See A Ghost More contrast on monitor than projector Different projectors == different results Colors to avoid with white are: Light Green Light Blue Pale Yellow Your slides should have good contrast Usually can’t read this… 21/02/62

Contrast Guidelines White background, black text is clearest Can use other (dark) text colors… But be careful -- don’t be distracting! Make sure to not use light-on-white or white-on-light Don’t using glaring colors If not an art major, don’t have to get fancy 21/02/62

Equations Ummm… okay… 21/02/62

Keep It Simple Do you really need all those equations? This is very instance-dependent! Depends on what you’re discussing Depends on your audience Sometimes you may need them Explain the variables and what they mean Give a “plain-text” description of it If you don’t need them, don’t use them! 21/02/62

Use Simple Examples This isn’t one. It doesn’t help. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z AA BB CC DD EE FF GG HH II JJ KK LL MM NN OO PP QQ RR SS TT UU VV WW XX YY ZZ a b c d e f g h j k l m n o p q r s t u v w x y z 21/02/62

Results You have lots of cool results Graphs are your friend… No one can read this No one can understand this Graphs are your friend… 21/02/62

Graphs Can Also Be The Enemy 21/02/62

Pick A Line, Any Line 21/02/62

Slide Organization [Tamara G. Kolda, 2002] Sample outline of a research talk: Title slide: credit to co-authors and funding agencies Up-front “carrot” (attention-getter) Outline Background material What you did new algorithm, theorem, proof, computational paradigm Why is it important numerical results contribution Summary and future work 21/02/62

Background Material Minimize background material At least 2/3 of talk should be original work Identify those who have done related work and spell their names correctly! Hint: People love to hear their own names. Describe motivating applications that will later tie into your results 21/02/62

What you did Emphasize your simple message repeatedly Back it up with details of algorithm and theory Use pictures and diagrams as much as possible in lieu of wordy explanation Keep notation to a minimum and avoid too many abbreviations Never use equation numbers—repeat the equation if necessary Illustrate your points via simple examples 21/02/62

How do you present an algorithm? Like this …? How do you present an algorithm? 21/02/62

Finding the largest among five integers Or like this …? 21/02/62

Tables and Figures Tables Figures Don’t make font too small Use color for emphasis Figures Be sure axes are clearly labeled Use color to differentiate lines 21/02/62

Why is it important? Emphasize an application What makes it a hard problem? Why should people care? 21/02/62

Summary and Future Work Repeat what you did Repeat why it is important Future work is important for recent PhDs because it shows you are thinking beyond your thesis problem Include contact info at the end email, web page 21/02/62

Fielding Questions Repeat the question. Talk. Demonstrate knowledge of standard problem solving. Draw a diagram. Specify an analogy. List the assumptions. List the ideas and tools that seem relevant. Respect the questioners and their questions Inevitably, someone will tell you your work has already been done by someone else! 21/02/62

Conference talk Title/author/affiliation (1 slide) Outline (1 slide) [Mark Hill, 1992] Title/author/affiliation (1 slide) Outline (1 slide) Background Motivation and Problem Statement (1-2 slides) Related Work (0-1 slides) Methods (1 slide) Results (4-6 slides) Summary (1 slide) Future Work (0-1 slides) Backup Slides 21/02/62

Take-Home Messages Know your audience Create a simple message and repeat it several times Allow plenty of time to prepare your talk Practice! Don’t block the slides during the talk Speak slowly, clearly Don’t run over on time Have fun and learn from your mistakes 21/02/62

Summary/Conclusion If your talk is more than 5 minutes, nice to summarize work & results Bring people back if they zoned out Remind them why you’re great Give “selling” points here 30x performance increase with only 10% area penalty Described novel method to create clean fuel from used cat litter 21/02/62

Bad Presentations Audience won’t see your work is great But will make fun of you from back row What does that slide say? Those are some NASTY colors… Dunno, I’m playing minesweeper Hey – it matches my tie. Please let it be OVER… zzz 21/02/62

Good Presentations Interesting topic, explained at audience’s level Slides are understandable and easy to see Good presentations reflect well on speaker! I understood this one! I wonder if this technique would work for my problem You should with a PhD… Let’s talk to them at the break But it’s outside my main area I never thought of that! Interesting 21/02/62

Thanks goes to … http://www.si.umich.edu/~pne/acadtalk.htm http://www.cs.dartmouth.edu/~brd/Teaching/Giving-a-talk/giving-a-talk.html http://www.cs.dartmouth.edu/~brd/Teaching/Giving-a-talk/phw.html http://www.cs.wisc.edu/~markhill/conference-talk.html http://csmr.ca.sandia.gov/~tgkolda/abstracts/giving-a-talk-snl-2001.html 21/02/62