SQL Saturday Cleveland 2018: Feedback Stack

My congratulations to the team of SQL Saturday Cleveland, for an outstanding event in 2018. You all put on a consistently well-run event, and I’m proud to be a part of it. I’m looking forward to submitting again in 2019. :-)

I wanted to make a post regarding the feedback I received from my session. I had somewhere between 30 – 40 people in my room, and the engagement was great. Thanks to everyone who came up to talk to me after my session. 19 feedback forms were received from the attendees.  Of those, 14 of which were all positive, for which I thank you very much. It’s good to know that what I’m providing is something people will find useful.

I’m also extremely grateful for the 4 negative feedback forms I received. I want to take a moment to address those specifically. Here were the negative comments I received under the category, “What could the speaker do differently to improve?”

“Slow down a little.” – Yep. I am in complete agreement with you on this one. I have a tendency to talk quickly when I get excited about something, or simply have had too much caffeine. Valid feedback, and duly noted. I will work on this.

“Make slides + scripts available before class begins.” – This is a hard one for me, because I have a tendency to modify the slides and scripts due to feedback I receive during the session. If someone points something out during the session that would require a correction on my part. I want to do that before posting the material. Making the materials available beforehand defeats that purpose. I could always issue an update, sure, but I’m not confident most people would bother downloading it. I am open to suggestions on this.

“More focus on diagnosis, remove inclusive vs. exclusive section, typo on DMV slide “individual””.  – Thanks for all that!  You’ll be happy to know that the typo was fixed before the materials were uploaded, so the available slides are correct. I’d be interested to hear more about why you think I should remove the inclusive vs. exclusive filter section, though. Lucky for me, you were kind enough to let me know who you are, so I will reach out to you individually. :-)

Here’s a comment from the “Did you learn what you expected to learn?” question: “No. Way over my head, was expecting use of EX.Events GUI.”  I’m sorry you didn’t get what you expected out of my session. However, I did explain my reasons for avoiding the GUI. You won’t be able to use any of the automation tactics or scrips I showed with the GUI. I’m not against using the GUI, but I choose not to so that I can save my scripts and automate them. I would suggest playing around with the demo scripts a bit to see if they make sense, and if not – contact me. I’ll see if I can help you out.

Astute readers, I am sure, will note that 14 positive and 4 negative feedback forms does not add up to 19 total. I have one last comment to post, from my favorite feedback form I received, and I think you’ll agree this one defies categorization. I love it.

What could the speaker do differently to improve? “Expand the universal constant governing relative time, and do a 4-day seminar in 45 minutes.”

I’m pretty sure I have a PowerShell script for that. :-)

Thanks for reading.


2 thoughts on “SQL Saturday Cleveland 2018: Feedback Stack

  1. mbourgon February 7, 2018 / 9:18 pm

    Nice post, David. I’ll have to make it up there for the SQLSat. Alas, I’m in Texas, and the drive is…formidable.

    As a presenter, and “that guy” who harps on it: make everything available beforehand. Here’s several reasons:
    1) if I’m on the fence as to which session to see, I can look at the slide deck/examples and decide if it’s an area of interest, or not. “Too basic” “too advanced” “oh, he’s covering this thing I already do”. You wind up with a more interested audience.
    2) I’m still waiting for slide decks that speakers at PASS 2014 promised they’d put up. Life gets in the way, but this way I get _something_.
    3) if I’m planning on discussing, I can have appropriate questions. If I go in cold, then I’m at the mercy of what I learn during the session, which may not fit with my questions. Basically, if I know you’re not going to cover part of the topic, I can ask if you if you could set aside some time for it. It also means I’m not asking questions ahead of that part, if you do plan on it.

    in your specific case, the guy who was overwhelmed could have known ahead of time. The guy who wanted more diagnosis would have been able to ask for more of it at the beginning, not rushing at the end.

    Hope this helps.


    • dmmaxwell February 8, 2018 / 9:14 am

      Thanks – that’s really good feedback. :-)


Please Comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.