Misused - Part 1

the systems administrator

All too often in my career, the systems administrator has been the role of the misused. After 20 years of being one, managing many, understanding how they breathe, what they thrive on, and what they are capable of, I can tell you this. The company matters not. The size of the organization matters less. The leadership, ah, there is what matters. A good systems administrator will be a silent type. You never have to hear from them  because they are always behind you, trying to making whatever it is you dreamed up to work. Tirelessly working out its issues, they are; sacrificing time after many have become pillow-fodder.

Why?

They believe this is what their job is, what their roll is in the big picture, and they have been trained and engrained to believe it since about 20 seconds after the computer was invented.

It does not need to be this way.

What if...

...they were an equal member of a kick butt team, able to provide input, be listened to and listen in alike.

...they assist in designing the road that carries everyone forward, pointing out where the path can be straighter and faster.

...instead of being handed something to make work, they have a hand in making it, so it works. Making it so it can be supported. Making it accomplish.

...allow them to do, to make, to attempt, to fail, to learn as a team, on the project, at the start.

You can. It works. I have seen it. I have done it.

If you have a systems administrator, you have, first and foremost, a person. Get to know them. Understand their strengths and what drives them, then tell them where you want to go, not how to get there. Work with them on solving the mutual problem and be amazed at what they know, and what they can accomplish as an equal team member from the start. Consider the following:

Do not ask for "a server". Ask for assistance solving a problem that requires resources and their expertise, then do the same for the network it rides upon. Work together on the design as engineers of network, server, code, delivery, monitoring and those things that are important to the operation of the problem solving solution.

Do not throw it over the fence. It does not matter what "it" is. No ownership will ensue. No digging in will commence. No availability will survive. Nobody will stay around.

Be an agile leader that makes this happen. You will not regret it.

Be the systems administrator that provides input to an entire project team.