Outline of presentation skills training:
WORK IN PROGRESS -- NOT FINISHED
Introduction
This 30-45 minute course is for geeks who feel they need to brush up their presentation skills before OSDC. It will concentrate on:
- Structure
- Speaking style
Attendees are expected to bring a short, but complete, presentation (3 mins) that will be given and then reviewed. It is suggested that they bring an extract from their OSDC presentation, however it is important that it be self contained (i.e. it has a beginning, middle and end).
Course Outline
Introduction and objectives
- Improve style and techniques for technical presenters
- Improve self confidence
- Provide specific guidance for OSDC presenters
Documents vs. slides
For technical presentations it really helps to have a corresponding paper. This paper has several benefits:
- It gives attendees something to refer back to, when remembering your talk
- It gives non-attendees something to know what they missed out on
- (but most importantly) It gives you the opportunity to put your thoughts down in a useful order
People who do a lot of presentations can get away with creating an outline and then working directly with their slides. Everyone else really ought to write a paper.
Content
If you haven't written a paper, then hopefully your proposal specifies your audience and assumed knowledge.
Decide now:
- What is the objective of your presentation and message you want to give? e.g.
- Teach a new technique
- Sell an OSS product
- Persuade the community on some issue
- If there will be demontrations:
- Do you really need a demonstration?
- Will be be simple enough to be understood?
- Will it make people go Wow? Or might it be boring?
- Be careful about demonstrations that show multiple activites in the same segment. They can be cery hard to follow and difficult to explain
- Can you create a robust demonstration -- remember you will need some reliable way to reset the demonstration configuration back to the start.
Tell a story
- People love stories and suspense is great
- Introduce us to a problem as if you're telling a story
I was working in a job running the campus email system some years ago when I got a call from the chairman of the statistics department.
"We're having a problem sending email out of the department."
"What's the problem?" I asked.
"We can't send mail more than 500 miles," the chairman explained.
- Your story doesn't have to be 100% true
- But it does have to be engaging.
- Give us an idea of some of the solutions you tried
- Suggest obvious but wrong paths if they exist
"I see," I said, and put my head in my hands. "When did this start? A few days ago, you said, but did anything change in your systems at that time?"
"Well, the consultant came in and patched our server and rebooted it. But I called him, and he said he didn't touch the mail system."
http://www.ibiblio.org/harris/500milemail.html
- Work up to your solution, and then present it
- Talk briefly about the consequences
- Then finish up.
Non-stories
Not all topics lend themselves to stories. In this case you need to be even better at presenting.
- Start the talk with a description for why the audience should care.
- Pose it in terms of what they might be looking to get out of the talk, usually with a question. For example "Have you ever needed to do X?"
- Explain the problem domain
- Cover some of the various possible solutions
- Give *your* answer
- Discuss any relevant aspects of your answer
- Finish up
Content assumptions
- Be careful about assuming specific knowledge, you will have a very diverse audience
- Not everyone will have used Linux
- Not everyone knows XUL
- Rule of thumb
- Major topics or jargon should be explained. This includes the title of the your presentation
- Other terms should be expanded when first used e.g.
- The Apache Web Server.
- Note also that terms like Apache have multiple meanings
- Apache is
- A web server
- An organisation,
- The name associated with a leading OSS license
- An umbrella for many software projects
Material
- Slides
- Written material and Papers distributed before, during or after
- Demonstrations
- Online materials
Structure
- Simple to more complex
- Make sure you get your important message over first
- Conclusion
Slides
- When not to use slides
- Slide layout
- Pace
- Alternatives to slides
Speaking
- Do
- Speak slowly
- Loudly
- Use tone and variety
- Scan the audience and try to make eye contact
- Seek confirmation from audience
- Dont's
- Read your slides
- Use cliches
- Mumble
- Talk too fast
- Wander off the topic -- slides can help you stay on track
- Let members of the audience highjack the presentation
- It's you presentation,so it's OK to force the presentation onwards and offer to take material offline or even point out that the question or interruption is not relevant
- Practice: Practise several times, in front of friends and colleagues
- Timing
Room layout
Backup of slides
It is always a good idea to assume the worst -- either your
- Printed
- Have a printed copy of your presentation that can be photocopied and given to the audience -- would you presentation work without access to any demonstration?
- Other Media
- Put the slides onto a thumb drive, in some neutral formt like S5 or HTML if possible
- On-line
- Place the material on a public web site
- Projector and laptop
- For deluse cover take a spare laptop and projector with you -- however that is not an option for OSDC
Printed copies and printed material
- OSDC provide all attendess with a paper copy of the proceddings before the presentation. Will you lay yours out to give room for note tacking. Whill you provide OSDC and the attendees with slides or a written paper.
OSDC Specifics
- Presentation format. OSDC require that you supply your own laptop of that your presentation can be displayed via OpenOffice or a web browser.
- Backup
- Publication and copyright
Practical work
- Each student will be expected to come with a complete 3 minute presentation which they will give and be reviewed
Notes
Supporting Material
And here I should put some useful links to external material
License

This work is licensed under a Creative Commons Attribution-ShareAlike 2.5 License.