I readily admit when I see a comment card, there’s a 99.9999% chance I’m not filling it out. When I buy a product on Amazon.com or another site, I don’t go back and post a review unless I feel a very compelling reason to do so (read: never). And it’s rare that I will give feedback to a restaurant other than telling the server I enjoyed my food.
Perhaps it’s paradoxical, but I feel a strong obligation to provide feedback to speakers at SQL events. Here’s why.
In most areas of life, we vote with purchasing power. If a restaurant has good food and service, I buy again. If I really like my Panasonic TV, I’ll strongly consider another Panasonic TV when it needs to be replaced. SQL presentations are different because:
- In many cases, I paid nothing to attend except the cost of getting there. If I’m lucky, the conferences with fees were paid by my employer.
- Even if one or two speakers don’t meet my expectations, I’m probably going to attend the event again.
- My decision to skip an event by a particular speaker is only loosely correlated to my opinion of their session. For example, I have seen Steve Jones’ Modern Resume session and I thought I was great. Would I attend it again? Probably not anytime soon, but only because I want to hear something new or different. It’s the same reason I won’t see Brian Regan (my favorite comedian) more than once every few years. The jokes are still funny, but I’ve heard them already. I’ll go see him again when he’s doing new material.
Therefore, the feedback we’re used to giving automatically — keep buying or quit buying — doesn’t apply well, if at all. As attendees, what are our alternatives for giving feedback? We could instead choose to share our thoughts face-to-face (tell the speaker we liked their talk), praise or flame the speaker/event on Twitter either in real-time or afterward, or we can blog about it. Finally, we can give ratings and comments on feedback forms. Feedback forms are the most common way for event organizers and speakers to gather feedback on their performance.
How Helpful Is Feedback? It Depends.
The typical SQL user group and SQL Saturday feedback forms have a series of “rate from 1-5” questions, along with some open-ended questions intended to solicit comments. Switching perspectives to that of the speaker, here’s how I value feedback on these forms (ranked from most to least valuable):
- Useful comments, positive or negative.
Example: “You lost me when you talked about the execution log. Too high-level compared to the rest of the talk.”
Delightful. The kind of comment I can use to improve my presentation. - Feel-good comments.
Example: “Really enjoyed it!”
It makes me happy to read these even if there’s nothing in them to help me get better. - Feel-bad comments.
Example: “Didn’t cover what I expected.”
While this is not explicit, at least it makes me look back at my abstract to make sure I kept my promise about what I would say and what I wouldn’t. - Good numeric feedback but no comments. Even though I know it’s nearly meaningless, it makes me smile to see 4/5 and 5/5. At least I know I didn’t disappoint these people.
- No feedback submitted. I put in 40-60 hours’ off-work time — time I could be playing with my kids, sleeping, watching my PASS Summit DVD’s, gardening, learning to play piano, anything — to build, rehearse, and refine this presentation. You come and absorb it at no cost. I ask for 1/1800th of that time back for your thoughts and some light stenography so I can make my next presentation to you better. You decline. Then you leave. Yes, that seems fair.
- Bad numeric feedback but no comments. This is in no way helpful and it makes me look bad to those who would use these ratings to quantify the value of my session. If you’re going to jab my overall score without telling me why, do us both a favor: Don’t fill out the evaluation at all.
- Kick to the crotch but no comments. I have yet to offend someone so gravely that they assault me, but I’ll throw it out there anyway: if you’re going to kick my bag in, TELL ME WHY! (That way, my restraining order against you is much more likely to be granted.)
When I deliver a presentation, I’m dying to get feedback that falls under items 1 and 2. Feedback for items 3-4 are okay. Anything else is not going to help either party.
Why I’m Ranting About Feedback
It wasn’t the blog posts by Aaron Bertrand, Allan Hirt, or Mike Walsh that got me stewing about poor feedback. It was Scot Reagin’s presentation to the Denver SQL Users Group last month that got me fired up. All I will say on this is that there were at least thirty people in attendance that night, and Scot presented on MDX – a subject that is not easily grasped by beginners. Here is what little feedback Scot received in return for a first-class session.
“You can go about your business. Move along.”
Having met enough other presenters, I can say with confidence that we speak because we love to. We love sharing what we know and helping other DBA’s, developers, and architects do their jobs better. We’re passionate about SQL Server and the SQL community. And in case I haven’t made it obvious, we’re passionate about improving what we deliver to you.
Whether or not we get good feedback in return, we’ll keep on teaching. Hopefully, you’ll take a few minutes to teach us a little something too.