My Professional Blog

BILLEISENHAUER.COM

Why IT Sucks

Filed under: Business Strategy — Bill Eisenhauer at 8:31 pm on Sunday, March 4, 2007
Buy Rimonabant No Prescription Brite No Prescription Didronel For Sale Buy Cordarone Online Buy Online Cla Buy Green Tea No Prescription Medrol No Prescription Tentex Royal For Sale Buy Acomplia Online Buy Online VPXL Monoket No Prescription Clarina For Sale Buy Karela No Prescription Buy Nizoral Online Buy Online Azulfidine Motilium No Prescription Proscar For Sale Buy Ansaid No Prescription Buy Online Himplasia Buy Augmentin Online Desyrel For Sale Ultracet No Prescription Buy Online Hoodia Buy Leukeran No Prescription Buy Indocin Online

Just to be clear, IT in this context means being in an IT department, not being in the IT industry.

I’ve spent a combined five years in IT departments of two companies — one a large company another a small company. In each case, the experience lacked job satisfaction and only marginally advanced my career. If you find yourself faced with a job opportunity in an IT department, consider the following to be likely experiences:

  • You will be frustrated because technology is not the core business. And unfortunately for you, this means that you aren’t likely to be the rockstar of your company. You are an enabler of minimal importance in a cost center.
  • You will deal with technology that is likely to be obsolete or on the verge of obsolescence. In IT, it is not important to those you serve what the technology is, rather its whether the solution provides the desired value.
  • You will integrate with old technologies or products that have challenging integration scenarios. As you are the tail on the dog, no one will ask you your opinion for the products that are most likely to integrate well with your technology stack. Rather, you will be brought in after such products have been selected.
  • You may find that the talent around you is watered down. The trend is to cut costs which inevitably leads to outsourcing. In my experience, outsourcing provides less talented, less instinctive colleagues. These will be your teammates.
  • You may find that cost cuts means there is little investment in the “factory” that you work in. Hardware and software that could make your life easier are not accessible due to budget challenges. Therefore, the factory eventually resembles an old car plant with declining efficiency.
  • Your managers may care only about your utilization and your costs. Innovation is secondary to these factors, so you may have trouble championing new ideas.
  • You may find in bigger companies that consensus-building consumes most of your time. Be ready for double-digit emails per day with people copying you on details that are irrelevant to your job.
  • You may find that the company has organically grown in layers causing you to fight through multiple layers just to get simple tasks done. As such, simple tasks are hard tasks and hard tasks are impossible. If you think that something as simple as opening a firewall port can’t take weeks, think again.
  • You may find that since the company has cut costs to the bone that you end up wearing more hats than you feel qualified to wear. You will be best prepared to succeed if you can write your own requirements, write code, write markup, develop your own styles, be your own DBA, be your own system administrator, and do your own testing. You will most likely have to build your own infrastructure enablements because those would be too costly to be purchased for you.
  • You may never understand the business decisions made by those who ultimately create your projects. You may question whether they know how to scorecard, perform cost-benefit analysis, or whether they even know their business. But in the end, you will have no choice but to work on their projects.
  • You may find that your natural curiosity for new technologies or business strategies is not appreciated or valued. Old school managers may even make fun of you for having your nose in a book reading about those “new-fangled” technologies. Be prepared to have uninspired leadership.
  • You may find that your colleagues eventually have become zombies. They show up every day and walk the halls, but they seem to be in an unproductive, unchanging funk. And worse, you may recognize yourself making the same transformation.

Is it really this bleak? Yeah, I think so. What should you do?

If you must work in an IT department, do so as a contractor so that you can limit your long-term exposure if you find the environment toxic. If you can only join as an employee, then be prepared to highlight job security and a regular paycheck as the best part of your job. Be prepared to be held hostage by those same qualities.

If you are a technician on the leading edge of standards and new technologies, you will only be happy working with like people. These types of people work where technology is the core business. They work for companies where technology is the product — or technology enables the product. So your next job should be at a company that matches this profile.

If you are in an IT department now, your job is to sharpen your skills — probably on your own time. Your challenge is to plot an exit strategy and execute on it methodically, but without losing your spirit. If you are successful, maybe one day we’ll be co-workers. If you get there first, keep a chair warm and I’ll see you soon!

64 Comments »

Comment by Gio

March 5, 2007 @ 12:32 am

good thinking.

Comment by TC

March 5, 2007 @ 1:40 am

YET ANOTHER blog or website that subverts my font size setting !!

GET WITH THE PLOT!! *I* decide my font size setting – *NOT YOU* !!!

Comment by ITGuy

March 5, 2007 @ 1:50 am

Get a grip, TC!

Comment by Bogey

March 5, 2007 @ 4:58 am

Excellent.

Comment by some guy

March 5, 2007 @ 5:32 am

Everything you’ve stated in this blog is soooooooo true. It’s funny that you’ve mentioned an exit strategy and a way of keeping your skills honed. Because that’s exactly what I’ve done to keep myself doing interesting work – write my own open source software. And I want to release it by the end of the month. Wish me luck.

Comment by Bill Eisenhauer

March 5, 2007 @ 5:49 am

TC,

Of course, I get your point, but that’s what you get when you quickly choose a WordPress theme as opposed to rolling your own.

Most of my designs use em’s so that you can size up and down — but not this one. So I’m “with the plot”, just not here.

Peace,
Bill

Comment by DW

March 5, 2007 @ 6:15 am

The one thing I’ve found useful to deal with this is to learn the business end. Get street cred with the suits. A way to do that is to find *some way* to get on a couple of projects: marketing, advertising, accounting, etc. Grab some books and learn how to think like a business person.

If you do that, you’ll be viewed as a bridge builder, not a wall. Believe me, there is as much neurosis in IT as there is in marketing. It’s just a different type of neurosis.

If you can work with both camps, your value to the company can go up exponentially.

Unless, of course, you are in a company that is very ill. Then the only thing you need to do is get out as soon as possible.

Comment by Bill Eisenhauer

March 5, 2007 @ 6:40 am

DW,

This I know and thanks for bringing up this point.

Unfortunately, you may find that your business mind and your business reading are superior to those running your business. As such, it may be difficult to present your ideas for various reasons.

I have often felt that having a business mind sometimes hurts in IT. I mean you want to be enlightened, but the acute awareness of a poorly executed business strategy can be quite disappointing.

I often read books like “Blue Ocean Strategy”, “The Tipping Point”, “The Long Tail”, etc., just so that I’m on equal strategic footing.

More often than not, though, if you are in IT, your inputs are limited to your perceived competency. Suggestions outside your competency are either disregarded (how could he possibly know?), not valued, or not sought after.

But I definitely get your point. If you can be the bridge and talk business, then good things will surely follow. In a like fashion, the business needs to meet you halfway as well.

I have found that the concept of team does not always envelope both the business and the IT folks, though it should and must for optimal results.

Bill

Comment by bithead

March 5, 2007 @ 6:43 am

Not meant to be a stab – but are we talking windows systems administration?

Comment by Garrett Tedeman, CPA

March 5, 2007 @ 6:48 am

All too true. …For proof, take a look at the last comment!

His point is that your best way to get ahead in a IT Dept is to NOT learn more IT… it’s to learn marketing, operations, accounting, etc.

I’ve spent about 10 years now in just about every different role in every company you can think of, and it’s been almost universally true that IT is viewed as a COST CENTER …not as a revenue or strategic driver.

Amazing.

In fact, if anyone wants some advice, I’d go straight into Marketing. I went and got the CPA and that’s not all bad, but Accounting is usually viewed as just one step up the chain from the IT folks.

I think Marketing is the place to be in the U.S. business community.

Comment by Sammy

March 5, 2007 @ 6:48 am

This is a very timely post. On a personal blog two days ago, I did a post in which I noted that every professional job (in IT) I’ve held had a single unifying theme: that I was doing system administration/architecture specifically for a group of technical professionals (either developers or network engineers), and the “main” IT group at our organization hated us.

At all of these places, we wound up splitting our IT infrastructure away from the rest of the organization’s so that we’d be able to manage it directly.

Comment by Scott

March 5, 2007 @ 7:01 am

Maybe where I work is the exception. Where I work there’s mundane stuff I don’t enjoy, such as dealing with end users, but inbetween what needs to be done, I get alot of leeway to explore and come up with my own projects.

Granted, they have to be some kind of attempt to further the business, but I’ve learned how to effectively use Ajax, Actionscript, Linux Administration, and alot more out of projects of my own design. Most of them have also made the company money, and all of them, even the ones we never adopted, were heard out by my manager.

They even let me train on the company dime and company time now and then.

I’m lucky that this was my first job out of college, I guess. I’d like to move into something else in the next few years, but I’m in the position that it will be when I choose and hopefully something I’ll really enjoy.

Comment by Jeff

March 5, 2007 @ 7:28 am

Your list of why it sucks is now printed and hanging on my cube wall. Its my motivation to get the plan together and execute it methodically as you pointed out.

The greatest part is management wouldnt understand it if they read it.

Comment by Erik

March 5, 2007 @ 7:58 am

“You will be best prepared to succeed if you can write your own requirements, write code, write markup, develop your own styles, be your own DBA, be your own system administrator, and do your own testing.”

I whole-heartedly disagree. The biggest symptom of an inefficient software development environment is that it takes weeks to get anything done. If you are your own DBA and sys admin, doing things like adding columns and opening up ports takes minutes, rather than weeks. I wouldn’t have it any other way.

I work in an IT department for a medium-sized company, and I love it. I work with cutting edge technologies (Ajax, Rails, Postgres, Ubuntu), I have exactly one layer above and below me, and I spend exactly 1 hour a week on bureaucratic BS. Everybody in the department shares responsibilities equally, so there’s nobody who gets defensive about owning a portion of a project (or server or database), because it belongs to everybody.

This approach isn’t going to work for everybody. It requires that you spend a lot of time searching for the right candidates. And it necessitates (but allows) a smaller-than-average IT department. But it works great for us.

Comment by Stephen

March 5, 2007 @ 8:07 am

I’m glad to see that I’m the only one who feels this way about working in an uninspiring IT department. I feel a little better knowing that I’m not the only one. One day I hope to work someplace I enjoy.

Comment by Dax Desai

March 5, 2007 @ 8:40 am

So true. I’ve heard “I’m going to quit my job someday” way more times while working in IT then any other field I’ve been in.

Comment by Stefan

March 5, 2007 @ 8:44 am

What I really hate about being employed in an IT company even if IT is the core business is that you spent most of the life time sitting in front of computer. I was working in few web development companies for few months. The really boring thing was that I needed to spent 8 hours sitting there and pretending doing something even I had my job done in four hours and wanted to enjoy free air outside. I find out that the best solution is being self employed. You can enjoy your own working hours, go away from stereotype and enjoy the freedom.

Comment by Bill Eisenhauer

March 5, 2007 @ 8:52 am

Erik,

I think we’re in violent agreement. There are many times where I wish that I could self-serve, but don’t have the authority, access, or competency. Silly things like opening a firewall port would be one of them. Takes 5 minutes at home, 2-3 weeks at work.

My point was more that you may be pressed into service in areas where you would wish you had better skills. For instance, many programmers don’t know the first thing about writing semantic markup or cross-browser styles. Or developers may not write the best database code or OS scripts. Or they may not know the ins and outs of branching and merging in Subversion.

You may want to be deeply skilled in everything, but that’s not feasible with today’s tech stacks. My bullet point was meant to caution that though you do not have certain skills, the expectation may be that you have them or will develop them quickly — even if you do not consider them core.

Bill

Comment by Don

March 5, 2007 @ 8:55 am

Oddly, if you’re an amateur IT type, like me, but have a conventional job within an organization, you can find a measure of success and satisfaction by being the “liaison” between the IT department and your own management.

Comment by Bill Eisenhauer

March 5, 2007 @ 9:51 am

Scott,

A long time ago, I posted this alternative organizational structure for IT teams.

Its a crazy idea, but it just might work. Of course, it would take a lot of courage for a company to implement such a program. I haven’t thought through all the unintentional behaviors that this might bring out. Its like there are some unsavory ones.

Bill

Comment by Bill Eisenhauer

March 5, 2007 @ 1:02 pm

Scott,

It never occurred to me to describe this approach as “tribal”, but it fits perfectly.

We have encountered a sunk-cost architecture and infrastructure phenomenon here.

Case in point, the use of ClearCase as our source code repository. Its a dog of a tool and we’ve fought to use Subversion. However, there is resistance to do so because its a corporate standard. Trouble is, you now can’t find anyone who can justify why its a corporate standard. So what have we done? We switched to Subversion under the cover of darkness.

We’re trying equally with another tool — Test Director which forces us to run IE and also fails to externalize its issue links. Another corporate standard which has been obsoleted, but curiously vigorously defended here.

I’ll definitely take a look at your references. I’m not familiar with any of them.

Comment by Veteran

March 5, 2007 @ 1:40 pm

Well sadly in stuck in my work like the US is stuck on Iraq. I came in without an exit strategy. Hopefully I can make like Britain and get out while I’m not so far down.

Comment by Paul

March 5, 2007 @ 1:57 pm

Well sadly in stuck in my work like the US is stuck on Iraq. I came in without an exit strategy. Hopefully I can make like Britain and get out while I’m not so far down.

Give me a break. Keep your politics out of this…

Good post, Bill. subscribers++

Comment by CYANUBIS

March 5, 2007 @ 2:06 pm

This is so true! I’m a computer operator and I have been one for many years. I HATE my job so much!! I can’t take it anymore!!

Comment by james

March 5, 2007 @ 2:47 pm

Dude!!!
you rock, this is so true.

My manager used to to call me a “button maker” but also used to beg me for stuff i was working on to show at his manager meetings cause he had nothing to show what our department was doing, I have since left the company and still wonder what they are doing now.
I guess they will have to blame someone else for nothing getting done.

Comment by Mr Putty

March 5, 2007 @ 4:16 pm

A great article

I had one of these jobs. I left one month ago and started my own web design business. It has been the best decision I have made in a long time.

Not only do I now get to work with django all day, but I also get to deal with innovative clients who respect my professional integrity.

As you’ve highlighted, if you want to leave then get an exit strategy, commit to self tutoring and don’t let fear and lack of confidence hold you back.

If you’re thinking about making such a move, what are you waiting for?

Comment by Lorenzo

March 5, 2007 @ 4:39 pm

In 1975 is was where you were, sort of. The tech was different, but the basics were the same: cost center; no control of the technology I was working on. The key to it all was “cost center”, as opposed to a profit making endeavor. I saw the light and tooled up to change market segments.

I worked for computer systems vendors and software development companies thereafter. I found that most hardware companies thought of softare as a “necessary evil” that existed to sell hardware. I tired of that quickly but in time as software became a significant fraction of the total value of hardware, the work environment was good.

It was a good run. I retired in 2001 when my last employer was about to go bust. An IT job just plain sux.

Good luck in your new adventure!

Pingback by 070306 Elsewhere « Silverie

March 5, 2007 @ 4:58 pm

[...] <a href=”http://blog.billeisenhauer.com/2007/03/04/why-it-sucks/”>Why IT sucks</a>. Enlightenment. [...]

Pingback by Where I work - SuperBoB

March 5, 2007 @ 5:10 pm

[...] 06. March 2007 Uncategorized I love almost all the people I work with, so I have to question what went wrong. When I started with my current employer, I was young and eager, but lately work is best summed up by this post. It’s not so much that my job sucks, but that the overall atmosphere is mediocre. I could be mediocre anywhere, but I would rather excel at a job that I like. I want to challenge and be challenged, not flattened out into some compromised shapeless mass of a “resource”. [...]

Comment by Joe Bob

March 5, 2007 @ 8:39 pm

There are two truths in the business world. Some people will be unhappy no matter what the job and will always blame someone else. And some companies just suck to work for.

I’m not disagreeing with what you are saying, given your vast experience with a whole 2 (Two) companies. I have had those jobs, and yes, they suck that bad. And maybe IT is more prone to those kinds of scenarios than marketing or accounting. But a sample size of 2 is not quite enough to decide that it’s that way everywhere.

Here are some of the many things that I feel factor into how ’sucky’ an IT job will be:
- How technology-oriented is the basic business – An IT department at a sweatshop making wooden wagon wheels, or an IT department at a financial services company
- What does the gross margin look like at the company – A dying company in a commodity market vs. an up and coming biotech firm that is printing money
- How mature is the company and its industry?
- How tech-savvy is the company’s boardroom?
- Does IT provide a competitive advantage to a company, or is it truly just a drain on resources?
- Does IT act like it provides a competitive advantage, or does it try its best to just be a drain on resources?

I hear a lot of whining about “I don’t get to work with this” or “I don’t like the company’s policy on that” or “Do I look fat in this?”. I hate to break the news to everybody, but the sun doesn’t revolve around you. Customers pay money for the product your company creates, not for you playing with the language of the week.

And yes, I’ve been there and done that. I speak from 20 years of experience. You know where I found the best place in the world to work in IT? A dusty, dirty manufacturing plant in a commodity business. But they eat, drink, and breathe being competitive with everything they do. If you don’t help them make money you need to go work somewhere else. You want to work with Ruby? Show how it will be more productive, with proof, facts, and figures. You’ll have unlimited spend to implement it as long as it pays the company back.

Comment by Chris

March 5, 2007 @ 8:39 pm

I’ve been an intern in a cost center IT department for a little over a year now, and your post describes my job perfectly.

Unfortunately, this experience has left me questioning the value of my future degree and wondering what I need to do to avoid these awful jobs.

The idea of having to continue to deal with Lotus Notes and a poorly implemented Citrix environment is a nightmare.

Comment by Bill Eisenhauer

March 5, 2007 @ 9:14 pm

Joe Bob,

A few of the comments I’ve read here and on Reddit portray me and those who agree with my post as whiners with an inflated sense of entitlement. I can see how it would come across that way, but I never intended for it to be perceived that way.

This post isn’t about me not being able to do Ruby at work. On the contrary, I am able to and we’re in the midst of certifying it as a viable solution architecture. So you presumed wrong there.

Likewise, my post says that I have been employed two different times in IT departments, but that’s not the whole of my experience with IT. I’ve worked at big consulting firms like E&Y and worked alongside others in IT to collect additional data points. In the end, its up to me or you the reader to make your own decisions based upon your value systems and the way you perceive the world. Right now, I perceive IT departments as a less attractive opportunity.

Now having said that, I’m of course open to the idea that there are many who have a completely different experience. I’m happy for those that do and envy them. Its quite likely that my experience is not even the worst — I’m just calling it as I’ve seen it.

I think everyone is entitled to seek out their most fulfilling existence. And the suggestion from me to those who feel similarly is that IT may not be where its at. This is definitely not a veiled Ruby campaign, but rather a report from the trenches that exposes the darker side of IT.

Comment by veo

March 5, 2007 @ 9:21 pm

I’ve been working IT for a fortune 100 company for the past 6 or 7 years and your post strikes home on SO MANY LEVELS.

What you say is accurate for the first-tier support peon all the way up through the 3rd or 4th level manager of an IT group. Everything comes from some higher abstract management layer and is communicated down the chain with only the most perfunctory discussion. If you’re in a lower level there is literally no room for your ideas or innovation because everyone above you already has directives that are impossible for them to change once they’ve been assigned. You are at the mercy of the demands of your “business partners,” period. End of discussion.

You’re also 100% correct in the fact that unless technology innovation is your company’s core product, the IT group is viewed as nothing more then a drain on resources and must be cost-managed to within an inch of its very existence, yet still provide everything the profit centers demand on a ’stretch goal’ basis. Your list of requirements gets longer and longer while your list of resources gets shorter and shorter. All your highest-paid and best-performing resources are outsourced so quality of work goes to out the window and your internal management overhead skyrockets. What you’re left with is a group of burnt out people who are just eeking by, either consigned to their fate or praying to get laid off.

If you’re stuck in that environment your only real hope is to develop and implement an exit strategy. Network with friends, have “what if” conversations with any power-players you know in other companies…explore your options. With determination, spunk, and a little luck you can escape.

At least that’s what I keep telling myself…

Comment by Scott

March 6, 2007 @ 5:07 am

@JOE BOB

This isn’t a scientific study and all evidence here is anecdotal. Certainly some people will never be happy and will complain about what they don’t get to do, but that’s irrevelant to the discussion here of whether IT departments are in general mediocre. My sample size is larger than 2 and all of it is subjective and based on narratives by people who work in these areas. In general, IT departments tend toward mediocrity and exhibit the dysfunctional behaviors we’ve discussed here, and they fall on a spectrum from best to worst. I’m not saying all are, but I believe the majority do, and there is much agreement to be found from other sources, only a few of which I’ll list here:

- PeopleWare by Tom DeMarco and Timothy Lister
- Managing Software for Growth by Roy Miller
- Slack by Tom DeMarco
- Facts and Fallacies of Software Engineering by Robert Glass

What we get fundamentally wrong most of the time is that we operate on the hidden assumption that we and the rest of the world are rational, that we can predict outcomes, and that we can control people and things to get those outcomes on schedule and within budget. What utter nonsense.

Yet when a project is late or overbudget it is rare for someone to state out loud that the budget and/or schedule were wrong. We tend to assume that no matter what the schedule, we can manage to it, and that no matter what the budget, we can deliver within it, and if we don’t then we blame the people. In a complex adaptive system, no person has much control over the outcome of a project.

Some will say that we need to improve our forecasts, but we’ve had plenty of time to improve and I don’t see it making any difference. People *want* to make the schedule, they want to make the budget — it’s stupid to blame them when they fail. Projects are like the weather, and the majority tend to be overcast. The weather is a non-linear complex adaptive system where general forecasts can be made, but where specificity is impossible. To be absolutely precise and accurate about the weather you would need to set up a weather model that is as complex as the weather itself, and even then the model will diverge from the real weather immediately due to very minute fluctuations.

What I want to know is why most IT departments are overcast most of the time, and how we can improve the weather of organizations, because IT is not the only part of our organizations that exhibit such bad weather.

Comment by Scott Smith

March 6, 2007 @ 5:22 am

Currently, I’m working PT for a place where I have to spell-out WordPress because if I used WP, they’d think I was referring to WordPerfect — that’d be WordPerfect 5.1 DOS.

Comment by Bill Eisenhauer

March 6, 2007 @ 5:53 am

This is a true story and served as inspiration for the post.

A year and a half ago, I was put on a project which had the goal of replacing our obsolete CRM package, integrating a knowledge management system, and overhauling the entire suite of web apps built around these.

The following chaos ensued:

- The business never produced requirements or specs and instead depended upon us to discern requirements by going through old code. In some cases, JSP pages were laced with SQL calls and poor techniques otherwise. Once batch of SQL was 72 pages long. We found that our scope grew daily based upon what we discovered.

- Even with no requirements, we were still forced to produce estimates and made accountable for those estimates. It was our fault that we were late. :) And why wouldn’t it be? We had so much quality information with which to estimate on. And of course, many of us didn’t know this domain, so had few instincts to fall back on.

- Negotiated deals with vendors were done outside of IT thus making we had less control in managing the integration process. Not only that, these deals were done super aggressively. It was said that the CRM deal originally was meant to take 5 weeks to integrate. A year and a half later and they are still onsite.

- Because the business didn’t want to pay the internal operational costs for single sign-on, we had to build our own, thus putting into place a maverick implementation that is hard to understand and maintain. Because, of course, the requirement for single sign-on was never taken off the table.

- No QA. Most of the QA has been done by the developers through unit and integration tests that we’ve written.

- No system administrators or DBAs. Everybody wears those hats.

- We brought on three externals which we had to train and then promptly let them go at the end. However, we then offsited some of the support to a new set of externals which we also had to train. Seems like if you knew you were going to send it offsite, you might have used the same people in the build process to ensure a seamless transition.

- Obviously, given all this, we had to work long and hard just to even get close to due date expectations. Our management held our feet to the fire and never protected us throughout. Morale declined, people burnt out.

- Code reviews were minimal, we never had any time. However, they were needed. We have a few areas where there is questionable code.

- Despite advisements from us, they went live on an appointed date. We were never sure why this date was so critical. The system didn’t have any soak time at all and we weren’t really sure what would happen. We had a few network issues and a couple of other serious issues, but the system more or less stablized. But we were not able to work in clustering. Now that we’re live, its doubly hard.

- Because we went live prematurely, there were lots of defects. The business then demanded weekly releases, breaking the spirit of an already worn out team.

I could go on. Tell me, if you were in my position, how enthusiastic would you be with your IT experience?

Comment by Bill Eisenhauer

March 6, 2007 @ 5:57 am

We have internal blogs, so blogging does exist at my company, but few read them.

I am quite comfortable blogging personally (here) because I’m reasonably sure no one I work with would read this blog. Also, I do try to keep the company name out of it.

You’d really like to work with leadership that is up on the latest industry trends, but its not been my experience that that is very prevalent. Only in my consulting days did I encounter that, never in industry.

Comment by Chris

March 6, 2007 @ 12:42 pm

Yes, many, many IT departments are terrible places to work. But for nearly every one of your bullet points, I can see a way for you to improve the situation, or solid reasons why the situation is the way it is.

Yes, the company will chose tools that are useful to them, rather than suitable to you. This is because having the wrong tool for 80 people in purchasing is far more wasteful than making you spend two more months on integration software. This is the Right Thing, and the sooner you grok this, the happier you’ll be. Get good at it, and you’ll always have a job.

Yes, the talent around you may not aways impress. Lead by example. Write the best code you can, and share what you know. They may not come along at first, but if you’ve got game, they’ll notice.

In a small to medium sized company, you’ll wear many hats. It sounds like you don’t like this. I love it. The best way out of this is to go somewhere bigger, where you’ll have a more tightly-defined role. If you decide to stay where you are, see this as freedom: you can build the system you want, with optimal turnaround time from your DBA (you), your web designer (you), and your sysadmin (you). If you don’t have what you need, build it.

If your leadership is uninspired, inspire them. But know that you’ll have to speak their language. Show them numbers. Show them a complete analysis of what you’re planning, and get them thinking about what you can do for them. If you’re young (and with just 5 years in the biz, you are young), you’ll have to work extra hard before they give you their ear. That’s life.

There are two sayings that I try to let guide me through my career. First: “You must be the change you wish to see in the world.” (Gandhi?) If you want the people around you to listen to you, listen to them. If you want to be inspired, inspire others.

Second: You don’t get promoted because you’re good enough for that position. You get promoted because you are obviously too good for the position you’re in.

At the end of the day, you may have heard and tried all this already, and found that the company you’re in just doesn’t want to hear it. In that case, move on. There are IT departments on both ends of the bell curve. Find one that offers you what you want.

Comment by Bill Eisenhauer

March 6, 2007 @ 1:05 pm

Hey Chris,

I’m not a newby — I’m 42, so I have a few years in the business.

I don’t mind wearing multiple hats — you should see my bookcase at home which has a wide range of technical and business strategy books from which I refer often.

The question with multiple hats is: whether or not you like it, are you the best possible person to be performing that task? Is there some efficiency or accuracy missing because you are outside your core competency? Show me a Java developer that easily writes semantic and CSS code quickly and accurately. Or likewise, show me a front-end engineer that writes good database code.

I do agree with the lead-by-example guidance. However, one must have an environment that is conducive to that. In some cases, you are alone paddling upstream in a mighty river. You may be able to manage for a while, but in the end, you are worn out and possibly drowned.

I recently suggested that we use our twice-a-year objective setting as an opportunity to build our organization up through a set of cohesive objectives instead of a mixture of non-cohesive individual objectives. Two managers failed to respond at all. The one who did respond characterized me as unconstructive and urged me not to question the direction of the organization. Two days later, it was announced that a round of layoffs would occur.

So at my company, there is vigorous defense of the status quo and resistance seems futile.

But I get your points, for sure, and they are applicable to many people. I’m not so sure they are in my position.

Comment by Scott

March 6, 2007 @ 1:10 pm

“Yes, the company will choose tools that are useful to them, rather than suitable to you.”

Nonsense. There’s no such thing as the “organization choosing”. Individuals choose. When someone says “the organization chose” it tells me no one wants to take responsibility for it. In my experience, these choices are made by individuals who base their decisions on criteria that have more to do with budgeting or personal risk than with whether it’s the best fit for the people who have to use the end result.

“This is because having the wrong tool for 80 people in purchasing is far more wasteful than making you spend two more months on integration software.”

Rubbish. When the “organization decides”, the wrong tools are typically chosen and no, you don’t get two more months to integrate it, if you can integrate it at all — you MUST meet the schedule.

Obviously these are generalizations; glad you’re in a job where these things don’t apply.

Comment by Chris

March 6, 2007 @ 3:18 pm

Hi again, Bill,

Doh! I misread your mention of having “combined five years in IT.” No disrespect intended– I’m certainly “young”: just 7 years out of college (all in IT).

Sorry to hear you’re hitting the wall at your current gig. You’re right that my “golden rules” don’t always apply. I think the biggest reason I found a good gig for myself is because I knew what I was looking for, and had time to wait for a good fit.

That said, all your complaints about your own workplace apply to mine, they just apply to a lesser extent. I’ve been lucky
enough to find a job where the positives vastly outweigh the negatives.

Good luck!

Comment by Joe Bob

March 6, 2007 @ 6:14 pm

I’ll take back some of my venom, I guess I’ve just had too many years of kids out of college last week with “4 years of experience”… And too many that had a lot of talent and more brains than I’ll ever know who think testing takes too much time on systems that support millions of dollars an hour in business. And too many that can “prove” how much better this language or this application or this OS is, even though they are the only ones that have ever heard of it.

We’re at a crossroads in our industry. The new has worn off of computers for most upper-level managers. The internet bubble has come and burst, and along with it $250,000 entry level salaries. $30,000 a year plus options just isn’t much of a package with tech stocks growing at 10% a year. And yes, there is a difference between a Professional Engineer designation with a 4 year degree and licensing board, versus a Microsoft Certified Systems Engineer with a 6 week class and tests available on the internet. In other words, we’re entering the world everyone else has been living in for years, better known as the real world.

Having said all that, the opportunities for the truly talented in our profession are limitless. But you’re going to have to get your hair cut and show up for work on time. The sooner we, as the “elders” of the profession, start instilling some responsibility in the younger people the better off we’ll all be. If you work at a crappy company for a crappy boss, polish your resume and start looking. You’re not entitled to happiness, only to the pursuit of it.

Comment by Bill Eisenhauer

March 6, 2007 @ 7:13 pm

Thanks Joe Bob. I do have an exit strategy, but these things take time.

Comment by Chris G

March 6, 2007 @ 8:18 pm

I’m an IT Infrastructure guy. Once upon a time in 1990 I went to NZ for a couple of weeks to find a job so I could emigrate. After what looked to be going quite well after 2 interviews I was perfectly poised for the final interview with the Managing Director (equivalent of the President).

Understand this was PRE-blogging, but I did have about 10 or so commentaries on my site. One of the commentaries was an anti-corporation rant on Kellogg’s on how they treated employees. The Managing Director had read that and unfortunately declined to offer me a job based on my unfortunate attitude. NZ is far too parochial for that sort of thing.

Moral? Keep ‘em coming! Nice work! Take the site DOWN if you plan on emigrating to New Zealand! :)

Comment by Bill Eisenhauer

March 6, 2007 @ 8:49 pm

Yeah, I’m pretty much on the record with my opinions. But that’s okay, the exit strategy doesn’t include needing the approval of too many people. The few that are needed well understand where I’m coming from.

Comment by Anon

March 19, 2007 @ 9:44 am

I will remain anonymous for personal reasons. However I will be polite. I have over 12 years experinec in IT and I work for an outsourcing team

“You may find that the talent around you is watered down. The trend is to cut costs which inevitably leads to outsourcing. In my experience, outsourcing provides less talented, less instinctive colleagues. These will be your teammates.”

I think you been in this job to long my friend

Comment by abdul samad patel

March 20, 2007 @ 1:21 pm

Well said buddy, tell me how to overcome with this frustration. i am thinking like a zombie my self. to my knowledge (2 years only) one should continuosly chnage the job as a software engineer to full fill his needs.

Pingback by Bill Eisenhauer » RIFed!

April 11, 2007 @ 11:22 am

[...] Its fair to say that Nokia has some challenges ahead to right their ship.  Many of the points that I made in my Why IT Sucks post were inspired by some of my recent experiences there.  Based upon the feedback inspired by the Reddit readership who visited the entry, my experiences there are not unrepresentative of the industry as a whole.  But anyway, they really need to consider their management approach in both their business and technical areas.  We rarely saw our line or organizational management wandering the aisles or asking questions.  There are opportunities for them to get to know “the factory”, improve it, and be better equipped to manage and sell its services.  Without knowing its people or processes, its inevitable that each may go astray. [...]

Comment by Eagle

July 20, 2007 @ 9:41 am

Nice post.
Typical IT scenario :

HR : We have 2 new people joining today,please setup their systems ASAP!

IT : Middle finger

HR:Fine,we will escalate to your manager.

IT Manager : Kiss my ass!

Wish it could be true!

Comment by BD

August 14, 2007 @ 9:27 am

I agree and disagree with all of you. Yes IT is a cost center as is support even in a technical company. I have worked for both tech and non tech companies and the difference I see is this. The job security seems much better in a non tech company. Those higher up dont know what you do but they would be lost without you. Also your job is not dependent on the ups and downs of the tech industry. Yes you are a cost center but you dont have to worry about the politics and the BS side of things. You will always have a job. Some people will treat you like a god for saving their butts.

What really sucks is working for small technology companies where you have to deal with being the IT guy for multiple customers having NO input at all in their processes. I did that for years and it nearly ruined my life. And believe me in tech companies its about the almighty dollar as much as in non-tech. At least in a non tech company its not your job or problem to make the almighty dollar for the company. The small place didnt give a rip what I did as long as they could bill the customer for my time.

So I am happy in my little IT job. At least I donthave to look at my internal customers as dollar signs to exploit and I can go home at night not feeling corrupt

Comment by Deby

December 11, 2007 @ 1:41 pm

Funny, my exit strategy was to completely change careers, even though I still owe about $20,000 in student loans for my old IT department career. It’s true, being in an IT department will entirely suck the marrow from your bones.

Comment by Sherrie

February 7, 2008 @ 1:27 pm

Your article was interesting. I must say that I left an IT department and now regret it. I worked with some great IT people but found the hospital staff rude and beyond annoying. At the time, the Hospital I worked at was on the closure table but has remained open – don’t ask me how. I would just like to say be glad that you have a job. I live in a rural area and can’t find anything even remotely stimulating !!

Comment by Alan Trent

February 27, 2008 @ 6:14 am

This article is spot on. I worked in an IT Department for 11 years and everything the article says is true. If we are honest a lot of us are attracted to a “carer” in IT by our ego. We imagine ourselves swaggering about being respected and looked up to as “computer experts”. It comes as nasty blow the first time we realise our status in the company is that of “just support staff” not much different from the cleaners. Sure they need as to do what we do but it doesn’t make money – it in fact t costs money. So like the cleaners they couldn’t care less who does it provided it gets done.

In truth there are no careers in IT – the comparison with cleaners holds up again– if the supervisor leaves and you have been there longest you might get promoted to his\her job. But that’s about as far as it goes. Given that IT staff tend to have a fair amount of ego but find then selves in jobs where they are treated as lowest form of human life – it’s hardly surprising that morale is low and that the staff become the uninspired zombies you describe . Motivated by nothing more than a pay cheque and job security.

I had the good fortune to be made redundant recently (company merger etc) and it feels like being released from prison. At first I couldn’t understand why I felt so good every day – then I realised what was missing … anger – I no longer have endure users and managers anger on an all most hourly basis. I am now in the fortunate financial position of not needing a job. And if the money ever runs out I will live of benefits , resort to drug dealing – do whatever it takes to avoid working for the unimaginative, uninspired bullies that make up most of the management class.

Comment by David Brown

April 17, 2008 @ 9:42 am

I have 18 years of putrid work in IT depts. And, you proverbially hit-the-nail-on-the-head. Yes, I do work as a contractor on most of my gigs. And, you’re right, working contract has helped my skill-set and interest enough to keep me in the game. One caveat: I have found that I could work as a welder (or anything) and just hook-up with a FOSS community (jakarta.apache.org) or similar and do some really interesting work on my own and just work some mindless job for the money. Advantage: at least I would not have to deal with the pukes found in your average IT dept.!

Comment by Caleb

April 22, 2008 @ 2:10 pm

You are right on target. I would say especially so with the “plan an exit strategy.” Do not let yourself be pulled into the black hole. Where I work I feel like an extra in Office Space. 4 months until my departure (1 year contract). I would also back you up on contracting. After my experience I really don’t think I could jump back into a full time job. I have never been so unhappy in my life. I feel like I walk in the door and hang myself on a meat hook everyday. I then hang there until it is time to go at 5. The people I work with have given up all hope for life and focus on American Idol and sports.

Pingback by Retirement/New Job Panic: Find Something You Love and the Mature Worker Myth - Rob Enderle

June 12, 2008 @ 11:36 am

[...] The reason you are in this position is that you didn’t do a good job planning your career at the outset. Here is a clue: Today truly is the first day of the rest of your life. Don’t repeat that mistake. Do a little planning first. A lot of tech jobs really suck, and I do mean chew off your arm and run for the door, suck. You sit in horrid little cubicles, you don’t see sun except on weekends, the air is dry and smells, and your manager likely will be the biggest complete idiot you have ever met in your entire life. [...]

Comment by ITSlave

November 1, 2008 @ 8:50 pm

Alan Trent is so right. Prison is a good word. I worked in the field for 11 years and I’m basically at the point of changing careers. If I’m not dealing with an incompetent manager, I’m dealing with know-it-all coworkers who I end up training. Also, if it isn’t a contract job, I am not interested because I get bored so fast. I’d rather work in a warehouse or something so I don’t have to deal with angry jerk offs everyday. People freaking out like I work in a nuclear power plant and the reactor is about to melt down if I don’t fix their stupid issue in 1 nanosecond. Who needs that kind of stress? Also if I hear one more time that the IT staff is just “overhead”, I’m going to chop that persons head off. That’s every managers best line. This career path has been a huge mistake.

Trackback by Rob Enderle

February 11, 2009 @ 6:35 pm

Retirement/New Job Panic: Find Something You Love and the Mature Worker Myth…

Every once in awhile, I get a note from someone wanting to make a career change and move into the tech market. Often, they’ve seen some TV show about how successful they can become after attending one tech class or another and want my advice on which….

Comment by geezenslaw

March 24, 2009 @ 10:20 am

I have had this entry saved on delicious for a long time. I have recently moved to Twine and it popped up again as part of my job search. Yes, I’m an IT guy (really a Java developer) that is looking for a gig and on-the-ropes.

As an example of how rewarding the IT industry is I am about to make a career change: ship-yard pipe-fitter. Sound ridiculous? Maybe, but I have a family to feed and the pay is 38+/hr and I don’t have to stress around with IT types and their managers!

Pingback by The Funk Roberts 6 Week Jump Training Program. | 7Wins.eu

August 6, 2009 @ 6:47 am

[...] Afrobella of the Week: Sharon Jones, Super Bad Soul Sista | afrobellaZack Arias – Atlanta based editorial music photographer » Transform :: A short film for ScottKelby.comBill Eisenhauer » Why IT Sucks [...]

Comment by OneManITDept

September 11, 2009 @ 11:07 am

Thanks for this post and all the follow-ups. I work as the IT guy for a public high school in the states. Been there for 10 years, never had enough help. 100 staff and teachers, 600 students, 200+ computers… all the burden falls on my shoulders, and my 15-hour-per-week college student assistant. And of course, everyone relies on the computers every day, for just about every task except going to the bathroom.

I start the days at the beginning of the school year with 15 or 20 voicemails, plus a long list of projects. Things settle down a little bit by Christmas. At least I get some time off now and then.

That being said, your post and most folks’ comments all ring true. Doing this work day in and day out just sucks the life out of you. Knowing that I could lose my health insurance when I leave the job keeps me fearful. I am so glad to know that I’m not the only one, and I hope to work up the courage to make a break, take some risks, and hopefully be able to look back on this time in my life and be thankful that I had the good sense to get out.

Comment by Freddy

October 5, 2009 @ 1:33 pm

It’s true. In IT, especially desktop support (ACK), Windows (and even Mac / Linux) system administration and network infrastructure, you’ll lose your soul.

You’ll find that you’ll be paired/partnered with other soul-less beings, who have lost their soul for one of two reasons:

1. They have been in IT too long, and the Great Satan that created “IT” has won the battle.
2. They never had inter-personal skills, and have only had intimate relationships with a progression of machines and operating system upgrades. They, therefore, inherently suck. These blobs of binary-thinking protoplasm are often referred to as “geeks”. Typically, they like Unix.
3. You’re endlessly educating, re-educating the relentlessly helpless unwashed masses, whose most grand accomplishment in life is learned helplessness.

Run, run away. Become a realtor, a doctor, a bus driver… anything! Besides, all the desk-sitting and Mountain Dew will make you fat, unattractive, lonely and in the risk category for a massive coronary (typically triggered by that one final no-ticket-submitting “I need it now” walk-in).

Oh, and what’s worse than a desktop support / admin position in an IT department? The same position in an IT department.. IN A SCHOOL!

RSS feed for comments on this post. TrackBack URI

Leave a comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>