The problem with the PASS Summit session submissions process is that people don’t know why they’re rejected.

So say we all.

Speaking at PASS

I say with confidence “so say we all”, because of a massive Twitter conversation this morning on the topic. If you’re not familiar with it, the general process for a speaker wanting to speak at PASS is:

Think up a great session. Write an abstract for the session. Present the session several times – at user groups, webinars, SQL Saturdays, to your husband/wife, to your dog, etc. Realize that the PASS Summit call for speakers ends, like, tomorrow. Spend approximately 17 hours polishing the abstract. Submit the abstract. Get an email 3 months later – either an acceptance email, or a rejection email with no or little reason for the rejection.

Usually, step 7 is a rejection email. Most of us understand that. After all, this year there are over 600 submissions, and far fewer sessions that can actually happen in a week. Speakers understand supply and demand.

And I think if this were a “normal” conference, most of us would be mostly okay with rejection without reasons. They didn’t want it, it’s a big con, whaddyagonna do?

PASS’ Purpose

But PASS is the Professional Association for SQL Server…it’s a community group. The whole point of the organization is to help SQL Server professionals grow in knowledge and career. Part of that growth, for speakers, is becoming better speakers. (We have said many times that you don’t know a thing until you teach it.) Part of becoming better speakers – part of knowing you’re advancing, maybe getting into the big leagues – is speaking at the big annual conference, the PASS Summit.

If you never get to speak there, clearly you’re doing something wrong. A vague abstract, too many typos, too popular a subject to break into. No problem! We’re ambitious, we speakers! We’ll work on that! Get a spell checker! Choose a better topic, or a better angle! Something!

But we don’t know what we’re doing wrong. We don’t know how we’ve failed the selection committee.

Tell Me Why You Broke Up With Me, or I’ll Keep Calling and Texting and IMing and…

The selection committees are volunteers. We get that there’s only so much you can demand of volunteers. “Work through these 120 abstracts, pick the best ones, rate them, formulate a distinct and clear reason for rejection for the others (no less than 150 words!), do my laundry and taxes, pick up the dog from the vet…” Of course you can demand too much of volunteers!

This isn’t too much. Ask the people who are volunteering. Many of them are speakers, too, and also long to have a reason for their rejected sessions. Find a middle ground…instead of “Too many selections submitted for this track” – I’m sorry, but great green jumping DUH there were too many sessions! I hope to god you didn’t reject me while leaving the track underpopulated!!

Ahem, I say, “Too many selections” is a complete non-reason. It’s an insult. “I couldn’t keep dating you because I don’t feel right dating you AND Bob at the same time, Mike!” Terrible, terrible reason. A non reason.

Tell me something useful, even if it’s really short. Examples:

Your session barely lost out. Try a different spin on this topic.

Title way too cutesy; tell what the session is about.

Misspellings galore, man.

I have no idea what this session is supposed to be about.

You’ve presented this exact thing at the last 3 Summits; submit something new.

Microsoft doesn’t even support this software any more.

Microsoft doesn’t MAKE this software.

You get the idea. Of course people will rant and argue, because people do. That’s the nature of rejection. But give us a reason we can work on, okay?

Commenters! Assemble!

Edit: See the comment below from a PASS program manager. Looks like they’re trying to remedy this. Honestly though, I expect this first pass might be a little bit light / weak.

Happy days,

Jen McCown

www.MidnightDBA.com/Jen