IT in a Bubble

It is an old story in SMB IT, IT managers who get their start young, stay with a single company, work their way through the ranks and become venerable IT managers who have never worked outside of their current environment.  Just like the “good old days” when people stuck with a single company for their entire careers, this too sounds like a wonderful thing.  But IT has long rewarded “job hoppers”, those technically minded folk who move from shop to shop every few years.  The lack of direct upward mobility within single shops has encouraged this process – incremental promotions could only be found between companies, seldom within a single one.

Some people support and some people dispute the idea that there is value, or significant value, to be had by changing companies.  The idea is that by moving between environments you will glean techniques, procedures, processes and general experience that you will then bring with you to your next position – that you are a cumulative product of all of your past environments.  This concept, I believe, has some merit, moreso in technology than in other fields.

In technology fields, I believe that the value of moving between jobs, after a reasonable amount of time, is generally of much better value than is staying put.  The reason for this is relatively simple: Most small businesses lack an ecosystem of support and training for IT professionals. It is well known that IT professionals, working in small shops, lack the interaction with peers and vendors generally accepted as necessary for healthy professional development and which is common in enterprise shops.

An IT professional, after spending many years in a small shop, effectively all alone, tends to feel isolated lacking the professional interaction that most specialists enjoy.  Most small professional or artisan shops have a number of specialists who work together, share research and experience, are encouraged to work with competitors or vendors, to attend trade events, training, etc.  Few fields share the odd dispersion of IT professionals with only one or two people working together at any given company with little to no interaction with the outside world or with peers at other companies.

This isolation can lead to “IT insanity” if left unchecked.  An IT professional, working in a vacuum with little to no technical or professional feedback, will lose the ability to assess themselves against other professionals.  As often the sole provider of technology guidance and policy for potentially years or even decades, a lone IT professional can easily “drift off course” and lose contact and course correction from the larger IT field with only light guidance offered through the filtered world of vendors attempting to sell expensive products and services.

IT professionals suffering from “IT insanity” will often be found implementing bizarre, nonsensical policies that would never be tolerated in a shop with a strong peer-review mechanism, purchasing incredibly overpriced solutions for simple problems and working either completely with or completely without mainstream technologies – mostly dependent upon individual personality.  Partially this is caused by an increasing dependence on a singular, established skill set as the lack of environmental change encourages a process of continuing dependence on existing skills and procedures.

IT insanity will commonly arise in IT shops that have only a single IT professional or in shops where there is a strict hierarchy with no movement at the management ranks so that fresh ideas and experience from younger professionals do not feed up into the managers and instead established practices and “because I said so” policies are forced down the chain to the technologists actually implementing solutions.

This is not to say that all is lost.  There are steps that can be taken to avoid this scenario.  The first is to consider outsourcing IT – any shop so small as to face this dilemma should seriously consider if having full time, dedicated internal staff makes sense in their environment.  Looking for fresh blood is an option – getting IT professionals from other shops and even other industries can work wonders.  Some shops will even trade staff back and forth in extreme cases to keep from losing existing employees but seeking to “mix things up.”

Short of drastic measures such as changing employees entirely, non-IT organizations need to think seriously about the professional health of their staff and look to opportunities for peer interaction.  IT professionals need continuous professional interaction for many reasons and organizations need to actively support and promote this behavior.  Sending staff to training, seminars, peer groups, conventions, shows or even out as volunteers to non-profit and community activities where they can provide IT support in an alternative environment can do wonder for getting them out of the office and face to face with alternative viewpoints and get their hands on different technologies than they see in their day to day lives.

IT managers need opportunities to explore different solution sets and to learn what others are doing in order to best be able to offer objective, broad-based decision making value to their own organizations.

IT Managers and the Value of Decision Making

When I was new to IT I can remember people using the phrase “No one ever got fired for buying IBM.”  At the time I was young and didn’t think too much about what this phrase implies.  Recently, I heard this phrase again – except this time it was “No one ever gets fired for buying Cisco” and soon thereafter I heard it applied to virtualization and VMWare.   This time I stopped to think about what exactly I was being told.

At face value, the statement comes as little more than an observation, but the intent runs much deeper.  The statement is used as a justification for a decision that has been made and implies that the decision was made not because the product or vendor in question was the best choice but because it was the choice that was believed to have the least risk involved for the decision maker.  Not the least risk or most value for the organization – least risk to the decision maker.

This implies one of two possibilities.  The first being that the decision maker in question, presumably an IT manager, feels that due diligence and careful analysis is not recognized or rewarded by the organization. That marketing, by an IT vendor to non-IT management, has convinced management that those products and services are superior without consideration for functionality, cost, reliability or service.

The second possibility is that the IT decision maker believes that they can get away without performing the cost, risk and functionality analysis which would be deemed proper for deciding between competing options and believes that by picking a popular option, well known in the marketplace, that they will be shielded from serious inquiry into their processes and simply deliver what sounds like a plausible solution with minimal effort on their part.

As IT Managers, one of the most crucial job functions that we perform is in identifying, evaluating and recommending products and solutions to our organizations.  The fact that phrases like these are used so commonly suggests that a large percentage of IT managers and advisers are deciding to forgo the difficult and laborious process of researching products and solutions and are banking on making an easy decision that is likely to seem reasonable to management, regardless of whether or not it is a viable solution, let alone the best one for the organization.  The assumption being that a very expensive product will be chosen when potentially a less expensive or less well known option might have worked as well or better and in some extreme cases a product may be recommended using this method that does not even provide for the needs of the organization at all.

IT lives and dies by the decision making value that it brings to the organization.  We hate to admit it, but finding people who can fix desktops is not that hard and the economic value of someone who can fix anything wrong on the desktop versus simply rebuilding one is small.  If we eliminate quality decision analysis from the IT manager’s skill set, what value does he or she bring to the company?