Burning the Red Tape
Of recent times i have noticed that the amount of project delays due to sheer user laziness has been on the increase. I am not sure why this is becoming the norm in the workplace but it is.
To me the most common scenario is the dependency delay. The dependency delay states the what ever you are working on is dependant on the work someone else is providing , with out them completing their work you are unable to proceed. Now while this is a valid reason it should not be abused so that everything you are working on becomes some one else problem. The trend that people tend to follow is the one where they will go to person A and request some data .Once the request has been submitted they feel their job is done, now while it may take person A few hours to get this data depending on how busy said person is, it does not give the requester permission to just sit around and relax. If it means that you sit by the users desk until you get the data or that you have to constantly check on the user to get the data then do that. Show that you a making and effort to actually get your work and other peoples work done proves that you are actually useful in a growing company.
I have been to way too many meetings where a issue was raised and the person in charge of the issue simply states that they are waiting on someone else ,while this may be valid the first time at any subsequent meetings this should not be the case. While it may look like you are doing your job really well (some times people do work so fast the rest of the office plays catch up) majority of time this is a false positive and does not really indicate just how efficient the person is. I personally feel that you should measure a person based on the end result of their work while taking into consideration length of project and difficulty as well.
Another thing that people seem to love doing these days is putting up red tape. While this is nothing new , in this day and age it has taken on a whole new meaning especially in the IT world. You just have to take a look at the number of story’s like this that appear in The Daily WTF to realize just how much of an issue it is. While it is understandable that at some point in the business life cycle there was a need for some red tape so that efficiency can be measured or even just so that stats can be captured. This is not always needed and it is definitely and ends up slowing down what might have once been an efficient process. Another note that comes to mind is that red tape is usually thrown around by people that a resistant to change.
There is however hope on the horizon (for developers at least) and that hope is agile development .In the agile environment there is usually changes made on a constant basis and because of this a lot of red tape has had to just fall away because it would just encumber the process to the point where it would not work. Now do not misunderstand this , there is still control in a agile development environment , its just that a lot of the office politics that results in red tape has to fall away.
There is still a lot that can be especially with regards to company’s implementing new processes because they have seen bigger company’s use them without realizing that its just not meant for them or that they need to put a decent investment into it to make it work.
As always let me know what you think and any comments are welcome.
~stalkerh


