IT professionals only wish they could nicely wrap up all their project work and the fires they must extinguish within a 24-hour period. As in 24, technology can greatly enhance our ability to resolve difficult tasks quickly. However, technology can also wreak havoc because of security intrusions, viruses, poorly trained personnel and overworked, tired IT workers trying to accomplish too much in too little time.
Despite all this technology at your finger tips, do you ever feel like there are simply not enough hours in the day to get to even half of the tasks on your daily to-do list? Well, join the club. Todays IT worker is truly stretched to squeeze every valuable minute out of every hour that races by each day. With short-handed technical staffs working in a global environment, the stress levels of IT workers are being pushed to extremes.
I thought the best way to illustrate this was to walk through a typical day of an IT manager. This may or may not resonate with other IT professionals, but hopefully it will illustrate how 24 hours can rocket past anyone working in IT.
05:30 Dragged to consciousness by alarm clock. Pulled out of wonderful dream where Vista desktop upgrade went without a hitch. Back to reality and off to the office.
06:00 Check the Blackberry while waiting for the traffic report to see if any system status alerts went out overnight and if the offshore development team in an opposite time zone has sent in their deliverables. Good news: no traffic issues. Bad news: a slew of system alerts and no deliverables in the inbox.
|Smart IT Columns|
Dealing with Idiot Vendors
When Just Enough Is Enough To Be Fired
Easing The Pain of Being On-Call
Understanding Your 'Idiot' Manager
06:30 Cant find seat on subway. Balanced between the masses and manage to send an email to offshore counterpart to see what the hold up is. While waiting for response, dig into backpack (no respectable IT professional carries a brief case any more, do they?) and pull out latest IT trade rag.
08:30 Roll into the office later than usual thanks to a subway snag. Receive email from offshore manager explaining that build didnt work. Now testers in US office will get to surf the Web all day. Must quickly prepare for 09:00 staff meeting. Shouldnt have read the trade rag on the subway.
09:00 Start staff meeting with bad news. Budget cuts have killed a pending software purchase that would have saved the team many hours in predicting and troubleshooting network issues. This means more after-hour support calls from irate users complaining about slow applications. End meeting on a positive note by announcing retirement of our biggest pain in the rear end-user. Everyone agrees that this helps offset the software budget loss.
10:30 Meet with CIO to discuss business intelligence initiative. Selected vendor was recently purchased by Oracle after team just finished migration of all databases to Microsoft SQL Server. CIO asks if the contract can be voided and wants an answer by end of day. Time to call in the lawyers. Had plans to meet a friend for lunch. Plans cancelled. Having lunch with lawyers instead.