Discussion Locked

IT Departmental Review Criteria

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently our Corporate Management asked us to come up with quantifiable performance criteria for IT.

The number of calls responded to is one indication but are there others which are more meaningful?

11 replies

by jim james

Although number of calls is the first thing that usually comes to mind in this area, we have also struggled to create better criteria of our IT organizations performance. The major problem I see with using number of calls is that if you are doing a great job, ie: solving problems, keeping systems running, training users, you're call numbers should decrease. IF you're counting number of calls, you've shot yourself in the foot!
One of the big ones for us is turn around time, because that is what really matters to the client. How fast can you respond, and equally important, how fast can you provide a usable, long term solution? We use a set of standard guidelines for each "type" of call, and monitor our preformance against those guidelines,ie: 95% within guideline for response, and 94% within guideline for solution time. This is not an end all for your problem, but I hope this helps a bit.

Jim

by calves

We're on the business of non-appreciation. Meaning that if the machines are working, no credit to us. But, won't be long for your name to come up if, God forbides, something goes wrong.
We show quantification by showing enhancements (How much didthe company save in long distance with the implementation of the VPN) or doing the old downtime X salary (
because we're 99% online, the company did not have the loss of the downtime X employee salary).
How much did we save on paper?
How many service calls and what was the response time?

Good luck!

by wayne m.

You need to target your criteria to the business aspects of the company. This probably what will interest corporate managment.

First identify the critical systems for your business. For each one, track uptime, and scheduled and unscheduled downtime on a monthly basis. In your reports, also highlight any changes made to reduce either catagory of downtime.

For user calls, catagorize them on a per system basis, and subcatagorize them on whatever natural break outs appear. Again, be sure to highlight any changes made to address one of the subcatagories.

Finally, provide a list of number of hours spent on out of the ordinary problems. How much time was spent last month on e-mail viruses or a server crash?

They key thing is to map your numbers into business catagories. Show how well you are keeping critical systems operational. Don't be afraid to show problem areas; just be sure you have a proposed solution on hand.

by mark l

I Have your answer.
JJames & CAleves answers point you to specifics that you might be in a position to use, or be in an administrative position, and not know what the heck they are talking about.

wayne.m gives you a variable answer that may or may not apply.

I offer this (from the Process Improvement Guide) PIG for short: FADE cycle:

F = Formulate
A = Advance
D = Define
E = Execute

Straight out of Process improvement guide. You into QA at all? You might want to look into it ...

enjoy :)
MLV//Mark460@trdesk.com 618,539.7439

by wbutler188

all the other responses were right on. heres what i will add. keeping some sort of paper system will be combersome and you will find your IT folks will not like to use it. the thing for you is a help desk tracking system. i have used, done beta testing on a prev version, and now am a reselling partner of a company called blue ocean who makes aproduct called trackit. this software tracks everthing. initailly what u do is scan all your pcs with this prog via the network or disk. this takes a snapshot of harware, software, config info, net settins and hosts of other tings. once this is done you have an inventory listed either by signon name or machine name. it scans w9x nt and i believe 2000.
once this is done when a user calls with aproblem either u or tech opens a help ticket, and assigns them to it. you can track time spent, level of problem either build your own solutin data base or purchase a preloaded one. then you can print daily weekly monthy yearly reports on tons of things.this is a great way

This discussion is closed to new replies.