Slashdot Mirror
How Do I Become an IT/IS Manager?
link915 writes "For the last seven years I have moved around from job to job climbing the rungs of the IT ladder. I've worked in tech support, network operations, sys admin, and as a programmer. Two years ago I took a job with a company that has a small IT department. We are now hiring on more people and doubling the department, and along with this growth comes an IT manager. Now, I could stay and wait things out with the goal of taking over the IT manager's position someday; or I could look for a new job as a manager elsewhere. What are others' experiences with moving up the ranks in IT? Is it best to move on to another company or to stay where you are and try to get ahead there?"
1. Have you asked? If you have asked management when the company is growing if you could be an IT Manager explain why you would be a good one.
2. Show management incentives. Do you help out the new guys by being a mentor to them? When you go to meetings bring up your own ideas. Talk to management outside of meetings about your ideas?
3. Do you need a lot of management yourself? Make sure you do not need to be managed a lot, prove that you are self-reliant.
4. Do you have efficient education? 4 year degree, graduate degree, PHD. Having or working on an MBA is a big plus.
5. Do you show interest outside of IT? If not they you may want to.
As a manager of IT your jobs is looking out for the company first then IT second and make sure they work together.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Generally, a company will look for someone who has experience working for that company so they'll understand what sort of management style is required for the department/position. Jumping around between companies is NOT the way to get someone to notice you. Your best bet is to stay where you are and try to get a promotion. Have you already asked and been turned down for the new job managing your current IT department? If not, then that's an excellent place to start--let them know that you're interested.
More meetings, more stress, having to deal with morons all day long. I haven't yet known anyone who went into management who's happy about it- in fact I know several who dropped out of management they were so miserable. If its about money, you can probably make more by switching companies than you can getting promoted locally.
I still have more fans than freaks. WTF is wrong with you people?
Why would you want to be a manager?
Spend all your time in meetings and nagging lazy workers to do their job? Asking for money to develop improvements and being told you can't have the budget?
The only rewarding thing to come out of IT is getting into the guts of a computer and making it work, which is not something managers do. I've turned down several opportunities since this became my profession, and I'm glad I did because everyone I've ever seen who got moved into management became bitter, unhappy husks of what they used to be.
Are you already in a leadership type position? Do the people you work with already accept, and respect, you as a leader? If so, you would probably do ok in management where you are. If not, do you think you can gain that acceptance and respect?
If you don't think you can get that acceptance, then it is probably best to go else where, especially if you have never been in a meaningful leadership position before. All.....ALL managers go through that new manager floundering stage. Do it where you where and you might lose respect because people still expect you to do what you used to do. Do it else where and they are probably more forgiving. Additionally, at the new place you are introduced as being "in charge" and the frame of the relationship is set. You don't have to be a jerk, but you do have the right to be the boss. Don't make the mistake of assuming that you can be all buddy, buddy and still be the boss. You have to draw a line.
My general advice of my short, 9 year IT career is...find a BUSINESS with which you like to work, the technology will be irrelevant at that point.
-fragbait
- Becoming a Technical Leader by Gerry Weinberg. Gerry talks specifically about making the transition between being in the trenches and being a manager-type and just what you have to give up in the process.
- Journey of the Software Professional: The Sociology of Computer Programming by Luke Hohmann. This book is not nearly as well known (and read) as it should be; it's also a great source of references for hard research on IT development teams.
- The Mythical Man-Month (20th Anniversary Edition) by Fred Brooks. Just because anyone in IT management should read, understand, and believe this book. I deal with failing or failed IT projects for a living, and most of those failures occur for the same relatively small set of reasons.
Once you've read these three books, then decide whether you still want to be an IT manager.Bruce F. Webster (brucefwebster.com)
I don't know. I made the change years back. It's demanding, sometimes painful, but often very rewarding. I get a great deal of satisfaction from seeing my subordinates grow and develop. When I've had problem employees I've had a great deal of success in turning them around; another huge source of satisfaction.
The hours suck, the demands are great, and you often feel like you are in a no win situation. There are also perks if you do your job well. Once you've gained trust in an organization as an effective manager who enjoys a good degree of loyalty from his people while also getting results you gain lots of freedom in many subtle and not so subtle ways.
Of course this is just based on my experience and that of a few friends. I know many who've fallen into the PHB trap, and many who have just plain failed. YMMV.
This is an excellent point. Also, are you looking for opportunities to manage up, both by providing constructive feedback to your manager and by offering to take on tasks of his/hers to free up their time to do more important things?
I'm not saying be an ass kisser, I'm saying go after the managerial work when possible so you can be seen as already functioning in many ways as a manager. This makes it much easier to promote you when the time comes, and also allows you to build a case if necessary.
The exact same thing happened to me. I was IT Operations manager for a few years, found the non-working IT manager role to be boring and am now happily a solutions architect... all at the same company and without losing any pay (technically I'm still a manager on paper).
the amazing bc
just another guy doing IT
webnaut, music junkie, holes-in-head
Although this method could work, I believe that challenging the existing manager to a fight to the death (complete with original star trek combat music) would be more interesting.
1. Do you want to be a manager or a technical lead? If you are in true management you won't be able to put as much time into the nitty gritty, some geeks will find this distressing. A technical lead position has a leadership component but you would still have to get your hands dirty. If you play it right, you can take your pick of the most challenging or interesting work as a way to lead by example.
2. Can you handle stress well? If you can't, don't bother because management is not for you.
3. How are your political skills? As a manager you are doing many things: directing a group of people, exchanging resources with other departments, little turf wars, big turf wars, etc.
4. Are you able to look a person in the eye and order him/her to do something you know he/she won't like? What about asking the person to work unpaid overtime when you know that your employee would rather be at his precious snowflake's thanksgiving play? Managers get to make these decisions, many times knowing well that there is an obvious disruption of the employee's personal life.
5. Are you able to work a 9:00 AM - 5:30 PM work day with a 1.5 hour (working) lunch, knowing half your team is pulling 15 hours day for its third week in a row, weekends included?
6. What would you do if you get pulled into your division VP's office and asked to reduce your workforce by one warm body every 90 days over a 9-month period? Laying off employees, many of which used to be your own coworkers, is extremely hard.
7. Would you be able to draw the line and move on with firing an employee that doesn't measure up to your standards? Laying off people is really hard, but nowhere as hard as firing a person for cause.
8. Are you a problem solver? If you are a real problem solver, you will be sucked into "fire fighting" drills (at a previous job each of us managers actually had a toy fireman's helmet). This is an easy way to get fast tracked even higher, but it also means you lose time you should have spent taking care of your own people and dealing with your own deliverables.
9. Are you a territorial person? Each manager has his own little turf to share with friends and defend from intruders. Some managers are easier to deal in regards to this than others.
10. Are you willing to act as a shit shield for your team? One of the most important jobs of a manager is to protect his/her team so they can get their jobs done with as little external disruption as possible. Think of your past bosses and try to remember which ones were more respected, the ones that protected their people (within reason) or the ones that fed them to the wolves at the first chance?
11. Can you play golf? Regardless of sex, golf is a great way to get together with your team or other managers at your level. If the weather is nice you can schedule your meeting late in the afternoon and run it while playing 9 holes. There's bound to be a cheap course at a reasonable distance. We used to sneak out of Bethesda to play at River Road, a municipal course in Potomac. It was very nice and dirt cheap.
Pedro
----
The Insomniac Coder
Exactly. IT people think about the present, what needs to be done now in the company. IT managers think about the future of the company, how the department relates to the whole of the company and its vision.
-Tony