top of page
Search

Building a technology conference session: The Title and Abstract

  • Ben Watt
  • 4 hours ago
  • 2 min read

If you are planning to do a session at a technolgy conference or user group, then I'd like to help you write the title and session abstract in a way that attracts selection from the event co-ordinators and attendance from conferences delegates.


I've enlisted some thoughts from a few close friends & seasoned speakers too, thanks to Alex, Andrew and Bob.


ree

Your session title


Conference delegates will read your session title and likely choose from there. What should you put?


The title is your hook, and my thoughts are to include three things:

  • Target audience

  • Main topic/focal point

  • Value propsition


I've seen people lean towards funny titles, which might make you smile but it can affect attendance. Conference delgates are there to learn, not attend comedy hour - that's for post-conference get togethers!


Yes:


"Beginners guide to DAX Studio for optimising your semantic model"

  • Target Audience: Beginners

  • Focal Point: DAX Studio

  • Value Propsition: optimising your semantic model


No:


"I can't get no DAX-isfaction"

This title tries to be funny, but it loses the plot on why I would attend.


Alex Whittles says:

Resist trying to be clever or funny with titles! Attendees skim hundreds of sessions on the agenda, so your title must instantly communicate what the session is about and who it’s for. If that’s not obvious from the title alone, many people won’t bother reading the abstract, meaning fewer will show up.

Your session abstract


The abstract should bring the delegate through the contents of our session, so they know what key points they'll hear. It's almost like a click-down on the session agenda, but shared in a way they know what they are going to experience.


Andrew Pruski says:

I really like abstracts that detail a problem and how the topic discussed can overcome it. Also a big fan of demos, what's being shown and why...aka show, don't tell.

Bob Duffy says:

Start with Problem. Eg You have private vlans and Infosec team will not allow public connections, Say what the session delivers (ideally the 3 point rule). Connect with the audience with statement like “You are X”, “For Data Engineers/Analysts/Architects”. Close with the outcome

All of my speaking peers say it's OK to run your abtract through your favourite AI tool too, but make sure you tailor the outcome to be in your voice.


Some background


Around the world there are many conferences that are run by community leaders or tech companies. My experience is generally in Microsoft Data Platform events, of which there are many to choose from. I have seen the number of speakers at those conferences evolve and grow as new speakers start stepping up, and some step aside. Recently, I've helped a number of people break into speaking, and after repeating some parts I thought I'd share best practices on building a session and writing the title and session summary, with some values input from fellow speakers.


With thanks


Many thanks to my good friends and speaking peers who contributed, you can hear more from them here:


 
 
 
bottom of page