The reason for the bloated timecard was initially a project to implement dual WAN for our network since we had severely outgrown our two bonded T1's. This effort quickly evolved into a massive overhaul that standardized a number of things in the environment and also corrected a few issues that had been hanging over my head since I came into this job.
So what came out of this?
Well, the project accomplished its intended end result and I'm happier with the way things are structured. There's something more though. When a person labors with that monk-like concentration day and night sometimes things come into focus a little better than they did before.
- Do decision makers understand the cost of understaffing IT? Its NOT a cost savings. Its gobs of downtime between periods of treading water.
- Planning is key to success. Seems like such an obvious thing but it isn't when you're in the middle of something. If you don't plan for 5-8 or even 10 years down the road when designing your infrastructure you will be screwed in less than 3 years.
- Users have no idea what IT does. And it shows about half way through a transition. Right around where people start calling to complain that "such and such isn't working" when it was very clearly established that downtime would be happening. My favorite are the folks who call me, the "network guy", for an Excel problem when they know the network is down and being worked on.
- Doing something the right way isn't what organizations want if it isn't the cheapest, quickest, and least amount of trouble short term. I see the point, but its a hard sell if I've been working for 30 hours with only 4 hours of sleep in the middle of that.