Price of Progress

Change is a funny thing. Change is what people fight the most, but only a bad situation can be remedied by it, a paradox that many fall prey to.

In the IT world, change is a bitch, to put it nonchalantly. I mince no words in saying that there are many, many times that change is a fantastic thing, but there are far too many instances when change just made things really, really bad.

One of the main reasons I was happy to leave ORNL was the inability to change anything. I?m happy to say that in a small office, change is not only happening, it is constant. Each day something comes up and people must work together as a team to remedy it.

That is, everything but the IT side. Because nobody wants to change the direction of the current computer/software/procedure schema in that regard. It?s been very interesting in my attempts at bringing change to an organization that needs it.

For example, I recently changed the way we processed payments from an old dilapidated laptop to an online-based webform system. More efficient, mobile, and usable in each and every way, but it was resisted because, like any IT change, it would hurt (that?s code for it would take time to learn). Of course, that?s just a myth, but every business person who doesn?t know what TCP/IP stands for would rather endure hours of fingernail-pulling than upgrading their operating system, favorite program, or business application. Some things must simply be seen in action before they are appreciated.

I?m happy to say that the payment processing is much (much) more efficient and after a few speed bumps early on, I?ve not heard a word about how we process payments nor anything relating to it. Better yet, the entire process from start to finish took 6 weeks, a total that sounds longer than it actually is. In IT, change happens like accelerated evolution: Sometimes when it?s over you?ll have an extra finger or eyeball, but that?s what scalpels were made for.

My latest project is even higher on that scale: The replacement of our file server and total calendaring system. This is a huge (huge) change, one that will try and affect almost a decade of consistent use. Were there objections? Some, but after ten years of the same old system, realizing and trying to work around its limitation, have worn on the people here. They?re ready for change, and now it?s my job to try and make that change as smooth and seamless as possible. Please realize that this is not the norm. Normally I?d be tearing the old program off their machines with the users? fingernails still attached, blood still running down the screen as the uninstaller fires up.

I?ve always viewed system administration very much like phone companies: You only hear from them if there?s a major problem, and you only call them when you have an issue. You?d never call up Bellsouth and say ?You know what? You guys kick ass. My phone has worked non-stop for years now? just like you?d never call up your IT guys and say the same thing. Now it?s nice when people appreciate your help with cookies, cakes, and treats, but that?s few and far between. You have to be prepared for a largely thankless userbase but as long as the boss and coworkers recognize your contributions, it?s nothing but gravy.

And here where I work, the gravy has flowed just fine. Now where?s a mashed potato metaphor when you need one? See ya next week.

Do you miss me, Miss Misery
Like you say you do?

Tags: Change Progress IT upgrade install payment processing calendar server