Discussion Locked

Advice On MIS Dept. Staffing

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm an IT Manager for a private, non-profit company. My CEO is asking for some sort of IT standard or best practices recommendation on adequate MIS staffing based on network user size.
I am unaware of any such thing, but asked a few of my peers (two of which are consultants). They recommended at least 2 support staff. Our current user size is 110 users (and growing). We are on a W2K Server network, and are in the process of implementing a new accounting software system. I am involved heavily in this implementation, and am trying to prove to her in writing that I need more staff. I use a local company to help supply hardware and software, but a good deal of the troubleshooting is left to me.
Help!

7 replies

by nels

Not sure what you're asking, but your consultant peers are correct. For the size of users you have and the "implementation" you should have 2 more to help support.
Besides the new accounting software, you need help troubleshooting the everyday problems that occur in a Micro$oft world.
The price comparison on productivity of your users should outweigh the prictag of new support staff. If users have to wait for you to come to the rescue (while you're helping somebody else) they are wasting time and money. Do a analysis and estimate what the price comes to on both.

by penguinsrule

There is no such thing as a perfect answer to this question. Here's an example. I know of a situation where the right number is one staff member to support one user. Obviously this isn't something you want to do in every environment, but for thatenvironment that was the right number. So what determines the right number?
1) Any access restrictions you may have to deal with in the user environment (such as security clearances, security, safety issues, etc.
2) The political climate - extremely important!!
If the political climate warrants more people for
a situation sometimes that may have to be done.
3) Particular complexities, such as complex hardware, software, or people situations. What if you have a user base that is at war with you? Then how do you come up with that number??
If you find some best practices paper out there that looks all great and pretty, it hasn't been lived out too well. Why don't you talk to some folks that have been in the trenches some to bounce off the ideas a little?

just my thoughts..

This discussion is closed to new replies.