Speaking for Geeks: What Should I Talk About?

Freshness Warning
This article is over 3 years old. It's possible that the information you read below isn't current.

You’ve decided to give a talk. You’ve found an interesting place to speak, perhaps a local tech meetup group. What you need now is a topic. The call for papers closes tomorrow, and you have no idea what to speak on.

Panic.

Coming up with a talk idea can be nerve wracking. You want to propose something good, which means something creative and well thought-out, but doing that on a deadline is tough. Here’s some ideas based on what I do.

Dust off an old talk. The best talks I’ve given are ones I’ve given before. I’ve had the chance to see, in front of a real audience, what works and what doesn’t. I’ve polished my examples, I’ve found better ways of making it flow, and I’ve probably improved my slides and my talk abstract.

This only works for conferences that have a different audience than the ones you’ve give the talk to before. If you gave the talk to last year’s industry conference, you probably don’t want to give it again at this year’s. Or if you gave the talk last month at a Javascript conference in one city, this month’s web developer event might have a lot of audience overlap.

Don’t just recycle the same talk, though. It’s hard to have any energy as a speaker if you’re repeating the same thing all the time. I like to add new information, remove stale things, and generally tweak the talk each time I give it.

Maintain a list of ideas. Every time I think of something interesting, I add it to a list of ideas. I have a notebook in Evernote called Talk Ideas. The title of each note is the subject of my idea. In the body, I throw a few notes. What made me think of this idea, possible angles for the talk, the types of conferences I might want to give it at. Not all of these ideas will turn into talks. Some might become a blog post. Some might become both. Some might die when I realize my 2am insight is really half-baked.

This takes a lot of the pressure off. Now when I have a conference coming up that I want to speak at, I can look at my past talks and see if something fits. Or I can look at my talk ideas and see if there’s a great fit.

Some of the talks I have in my ideas notebook right now are:

  • Everything I need to know about startups I learned from watching baseball
  • What language X can teach us about better language Y development
  • Big data for non-nerds
  • How the early days of blogging parallel the emerging API economy

Coffee Roasting at BarcampBreak the mold. Don’t be afraid to give a talk that doesn’t exactly match the conference. At a tech conference, generally geeky things can be interesting, and organizers are often looking out for things that aren’t yet another survey about how to use continuous integration/test driven development/containers/whatever.

At three different barcamps, I’ve given demos on home coffee roasting. I brought in some equipment, took everyone outside, and cooked some beans. Talked through the process along the way, explained how to get started yourself, and ended with a coffee cupping. One of those was 9 years ago, and Cal Evans still brings it up from time to time (photo here by Cal).

I once gave a talk at a Ruby conference about how to avoid lock-in when using cloud services. Although I didn’t mention Ruby once, the talk went over well because the Ruby community tends to use a lot of cloud services and APIs.

I spoke at OSCON a few years ago about how to make sure the user interface of your application is ready for IPv6. This wasn’t specific to open source, but was useful to the audience because they are creating interfaces.

The key is to make sure your talk fits the audience. Put yourself in their shoes and ask if you would find the subject interesting.

Don’t wait for that conference to come calling before you start planning for it.

This is part of a series on becoming a better public speaker. Read the rest of the series.


Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Follow me on Twitter

Best Of

Recently Read

Get More

Subscribe | Archives

Recently

Feature voting is harmful to your product (Feb 7)
There's a lot of problems with using feature voting to drive your product.
Encouraging 1:1s from other managers in your organization (Jan 4)
If you’re managing other managers, encourage them to hold their own 1:1s. It’s such an important tool for managing and leading that everyone needs to be holding them.
One on One Meetings - a collection of posts about 1:1s (Jan 2)
A collection of all my writing on 1:1s
Are 1:1s confidential? (Jan 2)
Is the discussion that occurs in a 1:1 confidential, even if no agreed in the meeting to keep it so?
Skip-level 1:1s are your hidden superpower (Jan 1)
Holding 1:1s with peers and with people far below you on the reporting chain will open your eyes up to what’s really going on in your business.
Do you need a 1:1 if you’re regularly communicating with your team? (Dec 28)
You’re simply not having deep meaningful conversation about the process of work in hallway conversations or in your chat apps.
What agenda items should a manager bring to a 1:1? (Dec 23)
At least 80% of a 1:1 agenda should be driven by your report, but if you also to use this time to work on things with them, then you’ll have better meetings.
Handling “I don’t have anything to talk about” in your 1:1s (Dec 21)
When someone says they have nothing to discuss, they’re almost always thinking too narrowly.

Subscribe to this site's feed.

Contact

Adam Kalsey

Mobile: 916.600.2497

Email: adam AT kalsey.com

Twitter, etc: akalsey

Resume

PGP Key

©1999-2019 Adam Kalsey.