Slashdot Mirror
Organizational Practices of an IT Department?
fbg111 asks: "I've recently joined a company, a regional airline, with an IT department that has grown organically (ie in response to immediate, rapid-growth-driven need, rather than according to any organizational plan). In the past five years the company has come to rely on IT, specifically the web team, for about 3/4's of its revenue. However, this unstructured growth has caused some problems, like this one: the lack of defined career paths and clear promotion 'triggers' makes techs feel 'stuck' in dead-end situations, and we tend to lose good people who find more transparent advancement opportunities elsewhere. I've recently joined the new CIO's task force for putting together a plan that addresses the immediate problem of defining career advancement paths and payscales. Does Slashdot have any ideas on this subject?"
"I'm particularly interested in industry best practices that cover providing breadth and depth of experience and training, dual (or more) career tracks that allow techs to go the management route or the technical guru route, and aligning promotion triggers and career paths with IT department & corporate goals, and anything else relevant to the matter. Do any of you have anything in particular to recommend?"
Talk directly with each and every member of the IT staff, first as a group and then in private. Find out what they want. Find out what they expect. Collect all the data you can directly from them. Then discuss your findings with the CIO.
After you come up with a preliminary plan, again, discuss it with the staff. Get their input. Don't just come up with a plan and then implement it. Use all the feedback you can get, so that you create something that benefits everyone (potentially).
Cyric Zndovzny at your service.
I hate to sound mercenary, but if you want your employees to feel valued and appreciated, say it with money. Other gestures can be very nice, but in the end most people come to realize that money is the only metric by which businesses measure value. If the IT department is as important to the revenue of the company as you say it is (which I find a little hard to believe, but let's assume you're right..) then the employees should share in the company's success.
Advancement doesn't really have to be attached in work -- it can be outside of work. I started my position as a systems administrator, and was promoted within a year to systems administrator II. The change in title was arbitrary, as I was doing the same work, however I had a few bonuses that were department specific. The biggest bonus for me, was a bigger and more flexible training budget for me. That means if I wanted to learn something and it was IT related (not job related), I had a budget I could use to do what I wanted. So we are a Windows only shop... I have chosen to learn Linux even though it has no bearing on my job.
:)
The rationale behind this is pretty simple -- a person gets complacent, and especially in IT, because they feel they are going to be outdated, or they aren't performing duties that will get them noticed in a future job. While your employer's job is to keep you working at THEIR company, they can't remove the possibility of you working somewhere else -- and the career 'path' at a company has to take this into consideration else there will be a lot of turnover in your IT department. Web programmers that are doing one thing, constantly and not being able to use and learn new technologies (because if it ain't broke, don't fix it) they won't feel the need to stay at that company, even though they are stellar at their jobs.
Bonuses are good too. Stock options, Christmas bonuses, paid holidays, and a big one that's often overlooked -- gym memberships -- are all very important. Little expenditures can reap huge rewards for an IT department because it keeps employees happy. As IT personnell, I have personally found working in environments that are laid back (let me wear a backwards hat, t shirt and shorts to work!) are the best. With hours being spent in front of the computer, they should be comfortable, and sitting in the best chairs, have the best keyboards and mice, nice monitors, etc. It's something that other departments SHOULD envy because let's face it -- if your company is relying on them to make the money, then your company is going to want to make them feel wanted. It works much the same for sales people in ANY field -- do your job well and you get more perks than you can imagine.
So if your company can offer title changes, personal training budgets, maybe some catered food once in a while, free tickets to see some ballteam playing, the best equipment, ergonomic chairs, etc... these small expenditures will go a long way to keeping the staff you have happy and working hard for YOU and not somebody else.
I should mention one piece of advice I learned from a friend that is a manager, and that is exceptional in his field and his employees love him. What he said is something like this:
"Your job as a manager for your employees is to assign them the work to do, see they do it satisfactorily, take the blame FOR them if they fuck up, and then tell them to stop fucking up in PRIVATE. And when time comes, you fight tooth and nail to get every penny you can out of the higher ups to make sure they get the best raises they can get."
There is no faster way to lose employees when if they make a single screwup, the world comes crashing down on them, believe me they are going to look to leave fast. It makes me regret leaving MY last job, because it's the situation I'm in right now. So on a side note... if anybody's looking for a Windows SysAdmin....
Good luck to you.
The price is always right if someone else is paying.
It's been my experience that this type of thing is simply a talking point. By organizing a committee/task force/other_buzzword, it gives the impression something is happening since all these wonderous ideas will get floated around a nice stack of papers in the form a report will end up on someone's desk and floating around by email. Unfortunately, 1/5 of the people who should read it won't because they have too many other things to be working on and of those 1/5 who do it will be very unlikely that someone in that bunch will do something or has the power to do something. All the while your CIO/high level manager can tell all other high level managers "We have a task force charged with reporting to us $XYZ analysis. Aren't I doing a good job".
If this were a high priority to your CIO, he/she would interview some key folks, including a few of you developer/admin types and then take action immediately instead of forming some bureaucratic committee who generates a report that gets debated on by management for months.
My 2cents at least. Sorry if I sound negative, but I just find committees to be an utter waste of everyone's time and really just a facade for the person who calls for it.
I think what he was getting at is that the CIO's main job is to provide "vision" to the company. Any "C" level worth their salt should already know what the department should look like. Pulling together a "task force" to address the issue is in my experience:
1) a smokescreen to make you believe they care and make you feel "empowered" so you do more work or not quit
2) The CIO is an idiot and looking for "vision" from subordinates
3) a "shiney thing" to distract you from something unpleasant on the horizon.
"C" levels set the tone for the organization, and there is very little that the guys/gals in the trenches can do to fix poor management. Keep your parachute handy at all times, and realize there is no such thing as a 20yr job anymore.
Pessimists.net - as if life wasn't depressing enough.