I am constantly awed and humbled by the hard work, dedication, generosity, and selflessness of the people I am surrounded with. The SQL Server community is no exception. A few months ago, I had an idea to bring a SQL Saturday to Wisconsin. Two days ago, that idea became reality with SQL Saturday #118 Wisconsin. It exceeded all my expectations. I did not do it alone, though.
Thank you is not big enough for Ted Krueger (b | t), Gina Meronek (t), Leonard Murphy (t), Tim Benninghoff (t), Tony Sebion (t), Matt Cherwin (t), and Steve Novoselac (b | t). Without you, this wouldn’t have happened.
Thank you to the staff and students at MATC. They helped reserve rooms, put out tables, put up signs, monitored rooms, and fed us well. It was a pleasure to work with them, and I would do it again.
Thank you to the 33 speakers that came from (at my last count) 12 states to present for us. They did this as volunteers – all I could give them was a freshly-washed shirt and a good dinner on Friday night. All the presentations went smoothly and got great reviews.
Thank you to the small army of volunteers. They stuffed bags for attendees, checked people in at registration, collected tickets at lunch, helped speakers as room monitors, and carried boxes for me. They rocked the event.
Thank you to the 226 other attendees at the event. Two hundred and twenty-six. I nearly had to pick myself up off the floor when I saw that number at the end of the day. That's a lot of people getting free training and networking.
Last but certainly not least, thank you a hundred times over to our great sponsors. We would not have been able to hold this event without the support of Red Gate, Tushaus, Confio, Idera, Rubix Consulting, PASS, CUNA Mutual Group, Trek Bikes, Melissa Data, and blog sponsors. These companies help us not only in our day-to-day jobs, but extend that to community events like SQL Saturdays. Please thank them, and give them your business. (Their software and services will make your life easier.)
Are you thinking about organizing a SQL Saturday? Do you want some advice? Here are my two cents ten dollars.
First, establish your posse. One person cannot do a SQL Saturday single-handedly (and do it well). You will need people to help make phone calls and send emails. You will need people with other ideas and contacts to extend your reach. You will need to sleep, and to see your family, and to do your job. Start a posse.
Then, establish regular planning meetings – they could be in-person, or conference calls. I did not do this early enough, and two months out I started to panic. At the advice of a mentor, I started weekly half-hour conference calls. That made a huge difference. It helps when everyone in your posse knows what is going on.
My super-magic Jes Secret to Success: Organization. The super-magic Secret to Organization: To-Do Lists. I had lists every week of what needed to be done and who was doing it. The week of the event, I created a list of what needed to be brought on Friday and Saturday, and who was bringing it. There was a list of what needed to be done on Friday and Saturday, and who was doing it. Write it down as you think of it. Check it off when it’s done. Keep that as a record. This will make your life easier.
There are two members of your posse that will stand out in the two weeks leading up to your SQL Saturday. These are positions I stress more than anything: someone to organize and wrangle volunteers (Gina), and someone to handle all communications with attendees (Leonard). These are huge tasks. They were done so well I hardly needed to be involved.
There are a few things speakers want to know ahead of time: if there will be a PowerPoint they should use, if there will be speaker shirts they should wear the day of, if and where there will be a speaker dinner, if there will be WiFi in the building, and who in the building to call with tech problems. Save yourself some time and questions, and figure this out in advance.
Make the day smoother on your posse and your speakers by having a volunteer in each room as a room monitor. We had morning and afternoon shifts. These great people handed out evaluation forms, collected them, gave them to the speakers, and made sure everything ran smoothly. It required a few extra people but eliminated a lot of headaches.
As I mentioned above, you need sponsors to make your event happen. Don’t forget to look for local sponsors! You can get them. They will appreciate the exposure. We asked our user group members to ask their employers. We asked local tech recruiting and placement firms. They said “yes”! We equally appreciate the national vendors that supported us, knowing that it is hard for them to spread their marketing dollars to every SQL-related event.
With that in mind, when the day comes, put the sponsors in a high-traffic area. They want to – and deserve to – be visible and accessible to the attendees all day. Remember, their products and services can make your life easier. Tap into that!
How do you know where your sponsors, and your speaker room, and your lunch will be? Review your venue beforehand. Know exactly where you want everything. When I was able to walk into MATC on Friday night and tell the facilities staff exactly where I wanted tables set up, they were happy. We didn’t have to spend an hour hemming and hawing over where things should go. This goes back to my point about being organized.
All day Saturday, I carried my iPad with me. I was able to check the schedule, my email, Twitter, the PASS website,etc. I made notes throughout the day of what to say during closing ceremonies. I was able to network with people instantly. If you have something like this: use it!
In the long run, attendees care less about getting t-shirts and books than high-quality sessions and face time with the speakers and other attendees. Remember this in your planning.
However, if you do decide to have some giveaways, order stuff like shirts or bags at least three weeks before. You will need time to gather copy and logos, get them to your supplier, have them printed, and have them shipped. Do not wait until the last week to do this. You will be stressed and you will likely pay rush charges and upgraded shipping charges. (I’d also like to plug my supplier, 4imprint. They rock. Use them.)
Accept this fact: attendees and even speakers will cancel. It happens. Life happens. When making the schedule, pick 3-5 sessions as alternates. Ask another speaker to cover if needed. I had also made up my mind that if anyone cancelled within three days of the event, that session would be cancelled. I don’t think it’s fair to ask anyone to contribute on that short notice.
On a related note: don’t speak at the event you’re organizing. I thought I could. I did, but I didn’t prepare well enough beforehand, and I didn’t give the presentation 100%. As soon as I was done speaking, I went to the speaker room, curled up on the floor, and passed out. It was that exhausting. I had to remind myself I am not Wonder Woman, no matter how much I want to be.
The only other thing I would do over would be to have an opening keynote, even if it was only 15 minutes long, to let people know what was going on. Close to 75% of our attendees were at their first SQL Saturday. I wish I could have explained how the day was going to run, what the Cows of a Spot tables at lunch were for, to make sure they stopped by the sponsor tables, and to remind them to network. Next time, I’ll add this in.
Last but not least, put your mark on the event. This is your chance to show off your user group, your city, your state, and your people. I tried to do this by washing the speaker shirts, having Wisconsin brats for lunch, and re-naming “Birds of a Feather” tables to “Cows of a Spot” tables. PASS has provided a great template for SQL Saturday. Embrace it, then make it yours. Have fun with it!
Most of all, enjoy your day. You’re bringing high-quality, free training and networking to people. They will appreciate it, learn from it, and spread the word. Enjoy it!
No cows were tipped in the making of this SQL Saturday. That I am aware of.