5 replies
We use Track-It. Our dept. manager originally generated monthly statistics on the various call types, response times, etc, but we quit tracking that stuff long ago.
Now we use it primarily to track open calls, and secondarily as an in-house knowledge base. We enter problems that may reoccur so we have the solutions, and we enter major projects to record our progress. We've also got a home-grown web interface for the users so they can enter their own problems and track our progress. We enter most details for each call because we often hand calls off between the seven of us (sometimes across state lines; we have lots of laptop users who travel between SC and PA). The closed calls also serve as a source for input into monthly summary reports.
Our rule of thumb: "If it takes longer to enter the call than to fix it, don't bother entering it". This includes things like minor hardware replacements, software tweaks, spot training, or PEBCAK / ID-ten-T issues. Most calls can be recorded in less than five minutes total, if they're updated as they progress.
by jdmercha
I too have tried tracking and reporting. And also have pared it down to only tracking open calls.
In a small organization it is a total waste of time. The reports are relatively usless. What do these reports show anyway?
by cube-dweller
Thanks for your replies. And you've struck upon what I was worried about: that we might be collecting stats that later prove difficult to enter properly or prove to be unneeded.
I think the hope on entries is that there's enough detail to find patterns that can be used to create standard responses, but not so much that we waste time.
As for stats, the idea is to benchmark and improve processes, and also to rebalance the resources. The hope there would be that the information would be collected easily, again not to waste time.
Any further thoughts? Again, thanks for the thoughtful replies, esp your historical perspective, Palmetto. And jdmercha, I was struck by the frustration re stats.
Question for you both: what statistics would you want to have, if time was no object (if each of your techs had a scribe to follow them around)?
I've got a brother-in-law who manages the help desk at a Florida hospital. He tracks the number of calls his technicians handle and how long it takes them to complete each call. He uses this as one factor in each technician's performance reviews. Obviously this type of statistic must be viewed in light of the type and difficulty of problems. Technicians working Level 2 and Level 3 calls can't be expected to close calls as quickly as a Level 1 tech; if they could be closed quickly, they wouldn't have been elevated past Level 1 in the first place :-)
For a while we tracked the volumn of calls by problem category (hardware failure, software configuration, etc.) We stopped that since the tech's can quickly summarize the types of calls they see most often.
by drfez
One thing no one has considered though is the asset management side. If we are to stay competative inhouse we need to be doing root cause analysis and understanding both return on investment and total cost of ownership.
If those items can identify bad performing tools and reduce the number of firefighting trouble tickets the techs can be utilized in more proactive ways. That's not theory, Ive built that type of technical services program myself.
Thinking of trouble management in the terms of just break fix undervalues the technical services side of the IT organization and makes us ripe for outsourcing.
One perfect example, after analysis of the patch management done to my NT servers it was determined my techs spent 1024 hours a year fixing Microsofts problems. That made a great negotiating tool the next time my MS license contracts came up for renewal.
How many applications are there in your environment that have duplication of services? Just from support issues alone analyzing the effectiveness and support costs of those duplication of services products could reduce the number you have and give the company the ability to reduce support agreements and do volume purchasing.
Ya gotta step out of the silo here gang and look at the whole picture when it comes to tracking the trouble management system.
This discussion is closed to new replies.
Trending Software posts
Sort by Trending