The recent trend towards online voting to select presentations for events at SQL Server conferences got me thinking: this is a great opportunity to look at how people vote, and consider what this means about presentation titles and abstracts.
Let’s Admit It: People Don’t Read Abstracts
When there’s a large slate of sessions to choose between and the abstracts aren’t easy to see, people definitely don’t read abstracts.
This isn’t too different from physical conferences. When you’re looking at your program, you may glance at the abstracts, but most of what you check out is the title and sessions. In both cases, you’re busy doing other things and you have a lot of information to absorb– you make the best choice you can based on your limited, valuable time.
The Decision Tree
The decision tree for choosing a session starts out pretty simple.
Most people have “must-see” type choices, either based on really wanting to see the presenter, or having a real need for the session topic. We’ve all had the feeling of, “OH, I could REALLY use that session!” because it’s applicable to some specific problem in our lives.
Based on my life experience (including surviving middle school, watching elections, and running for committees), the decision tree starts like this:
- Is the presenter someone you’ve got a nerd crush on? If so: vote
- Otherwise, is the session something you really need? If so: vote
These are both very valid reasons to vote for sessions. People who are well known for giving great presentations definitely deserve to get votes for that track record. We have a lot of superstars, which is fantastic!
But for everything that doesn’t fall into these category, things get complicated. And that’s for most sessions.
How I’ve Been Choosing Titles
I like to choose session titles that are fun and quirky. That’s just the type of session I’d like to go see– something a little out of the ordinary.
While I care about the titles a lot, and I spend a lot of time on them, I haven’t had many other criteria other than “quirky” and “amusing.”
What I’m Changing, and Why
My criteria aren’t enough. I need to make my sessions appeal to more people other than me. After all, my presentations aren’t for me.
While my titles and abstracts should still be in my own voice, I need to add more information to them to help people understand more about what I want to give them.
From my highly unscientific observations, here are some guidelines:
- People like Tips and Tricks.
- People like to learn a finite number of things.
- People like practical advice they can apply quickly.
- People like new features.
- People like to have difficult to explain topics explained, but they need to be broad (performance, internals, memory).
- People like T-SQL. It’s a very common tool for everyone, we use it frequently, and we all like a good session to help us think about it differently.
When I think about how I make my own choices, this does make sense. I like all of these things, too.
This doesn’t mean my next session will be titled “The Top 10 Tips and Tricks for SQL Server Performance using T-SQL and New Features!!!111!!!1!”
I may or may not use a number in presentation titles. But I’m going to consider them.
But, when writing titles (and abstracts, although I am convinced people don’t read them), I will ask myself:
- Does this show I will demonstrate something practical and useful?
- Does this help people understand why it is applicable and/or useful and interesting to know?
- Is there a way I can make this more practical, while still having it in my own voice?
And I may sometimes go with a title that I feel is a little boring, if it’s easier to understand.
Am I Selling Out?
I don’t think so. But let me know. 🙂