Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

You should speak at conferences. Yes, you.

Freshness Warning
This blog post is over 8 years old. It's possible that the information you read below isn't current and the links no longer work.

The speakers at too many conferences are the usual suspects, speaking over and over again. Local tech user groups and meetups are starving for content, leading to much of the meetings being dominated by companies from outside the group with an agenda that doesn’t always meet the need of your community.

Developers, you should give talks at conferences and your local meetups. Besides helping out your community, you’ll improve your own career. People who are outgoing, who speak up, who are visible, tend to be better connected within their company and their community. This leads to new opportunities. By speaking at events, you’ll gain confidence and find it becomes easier to be a leader instead of a follower. You’ll raise your visibility in your industry, your community, and your company.

You might think it’s hard to get a talk accepted. Many conferences have trouble filling all their speaking slots. Sure, the keynotes are usually full, and often with speakers who are paid to be there. But breakout sessions, technical trainings, lightning talks, Birds of a Feather, and other sessions are often available at conferences. Discussion panels often have spots available for panelists.

Your local technology meetup probably has trouble finding regular speakers. Think of the meetings you’ve attended where the speaker wasn’t known until the last minute, or that consisted of a free-for-all discussion. These were probably meetings where the organizers were scrambling for a speaker. They’d love it if you offered up a talk.

Have a Barcamp in your area? The talks there are open to anyone. Just put your name on the board and give a talk. At these, you could offer to lead a discussion, giving a short 5 minute talk, then using the rest of the time to discuss your theme among the participants.

Perhaps you’re afraid you have nothing to say? You certainly know something that not everyone else does. Your talk doesn’t need to be a comprehensive encyclopedia of all knowledge on your subject. For a subject that’s likely to be new to your audience, an overview is better. Give them enough information to decide if they want to learn more on their own.

Or you have an opinion, perhaps one that you’ve been giving to your friends and colleagues. Surely you can speak for 30 minutes about something you’re passionate about. At one conference, I recently said that “RCS is solving last decade’s communications problems.” The quote got a bit of attention, so my next talk was focused on why I believe that and what the industry needs to do in order to change.

Where to start? The easiest place is your local community. Those meetups and local user groups will be happy to have you speak. Ask any organizer and you’ll find that they really are struggling for content. That’s one reason your community is a great place to start: they’ll welcome you with open arms.

The other reason is they’re friendly. It’s a smaller, controlled audience. These are your people. You’ve probably had dinner or drinks with some of them. They want you to succeed. They’ll overlook your faults. If you have stage fright or fear you won’t be able to get your point across, or just don’t know how to go about preparing a talk, this is the right group of people to try in front of.

Go out, give a talk. Improve yourself, your community, and your future career.

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

December 8, 2015 7:05 AM

I maintain that 90% of being smart is just being about to communicate ideas clearly and intelligently. Public speaking has been the #1 way I've gotten better at that.

This discussion has been closed.

Recently Written

Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2024 Adam Kalsey.