The Importance of Soft Skills

It is my opinion that database administrators will always need to just as technically proficient as they had to be in the past. I will agree that database environments are becoming easier to administer. Oracle Grid Control allows us to administer, monitor, tune and troubleshoot an Oracle database without having to go as deep technically as we had to in the past. Although we won't have to know as much about the internals as we used to, our skill sets will become much more broad in scope.

The database engine is taking on a much more strategic role in most organizations. It provides the mechanism to store physical data along with business rules and executable business logic. The entire application environment (data storage, business rule enforcement, application program storage, communication, system monitoring) is now controlled by the database. Over time, the database engine will store more information related to the understanding of the business, the meaning of the data stored (metadata) and the mechanisms to control and track versions of the database, access programs and related software. As the database's area of influence expands, so does the DBA's. Can any one of us predict what IBM, Oracle and Microsoft have up their sleeves in their next "latest and greatest" release? Not me. But THAT is what makes this job exciting. Our area of technical influence will be expanding, not contracting.

The Importance of Soft Skills
Now that I have expressed my opinion on the expanding role of the DBA, let''s talks about the importance of soft skills. Before we begin, I define soft skills as the ability to communicate in both written and verbal forms and the ability to interact with fellow employees in a positive manner. In the past, a technicians' lack of interpersonal skills was often overlooked. The more technically proficient the technician was, the more leeway they were given.

Let me provide you with a couple of quick examples. When I first started in this profession, I attended a meeting at a large financial institution that included some pretty high-level representatives from both the business and technical areas. One of the technicians that attended the meeting was a mainframe operating system support technician.

The guy was well known to be very good at as his job and as nasty a person as you would want to meet. The meeting started and it quickly became apparent that most of the issues being discussed would be about business processes. The O/S expert slammed his pen and pad down on the table and declared "It looks like this is going to be a waste of my time. I have work to do. Call another meeting with me when you need technical advice." He then promptly walked out. Being a junior level programmer, I was in awe. I asked my boss after the meeting who he was. He stated "one of our mainframe gurus, don't act like he does until you get as good as he is."

A dozen years later, I saw a technician raise his hand at an enterprise-wide IT meeting when the CIO asked (rhetorically I think), who was the most important person in the organization. I think the CIO thought the answer would be "the CEO." The techie who raised his hand said "I am." I think every manager attending that meeting shrunk down in his or her seat. When the CIO asked why, he stated, "when my computers go down, all business stops." Just a few months ago, I had a 20-minute conversation with a UNIX admin who never bothered to turn around from her screen to look at me.

Although my examples may be over the top, they show you the mindset that often plagues our profession. I have been guilty of falling into that trap myself. In the past, I could be described as being "somewhat temperamental". I can also say that once you get a reputation for being "somewhat temperamental", it becomes hard to shake.

As the years have gone by, I have migrated from DBA to DBA Unit Manager and now DBA Operations Manager. I have seen too many excellent technicians end up with a mediocre career because they achieved a reputation for "not playing well with others." I talk from experience. If you want to excel as a technician, you will need to be technical, but you will also need to work well with others.

Verbal and Written Communication Skills
I think people read this blog because they take pride in their work and want to become better at their chosen profession. So here's my second piece of non-technical advice. The importance of improving your communication skills can not be understated. I don't care how strong of a technician you are, if you can't communicate effectively with your peers, you won't be able to succeed in this profession. In the old days, you might have been able to get by with just your technical skills. That is definitely not the case in today's business world.

Take a look at your last performance appraisal forms, I'm betting that most of the criteria you are being judged upon depends upon communications. The key words and phrases to look for are "ability to work in a team environment", "keep supervisors informed", "maintain good communication with the user community", "ensure the content of the communication is at the appropriate level for the intended audience", "provide system and user documentation for projects and system enhancements." I pulled all of the aforementioned phrases verbatim from one of my own recent performance appraisals. I reviewed all of the criteria that I was being evaluated upon and found that almost ninety percent of the items depended upon verbal or written communications.

If you don' have good communication skills, all is not lost. Like anything else, these skills can be learned. I still consider myself to be only a fair writer. I am in awe of people like Craig Mullins (a fellow blogger here on DBAZine) who can just sit down and let the words flow. I often find myself agonizing over every word and sentence.

When I first started working in a corporate environment, my writing skills were terrible. My original career was not database administration, it was construction. A job that didn't require you to excel at written and verbal communications. One on the job accident, 9 operations and 11 months of vocational rehabilitation training later and I had a new career as a COBOL programmer. I went from working with a construction crew to working with computer programmers. My first employer was a very large and somewhat stuffy financial institution. When I was employed there, men couldn't leave their floor without wearing their suit coat.

I quickly learned that getting caught wiping your computer screen off with your tie didn't really show your managers that you were good at thinking "outside of the box." That was about the only thing I thought that piece of knotted cloth around my neck was good for. For the first six months, I refused to tie them. Being the non-conformist that I was, I just loosened them up, slipped them off and hung them up.

Saying that my communication skills were rough around the edges when I started my carrer would be an understatement. But I had the good fortune of having a manager that understood the importance of both verbal and written communications. I would write a memo, she would correct it with her red pen and send it back to me for a rewrite. Many of them had a "Nice Try!" and a smiley face on top. After becoming exasperated because of the numerous rewrites (and seeing all of those smiley faces), I thought I had better improve my writing skills. I read books, practiced writing and became involved with as many company newsletters and related communications as I could. When I asked to join a newsletter, I always started with "I'm not the greatest writer, but I'm trying to learn." I also asked my peers that worked on the newsletter to critique my work. The more I was critiqued, the better I became.

Same way with public speaking. My first speech could be described as being "somewhat less than stellar." Craig Mullins would gently prod me from time to time until he finally convinced me that speaking was something I should be doing from time to time. Craig promised to sit in the back of the room for my first speech and give me hand signals if I was speaking too fast, too slow, too loud or too soft. Halfway through the speech, my knees were knocking and his hands were in constant motion.

I found that like anything else, experience helps. But I will say that my speaking career was not without excitement. I learned that you really shouldn't drink a carbonated beverage wearing a tie mike that is attached to a set of 6 12-foot speakers. When I was done chugging the pop before the speech, I looked around and saw everyone laughing at the noises I had just made. I then found out that a tie mike doesn't help when you try to stifle a burp.

I also learned that some podiums are on wheels and those wheels aren't always locked. I started my first sentence, leaned against the podium and it began to move. I tripped a little trying to stop the podium from moving and ended up heading for the end of the stage at a very rapid rate. It was a raised stage too, about six feet higher than the first row of seats. As I quickly approached the end of that raised stage, I noticed that the people in the first row were making motions just like the extras did in the old Godzilla movies- right before they got stomped on. Lucky for me one of my work buddies in the first row had the good sense to jump to his feet and stop the podium (and me) from killing a few members of my audience. I got over those little snafus and kept plugging away. With each subsequent speech, I started to improve.

The point I am trying to make is that you can improve upon your communication skills. IT shops are no longer evaluating technicians purely on their technical skills. I have seen the soft skill evaluation pendulum swing a little more each year.. It is the total package of skills that you bring to the table that you are being evaluated upon. We all know the importance that our technical skill sets have upon our success in this field. But you also need to be well rounded in all of the skill sets your managers are looking for.

Thanks for reading,
Chris Foot