Slashdot Mirror


Ratio of IT Department Workers To Overall Employees?

An anonymous reader writes "I was recently talking to a friend about the Fortune 100 company she works for in IT. She told me the company has 35,000 employees, including over 5,000 IT employees — and it's not a web firm. It has numerous consultants doing IT work as well. To me, from a background where my last job had 50 IT employees and 1,000 total, a 1-in-7 ratio of IT employees seems extremely high. Yet she mentioned even simple changes to systems/software take over six months. So, what ratio does your company have, and what is reasonable? How much does this differ by industry?" I'd be interested to see how much it differs by OS platform as well.

12 of 385 comments (clear)

  1. 1:100 at many places by VoidEngineer · · Score: 5, Interesting

    I just left a job at a hospital of 3000 employees, which had an official IT staff of... wait for it..... 12. I was part of the big "departmental restructuring" where the IT staff went up to... 18! And of course they wanted us to be on call 24/7 and would refuse us vacation time because there wasn't anybody to cover for us. Needless to say, I resigned.

    But yeah... 1:100 ratio is not unheard of at many hospitals. It's all because of outsourcing....

  2. Re:In Australia by Techman83 · · Score: 4, Interesting

    Forgot the OS stuffs. Imaging/Standard Builds/Standard hardware all User equipment Windows XP Sp2/3, Servers mixture of Virtualised/Physical, Windows, Linux, Solaris.

    --
    # cat /dev/mem | strings | grep -i cat
    Damn, my RAM is full of cats. MEOW!!
  3. Sixt has that without outsourcing by Casandro · · Score: 3, Interesting

    Sixt, a german car rental company which is mostly based on Linux (including the desktop) it is roughly 1:100. They have about 2000 employees and about a dozend of them are in the IT-department.

  4. Re:Makes sense by WinterSolstice · · Score: 5, Interesting

    I have repeatedly worked for exactly this kind of company.

    As a 13 year IT veteran who has worked everywhere from .com startups to world-wide multi-billion dollar fortune 100s, I must say that you hit an amazing amount of bloat quite quickly.

    I can't say what the ideal ration is, but my current company is too big at about 1:10, and my previous company was 5k people with an IT of less than 30 (about 166:1).

    The previous company was amazingly hard work when we had 15 IT, and then suddenly the C levels decided we need help and added 4 managers, 3 directors, a VP, and a change control board. We only got about 10 actual "workers". Productivity plummeted.

    My current company has an IT so big that we spend all of our time fighting with each other. It takes months to create new user accounts, months to get simple servers built, 2 weeks to schedule a reboot, etc. The users and the business hate us.

    A DOD shop I worked for had a staff of 500 for 12k users, and it worked pretty efficiently. Of course, they were almost entirely former/current military. This led to always knowing precisely what you were supposed to be doing and a really well run group. Maybe that makes a difference?

    So, while I can't say what the exact ratio is, it is pretty low. I also think the skill level has something do with it - a small team of skilled people "bond" and form a fast moving and smooth team. A huge team lends itself to infighting, argument, one-upsmanship, face saving, and general worthless behavior.

    --
    An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
  5. My old orkplace by tyldis · · Score: 4, Interesting

    250 employees on 200 computers.
    500 students on 100 computers.
    8 locations.
    10 servers.
    Ancient infrastructure (NT4 and NetWare) desperately needing an upgrade.
    IT staff: just me.

    This was for a Norwegian muncipality a few years ago. It was fun since I could control every aspect of things, and develop most things from scratch.
    NT4 got replaced by a mix of Linux and Windows 2003 and hardware inrastructure renewed.

    The downside was work 24/7 and no real vacation. I lasted two years before I ran away.

    Now, as for ratio i don't think it is symmetrical. Having your IT staff go from 1 to 2 will give you very little extra beyond sanity. It would not mean double capacity. However, going from 19 to 20 IT staff that last person would add heaps of more capacity.

  6. Re:no set ratio by NoobixCube · · Score: 4, Interesting

    A very good point. I work in an internet cafe, and everyone - even the manager - is IT staff. If anyone there weren't IT staff, our efficiency would go out the window. I'm just pleased that my first job in IT didn't land me with a Pointy Haired Boss.

    --
    Admit it. You post strawman arguments as AC so you get modded Insightful for refuting them, rather than Troll
  7. Re:What about technical vs. non-technical within I by AdamInParadise · · Score: 4, Interesting

    I worked with a US company were the ratio was 6:1. Yes, about 6 managers for 1 programmer (they had 3). They've been working on their (not so complicated) product for about 4 years, with no end in sight.

    --
    Nobox: Only simple products.
  8. Re:Crazy.. by TedRiot · · Score: 4, Interesting

    I was just about to think no-one would bring up SOX, when AC came to the rescue. The SOX requirements AFAIK for IT are insane. People doing development aren't allowed to touch production systems, for example.

    I met a guy recently that works for a US company that has to follow SOX. They have a quarterly audit which lasts 8 weeks at a time and has more than 600 audit points for IT alone. This means that 2/3 of the time of year they are under audit. And if you fail the same point in two audits in a row, it's byebye.

  9. Re:Makes sense by dotancohen · · Score: 3, Interesting

    Until you get the next time where someone has a genius idea with a subtle flaw that doesn't get caught until it goes through the 3rd level of red tape.
    When you are talking about a big enough organization, any amount of bureaucracy and layers will pay for itself if it prevents a single huge mistake every couple years.

    Quite the opposite. Each layer can then try to blame the one above / below it. When there are only 2 / 3 layers of bureaucracy, each takes on more responsibility.

    --
    It is dangerous to be right when the government is wrong.
  10. Re:extremely high by YttriumOxide · · Score: 5, Interesting

    Which brings me over to the question "what is an IT person?"
    I am sure that different companies define this differently, and some might consider e.g. payroll processing "IT work", while others include non-IT personnel working for the IT department, like (in order of importance) janitors, cafeteria workers and CIOs. In a big company, they still may be employed in the IT division, and count as IT.

    That's a very good point. It can work the other way as well, where you have "IT people" who don't work for the IT department. I have no idea how many people work in my company's "IT Department", because I don't work there and generally have no need to talk to them about anything. I work for a department called the "Solution Centre", which is in charge of finding and developing IT solutions for customers (rather than internal IT, which is what our IT department does). I'm employed primarily as a programmer. So, am I an "IT Person" or not? How about the guy in my department who (amongst other things) is responsible for making sure our test network stays up? He doesn't work in the "IT Department" either, but in almost every way can be considered a sys admin.

    If you ONLY count our "IT Department", I GUESS we have a ratio of around 1:100 or maybe less, but if you count people outside of the IT department who do IT related work, it's probably closer to 1:5. We've got somewhere around 40000 employees worldwide (not counting third party companies that "live and die" solely by what we do and for all intents and purposes are part of us, just not from the "business" side)

    Our main "normal" IT infrastructure is a mix of Linux and Windows servers for various tasks and I think an AS/400 type system somewhere, with almost exclusively Windows XP workstations for employees. In departments such as mine, we tend to be 25% Linux, 40% Windows, 30% MacOS X and 5% Other (including things like a couple of Solaris boxes, one Mac OS 9, and so on. Most of the people in our department have TWO laptops per person - one (usually WinXP system) for the "corporate network" (where we check our email, etc) and one for the "test network" where we do all our real work. On top of that, we have the mix of systems I just described as desktop systems and servers on our test network. The IT department only looks after our corporate network systems (which are mostly WinXP).

    --
    My book about LSD and Self-Discovery
    Also on facebook as: DroppingAcidDaleBewan
  11. Re:That's a lot o' IT by walt-sjc · · Score: 3, Interesting

    Then you need glasses. Seriously. Larger companies tend to have Many Many specialized systems, some of which require full time dedicated staff, or TEAMS. They probably have a mainframe (or 20 of them) too.

    Keep in mind that a fortune 100 company is likely to have facilities all over the country / world, some facilities probably staffed 24/7.

    While 1/7 seems quite high, 25/15000 would be just insane.

  12. Project Athena at MIT by Jah-Wren+Ryel · · Score: 4, Interesting

    Check out this article from the IBM Systems Journal about the work done at MIT on Project Athena and the model they developed for calculating the number of required IT staff based on the number of workstations, users, applications, licenses, etc.

    --
    When information is power, privacy is freedom.