I've been actively improving my public speaking skills (one of the reasons why I blog less these days 😁) and giving talks in meetups, user groups, and conferences.
When I started two years ago, the whole experience was terrifying for me. I started to read blog posts from famous speakers around how to respond to
CFP (call for proposals) and practice at home. Choosing a topic can be very hard so I was trying to find something interesting that I feel comfortable talking about in front of audience.
At the same time, I started doing brown bag sessions (short sessions sharing something you know in your own company or somewhere you work for) at Readify - where I work as a consultant - and got some internal feedback around what I should improve and areas that needed more focus.
Let me tell you that what you read on internet or hear from others might not work for you, so you need to find the sweet spot and customise it for yourself wherever you can. This is true for both responding to
CFPs and also how to put together your talk.
Since I was looking for improvement, I took part in an internal program called speak easy where we try to gather in our office at least once a month and focus on an area.
We try to make it fun as well by doing something like PowerPoint karaoke where you need to talk from a slide deck that you haven't seen at all and topics are usually chosen at random. It as been so much fun that we've made it a part of program to keep the fun side of learning as well.
Long story short I got heaps of feedback from my short presentations on how do I talk, how is my physical movements, how slides are arranged and their logical correlation and many other aspects where every speaker should really care about.
I've learnt to research about the audience in a conference and choose a topic that matches so that it would be interesting for people and they don't feel their time is wasted.
But the reason for writing this post is not to tell you my stories, but to share with you all the things that I've learnt by submitting talks to conferences and how I got to talk to an official conference as a first time speaker. So let's begin.
When submitting a talk proposal to a conference, you have to be aware that more than 70 percent of your chance of getting accepted is around your title. It has to have enough information to let the reviewer know what it is about, what you're trying to deliver and who is your audience.
Since those days, I have near 90 failed attempts where I had to sit and think about what should I have done to make it more clear for the conference organisers what I am going to present but in a short sentence or two.
Think of this as your 30 second elevator pitch for the subject you are trying to present. It has to be catchy and informative.
Here are some of the titles I've used which are accepted:
- Need for speed 8, tune your web applications
- WebAssembly's post MVP future
- Micro frontend and web components, web technologies peace maker
I should tell you coming up with a good title, is probably the hardest part 😱.
When you are finished your title, it is time to start writing your abstract. Here is your chance to point out more details about the talk and its structure. You can put something that you couldn't put in title but was important to mention in here.
There is a really good resource from NDC conferences that I used around this which has tons of good points on how to write it and what is its structure. It is titled Make me an offer I can't refuse. I highly recommend you read this before submitting your abstract.
It not only covers the abstract, but also goes through title and some examples of good ones, then it talks about how agenda committees narrow down and choose talks for a conference, and many more useful points.
This might seem trivial, but I assure you it is as important as rest the information about your talk. Specially if you are a first time speaker like me, this plays a key role in accepting or rejecting your talk.
People who are reviewing the proposals won't know you. So you have to let them know who you are, what you do and why they should choose you to give that talk rather than another speaker.
I have near 50 different bio's which I've written in near 4 month of trying and then I became happy with two of those. I used those and they helped me with my talks getting accepted.
Knowing how much time do you have for a talk and preparing for that plays a key role on what content you put into your talk.
I've listened to many great speakers and don't prepare my content before I know it is accepted. This has helped me to not spend time on something that might take so much of my free time and I won't be able to use it.
There is a reverse relationship between time and delivery in my point of view. The shorter the time, the harder is to prepare for it. As an example I struggle to give lightning talks where as I feel comfortable giving a long one like 30 minute or an hour.
The point here is that no matter how much time do you have, you have to practice so many times that you would feel comfortable giving your talk fluently.
I know it might sound silly but talking in front of mirror is a great way to practice. You can see yourself and your movements, how you talk and when you stumble upon something.
How much eh, ah, hmm (and in general filler words like so, and, you know, actually, etc) you use when you talk and so on would be very obvious after you watch yourself talking. Another way is to record your talk and watch it later if you don't feel mirror is your friend.
There would be still a couple of points to consider when practising. First is that consider the possibility that your talk might start a bit later than schedule and you have less time that what you practised for.
This happened to me and I had to rush through my content, so much that I rushed through and finished very early (almost 10 mins).
I find it if you make your talk modular (a point taken from Tatham Oddie our CEO) it would be much easier to skip a section or two to make up for lost time. You can have different sections which are relevant and easily replaceable.
It also helps if you want to shuffle stuff around after practising because you realised that the relevance of a specific item is not correct where it is in your timeline.
Eating food before talk is a risk you probably want to avoid. Your projection is one of your main tools to deliver a great talk. If you listen to famous speakers, sometimes they talk louder if they're talking about something important. Their voice is not monotone throughout the talk.
This happened to me in a meetup where I had pizza right before my talk and I struggled with my voice throughout presentation.
Usually people expect you to give your slides, demo code, and references to them at the end of your talk. I usually have my slides uploaded and put a reference slide at the end with all the links. I will also schedule a tweet on Twitter with the link to slide around 10 minutes before my talk finishes.
Lack of references might affect the feedback you get from the talk because the audience feel you haven't provided enough information so they can follow the topic further.
Remember your talk is usually introducing something and you want your audience to go and explore it later. So give them somewhere they can start.
Almost all of the official conferences have a way for you to get feedback on your talk. This is very important for future because you can keep the good points and improve the weak ones.
Try to contact the organisers beforehand and ask them what is the feedback mechanism.
If they record your talk it is OK to ask for it later from them. Most of the conferences will do this for you and upload the video somewhere, but just in case you ask for it to have a reference for your next submission. I figured most of
CFPs have a place for a link to one of your previous talks recording.
Although I've delivered many talks, I still feel a bit nervous on the day. This is completely natural and you shouldn't expect otherwise. Even big names have confessed they have a bit of stress before their talk. You should learn how to calm yourself in those minutes and start the talk in a way that your audience feel at ease.
Doing a health check really helps. Check your connectivity and see if you can project to the main screen OK. Check whether your slides aspect ratio matches the display or not. If you have video in your slides, check whether they play fine before your talks begin, especially if it has sound.
This will help you to feel more relaxed when you begin. It eliminates the need to worry about the small things that can go wrong.
If you happened to watch Scott Hanselman and his talks, you will see he usually has live demos and writes code on the fly.
Some other big names do the same. But those are in this field for a long time. We can't compare ourselves with them. Of course it doesn't mean you shouldn't try, but not until you feel you have
enough confidence and a good
There are a million thing that can go wrong from connectivity issues to demo Gods 😈 preventing you from showing something which worked just a couple of mins ago.
One of the tricks I use is to pre-record all of my demos and put the video in my slides. It works very well and I don't have any stress whatsoever that something might go wrong when showing my audience how something works.
Read and study around public speaking. It seems simple when you watch people on stage but I assure you it is very difficult and requires a lot of time and effort to get it right.
Practice your talk multiple times until you feel comfortable and your speech is fluent enough and you don't stumble between or in the middle of sentences.
Get a mentor if you can and get help from them. Someone who has done public speaking can help you go a long way compared to when you prepare by yourself.
These are my go to places when it comes to gathering information about how to respond to proposals:
Here are some of the places I usually look for open call for speakers: