If you have donated to our SQLRun fund raising for the Portland, OR-based Ray of Hope Charity, we will put our thanks to you on our blog. First, we’re going to recognize you by first name or company name right on the front page of our blog:
We will also give you a Tweet shout out of thanks to our 4,000 followers.
All those who donate will also be listed on our Thank You Blog Roll at the top of our blog page:
If you donate $100 or more, you can have your own image and text banner displayed in the same area as the thank you banner on the home page — and this can link to your blog, website, or social media page. Donate $500 or more to our Ray of Hope campaign and you’ll get your very own sponsored blog post and all of the above. We will include any company matching donations in your total.
Of course, we reserve the right to post only content that is professional and in the right spirit of our fundraising mission.
Finally, if you donated anonymously, we will not be listing your information anywhere unless you ask us to.
Thanks to all who have already donated and to those of you who will. We think Ray of Hope is wonderful charity.
I’ve uploaded a much more detailed checklist for what to do when you inherit a data model from someone else.
What would you add to it?
Two of my posts are now up over on Dataversity.net, a portal of all things data for data professionals.
The first, now with images working correctly, is Hiring Data Professionals: Mason Dixon Lines and Zombies in Your Job Postings. In that post I reflect on some of the craziness in job postings I’ve seen over the last few months.
In my most recent post, Normalization Myths that Really Make Me Crazy – Introduction to a Rant, I start a series on normalization myths. I expect this series to provide hours of new content for my Contentious Issues presentation. In the introduction I talk about why a series and the emotions people feel about normalization. Please stop by and leave your thoughts there.
I’ll be writing more than a dozen posts for Dataversity this year and I appreciate your reading my posts there as well as those here at InfoAdvisors.
For those of you who read our blog and don’t frequent SQL Server community events, you might find this post a bit surprising. I found similar posts odd when I first came across them, but now I understand the role they play in the SQL Speaker community.
Speakers at SQLPASS and related events often post the evaluation results they received, good or bad, along with the presenter’s analysis of how the presentation went and how the evaluations cause them to enhance their future presentations. I’ve learned a lot from reading how other speakers have responded to their evaluation data, so I’m going to start sharing mine.
SQLRally was held just a few weeks ago in Orlando, which fit perfectly into my schedule of waiting around for Endeavour to lift off. I had already been scheduled to speak, so I didn’t have to travel far from Cocoa Beach to Orlando to attend. My presentation was a Deep Dive, meaning I had a 90 minute time slot to present. I had submitted a couple of proposals, but the one that was voted on by the SQL community was my professional development topic, Career Success in the Data Profession During Turbulent Times. I forgot to count how many people attended, but I’m pretty sure there were more than 40 people, probably more. Nineteen people completed and turned in evaluations for the presentation, which I think is about the expected number.
The data (scale of 1-5, with 5 being best):
- Overall Average: 4.754
- Lowest Evaluation: 3.5, but evaluator gave no comments, so I’m not sure why he or she felt that way or what I could do to make the attendee happier.
- Highest Evaluation: 5.0 (12 people gave this score)
The questions asked on the evaluation and my average for each:
- How would you rate the Speaker’s ability to convey information and control the presentation? 4.737
- How would you rate the Speaker’s knowledge of the subject? 4.895
- How would you rate the accuracy of the session title and description to the actual session? 4.632
- How would you rate the speaker’s use of the allocated time to cover the topic/session? 4.684
- How would you rate your ability to follow along with the speaker’s examples/demonstrations? 4.842
- Please rate the practicality of the information presented. 4.737
I’m happy with those results. The lowest one, about the session title, is one that I struggle with. For technical presentations, I find titles and abstracts can be really clear. For professional development, I think that it’s harder to get a clear title that covers all the nuances of "how to do something better, regardless of what its". So I work hard on the abstract. I have a slide with the same title of each of the points in the abstract to make sure there’s a good link to help people understand what we will be talking about. A 4.6 is still good, but I’ll work on making that better.
Time allocation is tough. I make ending on time a very high priority. It was funny that the speaker before me went more than 20 minutes over in his session. I ended on time. We covered all the material and had a huge amount of audience discussion, which is how I rate the success of my sessions. That’s just my style. I’m not much of a lecturer.
Since this presentation focused somewhat on social media and getting others to market for you, I was glad that I didn’t have people feeling that was too much non-SQL content. It’s always a risk when giving professional development topics at technical conferences.
The comments evaluators gave were very encouraging, too.
Great Structured vs. unstructured presentation. Most audience involvement in a session I’ve seen here.
Like I said, that’s my style of presentation. So it works well people audience members enjoy that. I know some people don’t. I have had evaluations that complained about the time wasted with audience people asking questions or offering different opinions. Sure, sometimes presentations get derailed by those things, but I allocate a significant portion of my presentation time for these discussions. I’ve always wondered how to set people’s expectations about that.
Excellent slides. Focus on topical ideas, not text in bullets. Kept focus on stories. Great presentation.
Also good to hear. I’ve had people complain in the past that they don’t like my Zen-like simple slides; they want lots of text to use as a reference later. I’ve considered adding notes to my slides in PowerPoint to meet those people’s needs.
She explained everything well.
I’m glad. I was glad I had 90 minutes so that I could spend extra time explaining the social networks and what I meant by "networking".
Got off topic for a while at the beginning.
I’m not sure which part that was. There were some discussions that went on for a while I and I had to move on to other topics. But I was happy to see such an engaged audience. I will work harder at focus.
Discussed a lot of how to hire instead of how to position yourself for advancing your career.
That is excellent feedback. I did talk a lot about hiring people, as did some audience members. I can’t tell many stories about advancing through employment opportunities, though, because I’m in the services industries and have been my own boss for more than 15 years. My intent on telling interviewer stories was to show how hard it is to hire someone if they can’t explain well what they know and what they do. Next time I’ll work harder at making that distinction.
Knowledge is power. Know your profession’s mandate.
I like this statement, but it was giving as a comment under "what could the speaker do to improve future presentations" and I don’t know what it means. If you gave this comment and want to explain it a bit more, I’d love to hear more.
Not enough of this is being discussed in "DBA-dom"
I think it is great that SQLPASS and SQLRally have professional development tracks, so some of it is being talked about at these events. Many user group and SQL Saturday organizers are worried about putting professional development topics on their schedules, since some members don’t like non-technical presentations. If you do, you should talk to your local organizers to tell them you think it is important.
As with other presenters, Karen seems to be the leader in data architecting and IT resource field. Kudos.
Great natural speaker.
Could discuss all day, very thought provoking.
There’s a tremendous demand and a need or this. There’s a business here. Most valuable presentation of SQLRally.
Those makes me smile. It’s always nice to get this sort of feedback. Share some love if you enjoyed the presentation you spent time at.
So thank you for all of you who took the time to share your thoughts about the presentation. Speakers crave this sort of feedback. As other speakers have blogged, speakers have traveled away from the families, taken days to prepare for their presentations, rehearsed them, fretted about them, planned for them, and generally spent a great deal of time trying to make that 60-90 minutes the best session of your day. Do them a favour by spending 5 minutes filling out the evaluations. And please do the hard part: If you didn’t rate them a 5, tell them why. We really do want to know.
Jen McCown (blog | twitter) has called for a Un-SQL Friday blog post on Speaker Lessons Learned. Since I speak frequently, I thought I’d whip up a quick post to cover some of my tips on making a presentation look it it was all planned. I’ve been giving presentations for so long I can’t even tie these recommendations to any one event that caused me to adopt these practices. However, they are all most likely due to either a failure on my part or a failure I’ve witnessed while attending an event.
I once co-presented with someone who showed up to do a half-day training event and he didn’t bring his own slides, nor handouts, nor any contingencies. I had a copy of his slides, just because I wanted to see them before they were presented. The audience wanted to …well, let’s just say they didn’t feel they got the value they paid for. You don’t want to be that guy. You want to come across as being all in control. Even if on the inside you are quaking with fear.
Contingencies Will Make You Look Super Sauvé
I’m big on having duplicates, backups and just-in-case options. Some people, like the one I live with, think that I overplan for something to go wrong. Having options in place makes me a more confident speaker. I can sleep better the night before. I am more relaxed when I enter the room. So overall even if I never make use of these, it makes me better at what I do. This may seem excessive, but they are all pretty much part of my process and each takes only a minute or two to do. The benefit exceeds the cost by a huge amount.
- Don’t just have a backup; have a backup farm of backups. For every item involved in my presentation (slides, demos, code, databases, data, etc.) I have many copies stashed all over the place. These backups or copies are both at the component level and as an entire package. Here are the likely places I’ve stored these files:
- Dropbox: Dropbox (affiliate link) is a free service that will store your files on the internet *and* on your local machine and magically keep them all in sync. You can purchase more space if you need it, but the free space will hold many presentations and scripts. If you use my affiliate link above, we both get extra free space, too. I have Dropbox installed on my phone, iPad, netbook, laptops and desktops. My files are just always there. Note, your organization may have policies against storing company data on such services, so check first.
- Thumb drive/USB Stick: I make sure that all my materials are also on a USB storage device, too, just in case there is no connectivity in that hotel basement meeting room. This way, if my laptop dies or it won’t cooperate with the data projector, I can borrow someone else’s machine to present with, at least the slides. Did I tell you that I have a Bottle Opener USB drive from SQLSentry? That’s two contingencies in one!
- Phone/iPad: I also put the slides on my Phone or Tablet in case I need to e-mail them to someone to print handouts or to possibly even use as presentation device. My iPad has a dongle so that I can use it to present the slides. That’s another two contingencies in one.
- Server/Desktop: If there is connectivity, I can also remote desktop into a machine back at my office to run demos or to do the presentation completely from the office machine. Since I usually develop my materials on my desktop so no extra work to have it available.
- Email: I sometimes even e-mail myself a copy of all the materials so that they are there in my inbox, just in case.
- Have a plan for when other technology fails you. It’s not just your slides that can wrong.
- Projector: What will you do if the data projector isn’t working? Or the projector is very dim. Or very old and doesn’t work well? What if the person who was supposed to bring it doesn’t show up? This has happened to me a lot over the years, more than is acceptable. So I bring one printout of my slides with me to the presentation. If the projector isn’t there or is not cooperating, I ask the organizers if they want to make copies for handouts. Having a printed copy ready makes that process easier to do. This can also help mitigate missing screens. Having handouts instead of a projector isn’t perfect, but it’s better than nothing at all. Some people go as far as travelling with their own projector.
- Room set up: What would you do if your presentation counted on flip charts or whiteboards and they weren’t there? What if the room you are presenting in is very long and narrow and 3/4 of the audience can’t really see your slides? I arrive at my presentations at least an hour a head of time to check out the room and make plans for what to do if the room set up is not what I expected. This also gives me time to request flip charts or other items. In some extreme cases, I’ve been able to arrange a different room.
- Power problems: What if the outlet is 20 feet from where your laptop is supposed to be and there are no extension cords? Is your laptop fully charged? Will it make it through your whole presentation? I travel with an extension cord but sometimes a hotel doesn’t allow them or has anti-theft plugs to keep people from "stealing power". Have I told you how unhappy this makes me when I see these special plugs in public places? Sure there are designed for applications where you don’t want a plug to be accidentally ripped out, but when the entire conference center has these, you know they are there to protect the electricity, not the device that is plugged in.
- Anything else: There are so many other things that can go wrong with the facilities. Having a generic "what if I had to stand up in front of people and just talk for 90 minutes" plan is going to go a long way in dealing with all kinds of things the universe might throw at you. Sure you might not be able to do demos and your presentation might not be as strong as if everything went perfectly. You can still deliver a ton of value just by interacting with people during that 60-90 minutes. Don’t underestimate the value that you personally add to the presentation.
- Don’t panic. I would guess that every single person in your audience has had something go wrong during a meeting or presentation, so they will have empathy for you and the situation you are in. If you panic, though, you won’t be able to recover well and make a smooth transition into delivering value given the circumstance.
- The audience wants you to win, really. They might not be happy your laptop died or that the projector doesn’t work, but they want you to keep your focus on delivering the knowledge you came to share. Sure, there might be a couple of sadists out there who enjoy it when speakers fail, but even they don’t want to sit through an hour and half of flailing arms and incoherent utterances. So have your contingencies and plans in place. Make that smooth, suave segue into your other plan and keep going.
- Don’t keep apologizing. Yes, you feel bad that things are going to all heck. Yes, you should apologize. But don’t keep saying I’m sorry, I’m so sorry. Gosh, I’m sorry… That’s just focusing on the fact that things aren’t going as planned. Apologize, then move to your Plan B (or C or D) and you’ll look calm, cool and collected. In other words, act like a professional.
- Don’t blame anyone. Later, if you want to conduct a forensic investigation to find out who did it and have them prosecuted, do it. Don’t stand at the front of the room, blaming the hotel, the staff, the volunteers, your mother and your dog. Even if they all did get together and sabotage your event. No one in the audience cares why it happened. They just want you to fix it. By focusing on blame, you haven’t made the audience have any greater respect for you.
- Don’t quit. Whether or not you flew across the globe or just walked down the hallway to make your presentation, the audience carved time in their day to hear what you had to say. Say it. Work really hard to meet the same objectives that you set out to do. Deliver value. I’ve seen speakers cancel their presentation in front of 200 people because they didn’t have a backup of their slides. They had a complete fail instead of a partial win. If you are so dependent on your slides that you can’t deliver any value at all on your own, maybe you should just email your slides to everyone and save everyone a bunch of time.
Finally, I highly recommend you find a copy of Lily Walter’s What to Say When You are Dying on the Platform. Walters goes over a zillion things that could go wrong and how to avoid them…as well as suggesting snarky responses that diffuse the tension and get you moving forward again. This was written in 1995, so it might not cover some of the current types of technology failures, but you’d have the right sort of responses to deal with minor and major issues during your presentation.
I guess this whole post comes down to being prepared and having confidence when something you wanted to go right didn’t. Have lots of backups, have a plan, and don’t panic. That’s all advice I’ve paid for, so you can have it for free.
Break a leg!
Subscribe via E-mail
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- Joey D'Antoni on Strutting: We all Know When You are Doing It. So Stop.
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- Thomas LaRock on Strutting: We all Know When You are Doing It. So Stop.
- Karen Lopez on Strutting: We all Know When You are Doing It. So Stop.
- May 2013 (5)
- April 2013 (5)
- March 2013 (4)
- February 2013 (7)
- January 2013 (12)
- December 2012 (2)
- November 2012 (3)
- October 2012 (3)
- September 2012 (13)
- August 2012 (5)
- July 2012 (17)
- June 2012 (2)
- May 2012 (4)
- April 2012 (4)
- March 2012 (8)
- February 2012 (11)
- January 2012 (3)
- December 2011 (10)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (9)
- July 2011 (5)
- June 2011 (5)
- May 2011 (5)
- April 2011 (9)
- March 2011 (4)
- February 2011 (9)
- January 2011 (8)
- December 2010 (15)
- November 2010 (27)
- September 2010 (2)
- August 2010 (1)
- July 2010 (4)