It is not a secret that one of Jappware's key values is support for the technical community. Therefore, we regularly take part in technical meetups and conferences organization, and one of our most important goals is to ensure the highest quality of technical talks.
Like famous GoF collected and described the most typical design patterns in software, our team collected a set of common mistakes speakers make during their talks over several years.
Off-course, this article is far from the excellence of the GoF's "Design Patterns" masterpiece, but we believe this experience is still worth sharing.
Choose the most important message you’d like to tell your audience.
You may also have one or two secondary messages, but not more.
Compose your presentation according to the classic structure:
Setup - introduce the problem you will present.
Central part - journey and trials you (or your hero) have passed through to resolve the problem. The culmination of your presentation should be here.
Resolution - summary, conclusions, lessons learned, etc.
Slides design and content
Slides should be numbered. There are multiple reasons for that, e.g., it’s easier to refer to the slide by its number during the QA session.
Slides layout should be standard whenever possible. Make sure titles, and other typical slide blocks do not “jump” when you switch between slides.
Let the audience track the progress of the presentation. You may use one or more of the following:
announce total slides count during the intro
specify it on your slides (e.g., for PowerPoint: https://goo.gl/QyAbXg)
Make sure fonts are readable, especially for the audience on the last rows.
Use consistent fonts. It includes font families, font sizes, and font colors.
Don’t use Comic Sans MS unless your presentation is a comic. More on this:
Add slide with your contacts. This slide should not be the last slide of your presentation. Preferably it should be after the concluding slide, but before the Q&A (Questions) slide.
Third-party content (photos, pictures, articles, text from a book, etc.):
Respect content license - do not include any content unless you are authorized to do so.
Specify sources of the content. For example, specify the URLs of the images used on slides (e.g., place a reference is in the slide’s footer or under the picture).
Add a slide with a list of resources used in the presentation, such as [links to] articles, books, etc.
Include QR codes for links.
Highlight important part of the code snippet
One message - one line (if possible): if you explain a line of code (operator, statement, function calls, etc.), it should fit into one line on the slide.
Use animation when possible. By animation, we mean not all these fancy slide transitions. It’s rather about showing the information on the slide in small portions if there is a lot of content. You should uncover or highlight the information piece by piece as you speak.
Avoid infinitely-looped gifs or minimize their exposition time. Such gifs might make your audience sick.
If possible, determine the audience level in advance, and best guess the optimal level of details for your presentation.
The above is not always possible, though. In most cases audience level is diverse. Be ready that there will be newbies, middle level, and experts. Don’t make any assumptions about audience level before you start the presentation, though.
Prepare slides explaining basic terms and concepts.
Don’t be afraid to explain “obvious things”; for many listeners, they are not so obvious :)
Try to determine the level of the audience as you present. If you feel that the audience is mature enough, you may spend less time explaining basics and vice versa.
Practice your speech in front of a mirror. Rubber duck, pet, partner, or a friend may help too.
Record the amount of time spent on every slide and overall presentation time (PowerPoint’s features can help you here).
Determine the “outlier” slides - slides that take significantly more time than average. Think whether that’s OK, or maybe it’s worth splitting the slide into smaller parts or omitting some details.
Check time restrictions with the event organizers and make sure your presentation fits.
Think about the level of details you want to speak on. Adjust the level of details according to the expected audience.
Try to predict questions and be ready to answer them.
Practice speaking moderately (not too slowly or too quickly). Remember - people need some time to “consume” the information.
Practice not to read your slides or notes.
If there are complicated statements, think about how you will compose the sentence so that it’s easy to understand. Prepare two or more variants for such a sentence.
We recommend you conduct several trials where you speak to a trial group. It might be a group of 3-5 coworkers, an event program committee, etc. Collect feedback and adjust your presentation accordingly.
If, during the trial, reviewers repeatedly run ahead asking questions which you plan to cover in future slides - rethink your storytelling; maybe the sequence of information needs to be adjusted.
Ask experts to write down their comments, ideas, and suggestions. Discuss all of the notes after the trial. Ask reviewers to send you their notes (do not waste time noting everything yourself).
In the conference hall
If possible, visit the conference hall or the stage a few days before the presentation.
Determine optimal slide aspect ratio (4:3 or 16:9) for given screen and projector.
Make sure your equipment is compatible with the conference hall equipment and everything works well. If it’s incompatible or doesn’t work, ask the organizer to resolve the issue. Examples:
projector cable and adapters
presentation RC, laser pointer (ideally, bring your own)
flip chart or whiteboard, markers
comfortable and safe laptop stand (make sure your laptop will not fall from the stand)
Pay attention to the hall size (e.g., how close if the first row and how far is the last row from the projector screen) and adjust your slides accordingly.
If you plan a demo, make sure all the fonts in your IDE, browser, or other tools are
visible for people on the last row (also consider people with poor eyesight)
Make sure your slides and tools look well, considering the lighting of the hall. Adjust your slides theme and OS theme accordingly (don’t forget about your IDE, browser, and other tools you plan to present).
Check if you can speak loudly enough so that everyone can hear you. Request a microphone if it’s hard to speak loud enough.
Announce the high-level agenda clearly. You may also mention what’s NOT you talk about or what aspect of the topic is NOT covered (manage audience’s expectations).
Don’t read your slides
Speak to the audience, not to your slides or a window or a sidewall. It’s even more critical if the screen is behind you or if you have no microphone.
Make brief pauses between chapters (sections of your presentation). People usually need a moment to “process” the information.
If you are uncomfortable keeping silent for a moment, take a sip of water or ask if there are any questions so far.
You may use “wrap-up” slides to summarize the current section. The “Wrap-up” slide should precede the next section’s title slide. It helps the speaker not jump to the next section too quickly and lets the audience rethink what they just heard.
Observe the reaction of the audience and adjust the level of details based on the reaction.
Be ready that something may go wrong (presentation RC doesn’t work, demo failed, the internet failed, etc.)
prepare some jokes and keep calm ;)
don’t panic and don’t emphasize the issue
do not make excuses
prepare plan B for such situations (e.g., prepare the working version of the demo application in a separate git branch in advance)
If a live coding demo is a part of your talk, it’s often a good idea to publish the code in a public GitHub repo. Include also a README file with brief instructions (prerequisites, how to build and start the app etc.)
(Optional) Organizers may ask you to record your screen during the presentation so that they can include your slides and demo in a high quality into the event video recording. Please make sure you have enough free disk space and screen recording software installed.
If you provide a link to GitHub repo, your site, or similar, and you want the audience to follow the link, you may include a QR code.
There are lots of these on the internet. Consider the following resources before the first trial:
If you have any questions or suggestions - feel free to contact us at firstname.lastname@example.org