I am all for status reports and have found them to be very useful
for my fellow managers as well as for myself. The frequency and
style of the report is what you will need to work on with your
management types. It is likely that they will want a monthly (not
weekly) summary of IT?s productivity and/or major projects.
Most will not be interested in the 'behind the scenes magic' that
keeps network services humming. But a monthly reminder will
help with the perception that you don't have enough to do.
Be sure that you write your narratives in plain English avoiding
techno-babble and acronyms most people would find unfamiliar.
I have even resorted to "plumbing" analogies on more than one
occasion to explain bandwidth. Also, be careful of what numbers
you report. The number of server and application patches
installed is not nearly as descriptive as the time and number of
staff it took to do them, test the patched system, not to mention
the "why it is important to keep the system current".
Try to structure the narrative in a way that not only reflects what
was done and how long it took, but also what that (end product)
means to them as far as services (ie. continuity of service,
updated redundant system for DRP, maximum email server
reliability, etc....)
One last thing ... If management had the impression that you
could do with fewer staff, it leads me to ask the question. ?What
were they doing during their down time?? While other managers
don?t see the brainstorming and trouble shooting in the server
room, or the imaging of a new machine not to mention all those
great things we can do with remote management software, they
do notice to many copier/water cooler conversations. Be sure
staff have low priority tasks to do when downtime does occurs.
Be it cleaning up the mess of wiring at on the patch panels to
online or CD skills training.