I’m in the kind of job where, according to best practices, I need finite processes defined for everything I do. Skipping past acquisition, in order to get a server ready to install an operating system, I have to request a place for the server to go, ask someone to install it in that place, ask for cables to be run to it, define what those cables do, submit a request for a unique address(s), and finally provision the operating system. Really, that doesn’t look so bad on paper. In fact, looking at it here I’m thinking, hey, jotting this stuff down really simplifies things. There is one problem, however. While there aren’t that many tasks that have to be done – not unnecessary tasks, anyway – I’m not actually doing any of them except for the last one. That means I’m depending (corporations teach us to use the word “leverage”) on a bunch of people to handle my individual tasks. So what could be taken care of in a matter of an hour, generally takes in excess of a week. Did I mention that I’m doing this for servers that reside in a lab environment? There are also details within each of those steps that further complicate the problem. Bad forms, disparate requests, and busy people. Granted, there are plenty of reasons why this kind of process is really helpful. It’s just that when I’m pinned as the responsible member of a process that is done primarily by people other than me, I have a gripe. Everybody has this problem somewhere in their life. I’m certainly no exception.
My resolution to this issue is to develop a single form that documents all of the needs for a server(s). The form would then be sent to all accountable members of the process for their respective parts. Information sharing is enabled between the working members and is not sought through the requester. At least not for processes that are occurring outside of the requester’s interests.
It’s a pipe dream, I suppose. Maybe the new acquisition will help (snicker!).