A few days ago, we had a request from 'Senior Management' to configure a server for Netmeeting. This server was to be provided by another group within the company, as it would be for their use.
Us poor overworked souls in IT, after a brief discussion, realised that such a thing is utterly trivial. So we came back to them, and asked if they'd prefer some instructions on doing it - after all, this server was notionally theirs, and they'd be taking charge of it. And just because it really was quite so trivial, and we were helpful sorts, we attached the 12 lines of instructions to the email.
The response was "No, just install and configure the server, and then us know when it's done so we can change the DNS. It's more efficient to do it this way.". This email is of course, copied to 4 different 'Directors' and our line manager. Who incidentally is on holiday at the moment.
With a little wave of the magic wand of IT, the simple task of installing ILS is complete. We send off the details, and are content. A job well done.
A few days later, however, we receive a request (via the same senior manager) to document what we did to install this.
And as it was just so trivial, we re-send them the 12 lines of instructions on how to add and remove Windows components, and pointed out that it was ILS they needed to add.
But the Senior manager in question was not happy with a mere email. No, he wanted a Word Document, because that would be 'more formal'.
He has since gone on holiday, and his collegue (also a Senior Manager) is chasing up the document. Because it's important to them. That we take the email we sent them right at the beginning, and copy and paste it into a word document.
Never let it be said that our IT department wastes time.
Us poor overworked souls in IT, after a brief discussion, realised that such a thing is utterly trivial. So we came back to them, and asked if they'd prefer some instructions on doing it - after all, this server was notionally theirs, and they'd be taking charge of it. And just because it really was quite so trivial, and we were helpful sorts, we attached the 12 lines of instructions to the email.
The response was "No, just install and configure the server, and then us know when it's done so we can change the DNS. It's more efficient to do it this way.". This email is of course, copied to 4 different 'Directors' and our line manager. Who incidentally is on holiday at the moment.
With a little wave of the magic wand of IT, the simple task of installing ILS is complete. We send off the details, and are content. A job well done.
A few days later, however, we receive a request (via the same senior manager) to document what we did to install this.
And as it was just so trivial, we re-send them the 12 lines of instructions on how to add and remove Windows components, and pointed out that it was ILS they needed to add.
But the Senior manager in question was not happy with a mere email. No, he wanted a Word Document, because that would be 'more formal'.
He has since gone on holiday, and his collegue (also a Senior Manager) is chasing up the document. Because it's important to them. That we take the email we sent them right at the beginning, and copy and paste it into a word document.
Never let it be said that our IT department wastes time.
no subject
Date: 2004-08-23 09:57 am (UTC)*slightly bitter about IT today*
no subject
Date: 2004-08-23 10:08 am (UTC)no subject
Date: 2004-08-23 10:09 am (UTC)no subject
Date: 2004-08-24 02:47 pm (UTC)I sometimes believe if you want IT to work better for you, you should kill off the computer illiterates in your company.
:)
no subject
Date: 2004-08-25 12:18 am (UTC)There's a meeting to discuss how to improve staff moral. But it seems that no one could be bothered to go (seriously) and the HR person had to pop around and see if she could persuade someone...
no subject
Date: 2004-08-25 04:34 am (UTC)I could go ON and on.
no subject
Date: 2004-08-25 05:33 am (UTC)And I'll _tell_ them what the problem is. I doubt they'll hear though.
It's really very simple.
Pay freeze.
Hiring freeze.
Managerial types with no purpose but to generate work for everyone else. (In this particular case, there's an identifiable group).
Directives from 'head office' that make no sense - we have had to change our ISP service from one to another. The cost has quadrupled, and our service level has dropped.
Oh and the kind of crap I originally posted around. That's just a particularly clear example.
no subject
Date: 2004-08-25 05:35 am (UTC)no subject
Date: 2004-08-23 10:01 am (UTC):)
no subject
Date: 2004-08-23 10:41 am (UTC)no subject
no subject
Date: 2004-08-23 02:36 pm (UTC)mv instructions.txt instructions.doc
No-one who knows enough to notice the difference will care.
no subject
Date: 2004-08-24 12:03 am (UTC)no subject
Date: 2004-08-24 12:24 am (UTC)no subject
Date: 2004-08-25 02:18 am (UTC)