I recently gave a Speaking at Tech Events for Beginners workshop. Here, you’ll find the slides with my notes, and some resources for continuing on with public speaking. You can also download the accompanying worksheets.

Table of Contents

  1. Slides with Notes
  2. Attribution
  3. Resources
  4. Local Speaking Opportunities

Slides with Notes

Welcome to NerdLab YYC's first workshop, Speaking at Tech Events for Beginners.
Today, you're here to learn how to speak at tech events.
And I'm here to help. My name is Heather Tovey, and I'm a co-founder of NerdLab YYC.
I've given a few talks for Calgary's tech community, including a talk on learning how to code as well as a workshop on defeating impostor syndrome.
I'm also a frequent conference attendee. I love hearing from diverse perspectives, and I'm excited to get more beginners speaking at tech events.
So let's talk about today's workshop.
Today, you'll create and present a lightning talk.
For today's workshop, a lightning talk is 3 minutes long.
You'll learn how to brainstorm for ideas,
write a talk proposal,
outline your talk,
make slides,
practice your talk,
and then, at the end of the day, you'll present your talk to the rest of the group.
A few notes! First, today's activities are time-sensitive. Keep your eye on the clock so that you can finish up each activity.
Also, this workshop is collaborative. You will be working in groups.
It's also beginner-friendly. This is a safe space for you to make mistakes, ask questions, and learn.
With that in mind, it's important to note that NerdLab YYC does have a Code of Conduct. We're dedicated to providing a harassment free experience for everyone. See the detailed version of our Code of Conduct for more details.
In addition to our Code of Conduct, we have one very important guideline for today, and that is to be constructive and helpful.
During your group sessions, you will be providing suggestions and feedback, and it's important to keep that feedback constructive.
Try to frame your feedback within these 3 points. You can tell the other person what they did, the impact of what they did, and how they can improve.
For example, I could say, "You spoke very fast. People might miss something. Try slowing down and adding pauses."
What we don't want today is destructive feedback. Your proposal is awful, your slides are ugly, your talk is boring.
This isn't helpful, and it's just mean, so don't do this.
If there are any issues today, please come talk to me about it. Or you can email me at [email protected] or email NerdLab YYC at [email protected] We'll try to take care of issues as quickly as possible.
Okay, so now, you should already be in the groups you're going to be working in today.
I'd also like to make sure that each one of you has a set of worksheets. We will be using these worksheets during our activities today, so it's important that you have one.
Alright, so let's move on to our first activity of the day. Introductions. It's time to get to know the group members that you're going to be working with today. I'd like for you to take 5 minutes and go around the group. Each group member should introduce themselves, say who they are, and why they're here. And on page 2, you can take notes, as needed.
Now that you've gotten the chance to get to know your group members, it's time to setup tech for the day. Please turn to page 3 of your worksheets. There, you'll find instructions to go through. We'll be using Google Drive to share and collaborate today, and you'll find a link to your group's Google Drive on pg. 3. Please go ahead and open up your presentation software of choice. If it's not one of the ones listed on the worksheet, please let me know.
Okay, let's talk about Brainstorming! Brainstorming can be difficult.
A common refrain I hear is "Oh, well I'm not an expert. What would I possibly talk about?" But people tend to overthink how much they need to know about a topic before they can talk about it.
What you think you need to know may be an entire world of information around a topic. But in reality, conference talks just aren't long enough to say everything there is to say about a subject.
What you actually need to know are the points you want to make and maybe a few closely related items. It's okay if you don't know everything vaguely related to your topic, and it's okay if you don't know how to answer every question. Most speakers don't know everything about their topic.
It's also important to note that experts aren't always the best for the job.
Experts know a lot. They're all the way over here.
But many conference talks are made with the beginner in mind. Introductions, how-tos, tips and tricks.
The problem is that while experts may have the knowledge to give these types of talks, they've forgotten what it's like to be a beginner, and they've forgotten what they struggled with. They may find it difficult to communicate information to their audience without overwhelming beginners.
The people in the middle, with intermediate knowledge and skills, are the best for this kind of job. They have enough knowledge to share, and they still remember what it's like to be a beginner. They're more able to communicate without overwhelming their audience.
So basically, you definitely know enough to give a talk.
So now that you're maybe more motivated to brainstorm some talk ideas, let's talk about the types of topics you see at tech conferences and events.
There's the Development topic. These talks tend to cover topics like programming languages and frameworks.
An example of this would be "Double Feature: SSL Introduction & Git Basics for Developers & Designers" by Mike Tighe.
There's also the Design topic. These talks tend to cover things like design tools (like Photoshop and Sketch), User Experience, and even traditional art.
An example of this would be "Kickstarting Your Sketching and Visual Thinking Skills" by Eva-Lotta Lamm.
Then, you have the Business topic. These talks tend to cover topics like Customer Needs and SEO.
An example of the Business topic would be "The ABCs of Analytics" by Andrew Wright.
Next, we have the Personal Development topic. These talks tend to help people in their careers and personal lives and include topics like career-building strategies and finding creative expression.
An example of this type of topic would be "Anatomy of a Job Search" by Julie Pagano.
So those are the types of topics you may see at a tech event, but where do you find inspiration?
Think about what you work on a lot. What do you do at work or what do you study at school?
Think about what you work on sometimes. Are you involved in any open source work or side projects?
Think about what topics excite you. What are you passionate about?
And think about what you wish more people would talk about. Are there any questions you had as a beginner that you wish more people had answered?
Now, it's your turn to do some brainstorming. Turn to page 4 in your worksheets, and take the next 5 minutes to fill out the brainstorming worksheet on your own. During your 5 minutes, write down as many topic ideas as you can think of as quickly as you can. Don't worry about whether or not ideas or good or bad or whether or not you have enough material to give a talk. Just dump everything in your brain onto paper. You'll have time to choose one of the topics later.
Now that you've had some time to brainstorm ideas, it's time to get group feedback. Take about 5 minutes each to share your ideas with your group. During your 5 minutes, go over your ideas and note which ones are your favorites. Then, your group should give you constructive feedback, ask any questions they have, and maybe even help you to generate new ideas. Our Timekeeper will let you know when it's time to switch to a new group member.
Okay, now that you've received some feedback on your idea, I'd like for you to take the next 5 minutes and select the topic that you're going to use for the rest of the day. Remember that your talk today will be 3 minutes long, so be sure to choose a topic that you can discuss within that period of time.
Okay, now that you've chosen a topic idea, it's time to start writing a talk proposal.
A talk proposal is generally made up of a title and a description.
Many conferences use a CFP (or Call for Proposals), and ask people who want to speak at their event to submit a talk proposal. The conference organizers then use these talk proposals to decide who gets to talk at their event. So a good talk proposal can your talk selected for an event.
A talk proposal can also encourage people to attend your event. Here's the proposal that we put on Meetup for this workshop.
A talk proposal can also encourage people to attend your talk over someone else's talk in the same time slot. For example, I chose to attend Lindsey Wiebe's talk on User-Centric Site Improvement over the other talks in the same time slot because her talk was more relevant to my interests.
So let's talk about creating a talk title. There are generally 3 types of talk titles.
There's the descriptive title.
Examples of descriptive titles include "Speaking at Tech Events for Beginners" and...
..."Web Accessibility: Making Websites Better for Everyone" by Stephanie Hobson. These titles are descriptive because you get a general sense of what the talk will cover just by reading the title.
Next, you have the cute and descriptive title.
Examples include "What Your Mom Never Told You About Content Creation & Content Writing" by Meghan Somers.
"Here Be Dragons - JavaScript Debugging" by Rami Sayar. These titles are descriptive because you get a general sense of what they'll cover, but then they also add a fun element to the title.
Last, you have the cute title. And it's important to pair a cute title with a really great description.
Some examples include "The Missing Slice" by Lea Verou. Not a talk about pizza. It's about using CSS and SVG to creatively solve problems.
"The Humans are Dead" by Mario Klingemann. Not a talk about zombies, though that would be cool too. It's actually a talk about teaching computers to be creative.
Descriptive is usually better, especially for beginners. Descriptive titles are easier and faster to write, and you don't have to worry about people skimming over your titles without reading your description.
So now that we've talked about creating a talk title, let's go over how to create a description for your talk. Your description should answer questions for the audience.
What is the talk about?
Why is the talk important?
What will people get out of the talk?
Who is the target audience for the talk?
It's important to ask for help when writing your talk proposal. Talk proposals are similar to job resumes, in that they help you to get your foot in the door. So don't be afraid to ask for help with proofreading and making sure that your talk proposal is clear, concise, and engaging.
Alright, so now it's your turn to write a proposal. Turn to page 5 of your worksheets, and then navigate to your group's Google Drive. Then, hit "New" and then "Google Docs" to create a new document. Title this document with your name so you know which one is yours. Then, take the next 10 minutes to work on a rough draft of your talk proposal. I recommend starting with the description first. Answer each question on your worksheet. 1 sentence per question is fine. Then, write a descriptive title for your talk. There are a few examples for you on page 6. Keep your talk proposal short, as your talk is only 3 minutes long. Remember to keep your eye on the time so you can finish in time.
Now that you've had the chance to work on the rough draft of your proposal, it's time to share with your group. I'd like for each of you take 5 minutes, and during your 5 minutes, your group should read through your proposal, ask you any question that they may have, and then share constructive feedback with you. Once your 5 minutes is up, move to another group member. The Timekeeper will remind you when it's time to switch group members.
Now that you've gotten feedback on your proposal, I'd like for you to take the next 5 minutes to finish your proposal before we move on.
Before we move on, I'd like to take a minute to talk about managing your expectations for CFPs.
Rejection is normal (even though it hurts). Even experienced speakers get rejected.
To explain why that is, pretend that this is a conference with only 10 speaking slots.
And here's your awesome proposal.
Ideally, your awesome proposal gets selected into one of those 10 speaking slots.
But a ton of other people have also submitted potentially awesome proposals.
And the conference organizers can still only choose 10 from allllll of those proposals.
Conference organizers also have to consider how the talks fit together, how to choose between multiple submissions with similar topics, and what talks were given last year. And a million other things go into deciding who will talk at a conference. So just because you may be rejected doesn't mean that your proposal is bad. It just means it wasn't the right proposal for that particular conference at that particular time. You can work on your proposal, but more importantly you should submit your talk proposal to as many conferences as you're interested in attending. It's definitely a numbers game.
Okay, so now let's cover how to outline your talk. Outlines are important for organizing your thoughts and lead to a more well-thought out presentation.
Outlines typically consist of an introduction, 2-4 high-level topics or points, and then a conclusion. In the introduction, you would introduce your topic and write down why it's important, then you would write down a few points that you're going to cover in your talk. In the conclusion, you'll write down how everything ties together and what you want your audience to take away from your presentation.
So now, it's your turn to write an outline. Please turn to page 7, create a new Google document in the Outlines folder of your group's Google Drive. And then take 10 minutes to work on your outline. I recommend sticking to 2 points (as you only have 3 minutes to talk). And when you're finished, you should have a short introduction, 2 points with maybe a few short notes, and then a quick conclusion to tie it all together. There's an example for you on page 8. Keep your eye on the time, so you can finish.
So now that you've created a rough draft of your outline, it's time to get feedback from your group. I'd like for each of you to take 5 minutes, and during your 5 minutes, your group should read through your outline, ask any questions they may have, and offer constructive criticism. If you're having trouble wording something, this is an excellent time to ask for help. The Timekeeper will remind you when it's time to switch to another group member.
Okay, now that you've received some feedback on your outline, I'd like for you to take 5 minutes to finish it up.
Okay, let's cover how to make slides!
The biggest advice I can give to you is to keep it simple. Slides are merely a prop or a backdrop to your content. They aren't the content itself. So let's talk about a few things that go into making good slides.
First up, typography. Keep typography simple.
Choose a few fonts that you really like, perhaps like Open Sans here. And then stick to 1 or 2 fonts throughout your presentation for consistency.
Don't use scripty or cutesy fonts, as those fonts tend to be hard to read. Some fonts to avoid include:
Comic Sans.
Papyrus.
Lobster and Lobster 2. While these last 2 may be popular, they're overused and a bit difficult to read.
But more important than the fonts you choose is the way you present them. Don't use tiny text.
Use big text.
Use huge text.
Use ridiculously massive text! You want people to be able to see what's on your slide.
"But what about all my bullet points? Don't I need to use a smaller font-size so I can get all my bullet points on one slide?"
In a word? No.
At most, you should have a few bullet points on one slide. You don't want people reading your slide instead of listening to you. A general rule of thumb is one thought per slide.
And that brings me to code on slides.
You may see something like this, where someone has put all of their code on one slide. They use a small font-size and it's difficult to follow along.
What you want to do instead is only take a small chunk of code to step through at a time. Here, I increased the font-size and increased the line-height to make this code a bit more readable. But we can still do better. There are a lot of colors here. And while colors are great when you're working in a text editor, they can be a bit distracting when you're explaining code on a slide.
So take out of all the color except for maybe one highlight color to help guide your audience through your code.
You can also use comments to help guide the audience through your code. Here, I've stripped out the code and replaced it with comments that help to explain what the code does.
And then, you can use your highlight color and comments to guide the audience through your code as you step through it.
Another tip? Don't put important content at the bottom of your slide. Inevitably, someone much taller will sit in front of everyone in the back, and those people in the back won't be able to see anything on the bottom of your screen.
Okay, so now let's talk about choosing colors. Like everything else, you want to keep colors simple. Choose a few colors that you like, and try to stick to a color scheme throughout your presentation.
You should also be mindful of the contrast between the text and your background. High contrast, where the text color is very different from the background color, is more likely to have good results.
Your slides are unlikely to look the same on a projector screen as they do on your computer screen. Using low contrast colors means that people will have a hard time seeing what's on your slide. But if you use high contrast colors, your audience will be able to see your content even if you get stuck with a crappy projector.
High contrast is also important from an accessibility standpoint. People with color blindness have trouble distinguishing between colors with similar contrast. Red-green color blindness, for example, is very common. And people who are color blind may have trouble reading this slide. Plus, this slide is very ugly!
High contrast is especially important for displaying charts and diagrams. We often mean green to mean "good" and red to mean "bad", but without good labeling, this can make things difficult for people with color blindness.
For example, they may see something like this. Which segment is good and which segment is bad? It's hard to tell at a glance.
Okay, so let's talk about supporting imagery. Images help people to connect with what you're saying and they help people to remember information long after the presentation is over.
A great place to find images is the Noun Project. You can type in any noun, and it can give you a ton of amazing images. This is what I've used throughout this workshop.
If you're a cat person, they have "Cat Cuddling."
If you're dog person, they have "Barking Dog."
They even have something for the shark lovers among you.
The images on Noun Project are generally licensed as Creative Commons with attribution. And what that means is that you can use the images for free as long as you credit the people who created the images.
Another place to find great Creative Commons imagery is flickr.
And there are a ton of other amazing resources for free and beautiful images. Just remember to credit the creator.
Pop Culture is a fun way to add imagery to your presentation.
But be careful not to overdo it.
You don't want to end up with a presentation that's 80% silly memes and only 20% content.
Because as the saying goes, content is king. Make content the star of your talk, and only add extras as they improve your presentation. Keep it simple.
Okay, so now it's your turn to create slides. I'd like for you to turn to page 9 in your worksheets. There, you'll find some guidelines to help you create your slides. Over the next 20 minutes, you should work on a rough draft of your slides using your tool of choice. Remember to start with content first, and only add extras if you have time.
So now that you've created a rough draft of your slides, it's time to review your slides with your group. So each of you should take 5 minutes, and during your 5 minutes you should quickly walk your group through your slides. Just quickly explain what you'll talk about on each slide. And then your group should ask questions and give you constructive feedback. The Timekeeper will let you know when it's time to switch to a different group member.
Okay, now I'd like for you to take 5 minutes to finish up your slides based on the feedback you just received.
So now let's cover how to practice for your talk.
The best advice I can give you is to practice a lot. The most natural speakers are the ones who have practiced many many many many times. Giving a talk is one of those things that everyone is bad at when they start out, and you can get a lot better as you practice.
When you're practicing, it's important to note down how long your talk is taking you. You want to make sure that you don't go over or under your time, and making note of how long your talk is taking you as you practice will give you the opportunity to make adjustments as you go so that you don't have to remove or add a large chunk of content right before a talk.
Okay, so now it's time for you to practice your talk. Please turn to page 10 of your worksheets. There, you'll find a place to take notes and jot down the time it's taking you to get through your talk. So over the next 15 minutes, I'd like for you to practice your talk twice, and make any adjustments that you need to. Once you've practiced twice, please upload your slides as quickly as possible to the Slides folder in your group's Google Drive. Once you've uploaded your slides, you can keep practicing if you still have time.
Congratulations on creating a talk today! And now it's time to start presenting talks.

These workshop materials are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Attribution

Thank You

Thank you to Julie Pagano for the source material for this workshop! NerdLab YYC definitely could not have done it without you.

Also, thank you to Poornima Vijayashanker and Karen Catlin for providing free ebook copies of their book Present! A Techie’s Guide to Public Speaking to our workshop attendees. Here’s my review!

I've given a few talks before, and I've previously struggled to find one specific resource for tips and tricks on public speaking. This book answers so many of the questions that I've had and so many of the questions I didn't even know to ask. There are many personal anecdotes and examples throughout the book, and these examples really helped me to understand how to implement the strategies found within each section. And while I would definitely recommend this book to anyone interested in public speaking, the tech-specific advice (e.g. how to present code on slides) is especially helpful.

I've been having a lot of fun going back through the activities as I put together a new talk. And you better believe I've been practicing power poses.

Thank you to Poornima Vijayashanker and Karen Catlin for this invaluable resource.

Images Used from Noun Project

  • Presentation by Gregor Črešnar
  • User by Melvin Poppelaars
  • Speech Bubble by Lisa Krymova
  • Gears by Roman J. Sokolov
  • Woman by Jasmin May
  • Notepad by Vectors Market
  • Message by Dmitry Mamaev
  • Presentation by Jamison Wieser
  • Presentation by Rutmer Zijlstra
  • User by Mete Eraydin
  • Timer by K Design
  • Collaborative Learning by Duke Innovation Co-Lab
  • Work Group by Gerald Wildmoser
  • Questionnaire by Yu luck
  • Thought Bubble by Jason Santos
  • Technical Assistance by Mon Aguilar
  • Art by Will Deskins
  • Briefcase by Aha-Soft
  • Career by Martha Ormiston
  • Working by Creative Stall
  • Working by John Caserta
  • Woman by TukTuk Design
  • Fireworks by James Keuning
  • Question by Tommy Lau
  • Pizza by Alex Vaughn
  • Zombie by Stephen Peluso
  • Sad Bunny by Bradley Ashburn
  • Crown by sortagreat icons

Resources

Here are some great resources (some with resources of their own) to help you through your public speaking journey.

Local Speaking Opportunities