PASS Summit — Nothing to see here

I haven’t written anything in a while about my PASS Summit prep. To be quite honest, I have nothing to report. I’ve been busy with several other things (among other things, I’ll make a trip to New York City before I head to Seattle), and I have plenty of things to keep me distracted (some of it in a good way).

For those of you new to my ‘blog (the rest of you can skip this paragraph), here’s a quick summary to get you caught up: this past July, I learned that I was chosen to speak at PASS Summit! If you’re a data professional, PASS Summit is a huge deal. If you’re familiar with SQL Saturday, I’ve heard it described as “the Super Bowl of SQL Saturdays” and “SQL Saturday on steroids.” Being selected to speak at PASS Summit is an enormous honor for me, as well as being a great boost for my career! (I should also mention that not only is this my first time being selected to speak at PASS Summit, this is also my first time attending, as well!)

I did get feedback about my presentation slides. I’m not sure whether or not I’m allowed to talk about that (it’s nothing bad), so for now, I’ll leave it at that. I also asked about luggage storage arrangements for the last day, after American Airlines pulled a fast one on me and changed my flight schedule. (Tip: I can store my luggage at PASS Summit. And from now on, I am avoiding American Airlines if at all possible.)

I’ve been poking around the Summit website for the latest updates. The only new thing that really caught my eye was a link to buy PASS merchandise. I can always use more polo shirts, so I will likely splurge on a shirt. (Heads up to my wife, a.k.a. she who controls my checkbook!)

I did speak to my mother this week, who asked me if I was planning on visiting my cousin (who lives in Seattle) during my trip. I said that, most likely, I wouldn’t have time. To be honest, it appears that there are a lot of activities going on around PASS Summit, and multiple friends who’ve attended in the past have told me to prepare to drink from a fire hose. So as much as I want to see people — I have several friends and family members who live in or near Seattle — I’m not sure if it’ll be in the cards for this trip. (And to those friends and family, if you’re reading this: if you do want to hook up, drop me a line; maybe we can work something out!)

So that’s about it for now. As I said, nothing really significant to report. Less than two months until I fly out to the West Coast! Looking forward to it!

Advertisements

Don’t tell me how to build the clock! Just tell me what time it is!

This article’s title comes from something that a former manager used to tell me all the time — often enough that he seemed very fond of saying it. Nevertheless, it’s an important message. This is not the first time I’ve written about this issue, but it’s something that occurs all too frequently. It is a problem in technical and business communication, and the issue is something that bears repeating.

I was reminded of this during our daily status update meeting this morning. The gist of this regularly scheduled meeting is that everyone has a short time — usually no more than a minute, if that — to provide a brief update of what they have going on. The key word here is brief.

One person proceeded to go into detail about some of the projects he had going (he has a tendency to do so). He’s been pretty good about keeping his updates short and to the point, but he wasn’t always like that. It took several long meetings and complaints to the manager to get him to tone it down.

For whatever reason, this morning, he reverted back to form. He started getting into details about his projects that, while important for the projects themselves, were unnecessary for status updates. It got to the point that I stopped listening to what he was saying and pretty much just zoned him out. I don’t know how long he took, but I’ll guess that he took three times longer than anyone else. Or at least it seemed that way.

This is something that everyone does (yes, I admit to doing it, too — ironically, even this very article may be too long). And it is a big problem in communication.

A part of the issue stems from human nature. We all have a limited attention span. The length of that attention span varies, but for the purposes of this discussion, let’s assume that it’s short — say, no more than a minute (sometimes, that might even be too long). If we’re communicating something, we need to make sure that it’s short and simple — and it had damn well better be efficient.

This is why people in roles such as technical, business, UX/UI, media, and marketing communication have jobs. They are in the business of taking large amounts of information and boiling it down into a format that most people can understand.

Whenever I’m writing a user or step-by-step guide, I follow a general rule of thumb: if an instruction cannot be understood within a few seconds, it has failed. That’s when I go back and rewrite the instruction.

Most of the time, people don’t want — or don’t need — or don’t care about — details. Unfortunately, too many people trying to communicate ideas don’t understand this (and worse, they often don’t care). As a result, horrible documentation (or, in some cases, absence of) is pervasive.

Too many people don’t understand that reading is work. It takes effort to read and comprehend documentation. One of my big pet peeves is any time someone tells me, “it’s right there in the documentation,” yet when I look at it, the information I need is buried someplace where I have to fight through the noise of other irrelevant text to find it.

This issue is the basic tenet of my presentation about talking the language of technology. People don’t want detail. They just want the information they need. If they need more information, they’ll look for it.

Good communication makes it easy for a recipient to quickly get whatever information (s)he needs. Don’t make someone have to work to understand communication. Don’t tell someone how to build a clock. Just say what time it is.

Monthly CASSUG Meeting — September 2019

Greetings, data enthusiasts!

Our September speaker is our own Greg Moore! He will do his presentation titled: “Pocket-sized Server: SQL Server for under $200!” For additional information and to RSVP, go to our Meetup event page at https://www.meetup.com/Capital-Area-SQL-Server-User-Group/events/264169963/­

Thanks to our sponsors, Datto, Capital Tech Search, and CommerceHub, for making this event possible!

Hope to see you there!

Want to get started with speaking? Try your local user group!

Usually around this time of the month — a week before (my user group‘s) monthly meeting — I’d be posting an announcement about our upcoming meeting.

I still will do so — as soon as I find out who’s speaking.

As I write this, I’m guessing that our speaker will be Greg Moore, but I’m not completely sure. One way or another, I’ll post an announcement later today.

Which brings me to the subject of today’s article.

Have you ever wanted to speak publically or do presentations? Consider doing so at a local user group. It’s the perfect place to do so!

There are many advantages about speaking at a local user group. If you’re a first-time speaker, it’s an opportunity to practice your presentation skills. If you’ve been a part of a user group for some time, you can do so in front of a familiar audience. If it’s your first time at a particular user group, it can serve as an introduction to the group. Either way, it’s a wonderful experience that is generally less pressure than presenting for the first time at, say, a SQL Saturday.

I’ve told this story plenty of times. In 2015, I came up with a presentation idea that I first presented at my user group. I had been involved with this user group for a while, I was among friends, and I felt comfortable about presenting to this group. Ever since that initial experience, I’ve spoken at several SQL Saturdays, and this coming November, I will be doing that same presentation for PASS Summit! My experience with speaking has also passively helped my career in numerous ways, including (but not limited to) expanding my network and improving my own professional self-confidence. I’ve come a long way since that initial start!

And if you’re still not completely comfortable with speaking, but still have an interest in doing so, there are other resources available to get you started. Look into groups or courses such as Toastmasters or Dale Carnegie. (Disclosure: I have friends who are involved with Toastmasters, and I, myself, am a Dale Carnegie grad.)

If you’re interested in speaking, consider starting at your local user group. You never know where a small start could lead!

P.S. if you’d like to speak for our user group, feel free to drop us a line!

Coming up with presentation ideas

As a followup to yesterday’s article, I thought it might be fitting to talk about presentation ideas.

Despite the fact that I speak regularly at SQL Saturday, none of my presentations (up to this point) have anything to do with SQL Server or even anything data-related. My topics revolve mostly around documentation and communication. So how do I go about coming up with presentation topics?

To answer this, I suppose I should go back to the beginning, and (re-)tell the tale as to how I got involved.

Back when I was primarily a SQL Saturday attendee, I knew I wanted to get involved. The question was, how? At the time, I looked around at the people attending the event, and I said to myself, “these people probably know more about SQL Server than I do. What can I present that these people would find interesting?”

In the early days of our user group (I was one of the original co-founders and members), we sought out speakers to present. I thought about data-related topics. I even took a turn one meeting where we were encouraged to bring up SQL-related issues as discussion topics. But when it came to ideas for data-related topics, I kept coming up empty.

I thought about a time at one of my jobs where I became an accidental customer service analyst. As a developer, I was not allowed to speak with end-users, but one day, I received a phone call from a user. It turned out that he had gotten my number from someone who was not supposed to give out my number. I was able to walk him through and satisfactorily resolve his issue. In fact, I did such a good job with it that, from that point forward, I became one of the few developer/analysts who was allowed to talk to customers. It made me realize that I had a knack of being able to discuss technology with end-users without being condescending to them.

During one user group meeting, I jotted some notes down. By the end of the meeting, I had come up with enough material for a presentation. I ran my idea past my fellow user group attendees, all of whom said, “that would make a great presentation!”

I worked on the presentation and presented it at a user group meeting.

Four years later, I will be giving that same presentation at PASS Summit! I’ve come a long way!

While that ended up being a good presentation, I’ve tried not to rest on my laurels. I still try to come up with new presentation ideas. I’ve come up with several since then, and I’m still trying to come up with more.

When I think about presentation ideas, I generally keep these thoughts in mind.

  • Is it a topic that attendees will find interesting?
  • Is it unique?
  • Is it something about which I’m knowledgeable, and I feel comfortable talking about?
  • Is it something I can present within an hour? And do I need to cut it back to an hour, or do I need to fill it in to an hour?

I still remember a piece of advice that Chris Bell, a DBA and fellow SQL Saturday speaker, once told me: “an expert is someone who knows something that you don’t.” That was profound advice, and I’ve never forgotten it. So far, it’s served me well in my speaking endeavors.

So if you struggle to come up with presentation ideas (like I do!), hopefully this will help you get the ball rolling. I look forward to seeing your presentation soon!

What do you do for an encore?

“The reward for work well done is the opportunity to do more.”

Jonas Salk

As a Syracuse alumnus and sports fan, I’m looking forward to this upcoming football season. Orange fans are excited for this season after last season’s 10-3 breakthrough, the first time that Syracuse has won ten football games in a season since 2001. Season ticket sales are up this year (and I’m happy to say that I am one of those season ticket holders). I’m looking forward to attending games this season!

In a recent interview, Syracuse football coach Dino Babers said that getting the team to break through with a great season (after years of mediocre ones) was the “easy” part. The harder part, he said, is maintaining it. As he often puts it, he wants to be “consistently good, not occasionally great.” Breaking through is a great thing, but after you’ve done so, how do you maintain that success?

I thought about this recently in regard to SQL Saturday presentations. One of my friends and fellow speakers gives a great presentation, but I do have one concern about it: it’s only one presentation. I’m not sure how long he’ll be speaking at SQL Saturday if he keeps submitting the same presentation again and again. I’d like to see him do more presentations, and I hope to see him at more events. Yes, he has a good presentation, but what does he do for an encore?

It’s for that reason why I look for more presentation ideas. As of this article, I have a brand new presentation idea that, right now, only exists in the back of my head. I listed it so that I’d remember to work on it. If I come up with what might potentially be a good presentation idea, I’ll set the idea aside so I can work on it. I want to make sure that I have fresh ideas. I love speaking at SQL Saturday, and I’ve been doing it for four years. I want to keep doing so. To do that, I want to make sure I have new material. While I do occasionally recycle my presentations (it’s unavoidable), I try not to resubmit the same presentations over and over to events.

For those of you who are looking to get your career off the ground, the same holds true for career endeavors. A great job that you did on a single project will often be enough to get you in the door. But once you’re in the door, how do you stay there? Breaking through on a project is the easy part; the harder part is sustaining that success. Once you’ve achieved something, can you do it again? And again?

If you are able to sustain success, you develop a reputation as someone who can deliver. That’s how you build a career. Achievements are great, but once you attain them, what do you do for an encore?

Upcoming speaking engagements (as of 8/22/2019)

Given this morning’s news, I figured it was as good a time as any to update my upcoming speaking calendar.

I am confirmed to be speaking at the following upcoming events:

So far, these are all I have on the docket.

Unfortunately, as much as I would like to go, I am unable to attend either Boston or Washington, DC this year because of schedule conflicts.

I did see save-the-dates for Philadelphia (May 2, 2020) and Virginia Beach (June 13, 2020), but those sites are not yet active (and may not be for a while).

I previously saw a save-the-date for Boston BI for March 28, but it is no longer on the calendar. And although it won’t be scheduled (or even discussed) for a while, Albany will likely be at the end of July next year.

So those are my latest speaking schedule updates. Stay tuned for more updates as they become available!