Recently I read a book titled "The 21 Irrefutable Laws of Leadership" by John Maxwell. In this book, Maxwell categories the qualities that creates a great leader. As I read this book I thought about the many managers and leaders that I have encountered in my life, including the ones that we all have read about in the history books or seen on the evening news. I saw how these qualities were exhibited in some leaders and how they resulted in exceptional leadership. I also saw how these qualities were disregarded which resulted in disaster.

The reading of this book would be incomplete without a fair share of introspection. I saw qualities that come to me naturally; but could use some refinement and intentional growth. I saw qualities in which I really struggle to be average. It was a great comfort to read in the book's introduction that even the author recognizes that he is weak in some of these qualities. It is also comforting to read that all of these qualities can be learned.

As I concluded the reading of this book, I thought about the role of a DBA in light of these qualities. There are some DBAs, such as myself, who are in a role or position of leadership within their organization. There are other DBAs whose role is more of a solid technical one without any clear designation of leadership. One of the statements that Maxwell emphasizes in this book is that everyone has the opportunity for leadership even if their organizational position does not call for it. There is a clear difference between the mindset of leadership and positional leadership. The former can exist without the latter. The latter cannot be effective without the former.

I would love to write about each of the 21 laws and how they relate to the DBA role; but it would be very likely that most reading this will not get past the first few before heading on to other blogs. There is only so much time in the day to read, right? So, for the benefit of brevity I will pull out two of these laws and provide some quick thoughts:

The Law of the Lid: "Leadership Ability Determines a Person's Level of Effectiveness"
As a DBA you can possess all of the technical skills that can be acquired. You can take a poorly performing database and optimize the heck out of it. You can author the most effective and efficient T-SQL and speak to its minute intricacies. You can design an awesome database schema that is appropriately normalized and indexed. All of this can make you very effective technically; but if you cannot express your thoughts in a way that the non-technical managers of your organization can understand and be convinced to fund your efforts financially or resources you will not realize your full effectiveness.

A DBA who has put as much effort into refining their leadership skills as they have their technical skills will flow into the category of being an exceptional DBA. Brad McGehee has often spoken and written about "How to become an exceptional DBA". Many of the qualities that he speaks of are a great representation of the balance of technical skills and leadership qualities.

The Law of Connection: "Leaders Touch a Heart Before They Ask for a Hand"
The DBA role is often characterized as a fascist dictator who guards the database realm with a pack of rabid Doberman Pincers. He carries a big stick and uses it quickly leaving Developers cowering in the corner paralyzed. This certainly is not the picture of an exceptional DBA with leadership skills.

An exceptional DBA with leadership skills will make the effort to understand the task that the Developer has been charged with and take the time to discuss solution options. When the DBA can elevate the skills and morale of the Developers then they are exhibiting leadership qualities. When the DBA is busy tearing down the Developers they are a destructive element. Think about how you speak of the Developers that you work with when you are conversing with other DBAs.

Imagine the culture that I described at the beginning of this section where the DBA and Developers are infected with the "us vs. them" spirit. What will the response be when the DBA is in need of the Developer's assistance? Would the DBA even approach them for help? How effective will the DBA be in their role?

"Leaders define reality." - John Maxwell
"Be the change you want to see in the world." - Mahatma Gandhi