6 replies
by j.lupo
by espaul
by j.lupo
The problem is that the upper echelons only see IT as a necessary evil (ie. cost center). Which is why it is hard to justify budgets and performance reviews and so on. I was discussing this topic recently with a VP I am working with. He said that when he does the pay for performance review it is a 3rd or 4th generation number because his value is that he did work that allowed another department to increase profits, and so on.
You need to itemize how you add value now to the company. Think of the things you do that help the company to not LOSE money. For example: network security preventing unauthorized access to your systems reduces costs since for example Internet access cost money, phone lines cost money, voice mail systems cost money. Take a look and see how you reduce company costs - THAT IS ADDING VALUE!
There are a lot of things you can do, but you will rarely get anything from the upper echelons because it is something you are suppose to be doing anyway. Now I am not saying it isn't possible, but you need to create a track record of success and market those successes.
If your team were a company providing the services, why should this company continue to retain your services, what do you have to add? This is another way to see how to add value. Treat your group as if you are your own company brought in to add value to this company.
Hope this helps.
by waity85
to add to the previous post. Have a look at what external support companies would charge to manage the resources that you and your team are responsible for. (if its less than the sum of your salaries you may want to keep quiet though)
Also look at the profit/production of other departments that rely on IT resources being available. Calculate what each minute/hour/day of production adds to the company. Then measure your uptime to an industry 'standard'. Providing you uptime is better you can then work out how much value is added to the company by your department being better than industry standard.
You could also look at what downtime would cost the company and highlight the measures and systems that your team have developed to prevent/reduce such downtime.
Unfortunately all this is difficult to explain to the 'suits', especially ones with the technical ability of a cat walking over a keyboard, welcome to the club
by rahammers
A year ago I took a position as the Lead Network Admin at a manufacturing company with ~ 20 World Wide locations. This company had an unusual tollerence for errors. Realizing that that could at any moment turn on me I began to market what we provide the company.
First define a reportable outage. Report every single outage that meets the criteria. This is painful at first but as you implement redundancies and upgrade systems the payoff is reporting to the "suits"...NO Reportable Outages. With due dilligence, this will pay off.
Through "factoids" in my weekly report, I have tried to put the network into terms a non network admin can understand. In one week we move over 20 terabytes of information through reportable links (all uplinks and server ports). I put a graph of the daily traffic in the weekly report and I googled the library of congress...it just happens to = roughly 20 terabytes of information. Put that in the report to. Allow management to understand things in their terms not ours.
In the past, i have reported number of user minutes of up time. Simple enough...user ports X 60*24*7 for the weekly report.
Keep in mind some of these numbers may not be as meaningfull to another network admin but that is not who you are trying to sell to; you are selling to management.
If you can ever show monetary value, all the better but it is not always easy. Sell the up points and be honest about the shortcommings.
Good luck
by espaul
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending