Skip to main content

How I prepared for my first big conference talk

Last Friday, I gave a talk at AnDevCon Boston. I had about 4 months to prepare since the conference's Call for Proposal(CFP) deadline was in March and the conference was in July.

I have broken down my entire process of giving a presentation - from writing an abstract to giving the final talk into the following steps:
  • Choosing a conference and submitting a proposal
  • Breaking down the topic into smaller components
  • Giving my talk at a local meetup
  • Prepping for the conference
  • Prepping hours before the talk

Choosing a conference and submitting a proposal

The whole process of giving a talk started at the Write/Speak/Code conference which happened earlier this year in March. On Day 1 of the conference, I wrote down several topics that I have expertise in. I settled down on one topic which I knew would benefit several Android developers: Monetization. I wrote a quick abstract which was reviewed by attendees and mentors at the same conference. I was paired with a mentor and we quickly put together some slides and gave a 5 minute lightning talk on Day 2. I looked up upcoming Android conferences and AnDevCon Boston's deadline was a few days away so I went ahead and submitted the abstract I had written.

Now, not everyone has access to mentors or peer review when writing an abstract for a conference. So for those who are starting out, an abstract is generally about 400 words long that describes what you are going to talk about in your tech talk. Here's my abstract from AnDevCon Boston.

Time spent to write abstract and get it reviewed: 2 hours
 spent to prepare for a lightning talk: 2 hours
Time spent to give the ligthing talk: 5-10 minutes
Time spent to submit a proposal to a conference: 15 minutes 

Breaking the topic down into smaller components

When I first started out writing down my main talking points, I wanted to cover a lot of things. I jotted down all my thoughts on paper and on a giant google doc. I went through the documentation, code and Google I/O videos, discovered things I hadn't known before, and recalled a lot of the challenges and solutions on the topic. I gathered all of these notes into 7 smaller components.

Time spent to prepare: 8 hours

Giving my talk at a local tech meetup

I got in touch with the organizers of Android Alliance Philly where my talk was most relevant (since it is about monetization on Android) and told them that my proposal had been accepted. I was given a time slot of 45 minutes. Once I had the deadline and time limit, I refined my lightning talk slides, added new diagrams using and practiced my talk. I audio recorded myself and made sure to continue even when I made grammatical mistakes or struggled with segues into the next slides and sections. I listened to my recordings a few times to improve myself. The third time around, I was confident enough to give the talk without looking at my notes and without stopping.
I gave my talk at the Android meetup as mentioned in one of my older blog posts. The audience asked a lot of relevant questions which I noted down so I could cover them in my AnDevCon talk.

I also asked the attendees to fill up a feedback form with these questions and some of them actually did!
  • How did the speaker do?
  • How was the pace of the talk?
  • Did you get a better understanding of monetization on Google Play?
  • Would you recommend this talk to someone?
  • Was this talk useful to you? Why or why not?
  • Do you have any other comments?
Some of the feedback was that the code was too hard to read from the back, the diagrams weren't clear enough and that I needed to spend some time talking about the big picture before diving into the details.

Time spent to prepare slides: 4 hours
Time spent to practice talk: 3 hours

Prepping for the conference

AnDevCon Boston had a deadline for slide submission two weeks before the conference. A few days before the deadline, I refined my slides from the local talk and used Google Draw to draw new diagrams. I googled around to figure out the minimum sizes for font and lines on slides and went with 24 point for fonts  and 4 px for lines in diagrams. I tried to transition to Keynote but settled on Google Slides since I was already familiar with it. I practiced my talk before submitting slides to make sure the transitions between slides were smooth. 

Once the slides were submitted, I had two weeks to practice my slides. Since the time slot was for 75 minutes, I could only practice once every few days. I audio and video recorded myself every time so I could keep track of the time, my nervous ticks and my filler words (umm, uhh).

I also emailed the conference organizers to ask them logistical questions such as microphone availability, audience demographics, wi-fi access, number of projector screens and so on. A complete list is available at Questions to ask Conference Organizers

Time spent to prepare final slides: 4 hours
Time spent to practice talk: 3 hours

Prepping hours before the talk
I had the last time slot on Day 3 of the conference for my talk. I practiced once every night after Day 1 and Day 2 of the conference without my notes. I audio and video recorded myself to make sure I was within the time limit and had about 10 to 15 minutes to spare for answering questions. 

I also incorporated some of the tactics used by other speakers to engage the audience like asking them a few questions so that they could answer with a show of hands, asking them their names when they asked a question and repeating audience questions. (I vaguely remember doing some of these once I was at the lectern talking.) On the morning of the conference, I got up early to practice one last time. 

Time spent to practice talk: 3 hours

Over the months leading up to the conference, I read several blogs and email newsletters about public speaking and this amazing book - Confessions of a Public Speaker by Scott Berkun twice! I have listed some helpful links below:

My motivation for preparing so much was because I wanted to make sure I gave a good talk that would show that I had done my research and was worth everyone's time. 

I hope it was great so I'm invited to speak again. It was a fun and harrowing experience but I would do it all over again!


  1. Talent becomes excellence through practice. I have lot of respect for well prepared presentations.


Post a Comment

Popular posts from this blog

2017: Year In Review

We're a month into 2018 and I already have a lot going on for the next couple of months. But before things are in full swing, I wanted to take a step back and review the past year. Photo by Miesha Moriniere from Pexels In numbers Wrote 2 blog posts  Won 2 awards  Attended 5 conferences  Spoke at 4 conferences Attended 14 meetups Spoke at 4 meetups Read 12 books  A lot of firsts! Speaking This was the first time I gave 3 completely different talks on different topics like design-developer collaboration, public speaking and leadership, and mastering Android's app resources. It was also the first time I gave a talk with a co-presenter at a conference ( Chicago Roboto - Design Develop Deploy ) Community Organized and helped run the first Android meets iOS meetup at Philly Tech Week. Learning new things This year I immersed myself in Kotlin via Kotlin Koans, Kotlin in Action book and Koltin programming challenges. It took me a while to write my first PR

Recap of Android Summit 2017

I recently attended and spoke at Android Summit , an Android conference organized by the folks at Capital One. Special shoutout to Jared A Sheehan, Michael Jones and the entire organizing committee for running a fabulous event which raised $6000 for Women who Code. All speakers received a Phillips Hue Starter Kit as a speaker gift which I've used to toggle and dim my living room lights via Amazon Echo. So much fun! I had a prior commitment and could only attend Day 1 but here are my highlights. Process & Workflow A common theme on Day 1 was process and workflow talks which tied in beautifully with Kelly Shuster 's keynote. Kelly is an excellent story teller. In her keynote, she connected a story of communication from her theatre background to how developers, designers and testers need to work together to reduce boiler plate conversations when designing and developing apps. I gave a similar talk earlier this year at  Chicago Roboto  with my co-worker and designer  J

Chicago Roboto 2018 Recap + First Keynote!

Chicago Roboto was back again this year as a single track conference and there were a lot of excellent talks.  Last year I gave a talk with my co-worker and product designer extraordinaire Jess Moon about design and development workflows and this year I was back again but as a Keynote speaker. Keynote Giving a keynote was a stretch goal I set for myself in 2018 and I managed to achieve it early thanks to the Chicago Roboto review committee. The topic I chose was being an Android Advocate who brings teams and communities together. I will be writing a follow up blog post about my keynote process soon but before that, a quick shout out to Corey Latislaw and my coworkers at Warner Bros. Digital Labs who took a look at my first and second drafts and listened to all my half-baked thoughts and ideas. Achievement unlocked 🎉🎉🎉 - Gave my first keynote @chicagoroboto #chicagoroboto Slides with resources available at — Yash Prabhu (@yashvprabhu)