A perfect example

I’ve mentioned before why I think measuring the effectiveness of your help desk folks by looking at the number of tickets they work alone is dumb. This week, I had a perfect example.

We had one of our pool laptops lose a hard drive this week. The replacement drive came in Thursday late in the day, so I set out Friday morning to swap the drive and start the process of installing Windows XP and all the various device drivers, getting all the updates, installing Office and all the other extraneous software (A-V, VPN, Adobe Reader, etc.) that our users might require when traveling with this laptop.

I also answered a few help desk calls/emails while this process was ongoing, but, obviously, not nearly as many as the other people working the help desk that day. If you pulled a report from our help desk software for that day, it’d look like maybe I didn’t do as much work as the other folks, when, in fact, I probably did more. It just so happens that one of my tickets was an all-day project. If we were using number of tickets as an important metric, I wouldn’t have focused on getting this laptop done, and available for our users, I would have focused on closing more tickets, because that’s what I’m being measured by.

On the other hand, I know what was better use of my time in terms of providing support, and that wasn’t worrying about the number of tickets I worked.

Tags: HardDrive, HelpDesk, Metrics

Similar Posts

  • Speaking of big stinks

    Speaking of big stinks, I just had to replace a monitor upstairs. I knew as soon as I hit that hallway that it had shorted, the odor was a definite give away. Luckily we had an extra sitting at an empty cubicle, so I didn’t have to run out and buy one on the spot….

  • | | | |

    Is IT Burnout Limited to IT?

    A post at Lockergnome about IT burnout got me thinking today. The author listed some of the reasons we see a high rate of burnout in IT, and I couldn’t help but think of the seemingly large number of people I know who have left legal IT specifically, in recent months, citing burnout as a…

  • Supporting everything

    Last week I was informed that I’ll be getting a new piece of hardware. Actually, I’ll be getting a second PC, because we’re going to be testing and then partially rolling out a new version of software, and since we will have to support users running both versions for awhile as the roll out moves…

  • Tech chat

    Today was pretty insanely busy at work today, so this post has been “in the works” all day, at least in my head. I took part in the Tech Chat on Kevin’s podcast over the weekend, which was pretty fun. I guess Kevin will have some excerpts during some upcoming podcasts, and I understand there’s…

  • My own thoughts

    Regarding my previous question from the weekend about where you draw the line between keeping up a good relationship with your users and letting them walk all over you with non-work technology issues, I would mostly err on the side of letting them walk over you. There’s definitely a line that needs to be drawn…

  • Documentation

    Kevin stumbled on one of the more frustrating “rookie mistakes” that we all make from time to time. Not documenting stuff! I’ve stumbled on this one myself a few times recently, mistakenly thinking that a problem was a one-time thing and not writing down, and sharing with the other tech support folks, exactly what I…

3 Comments

  1. On the other side of the coin, you can look at number of per user initiated tickets to see who needs training, pc replacement or a “think for yourself – press F1” sticker placed at the top of the monitor 🙂

  2. Andy, I totally agree, there are lots of good reasons to track the number of tickets being handled, you gave one great example and you certainly want to have an understanding of what sort of workflow your people are dealing with too. It’s just not the only way to measure productivity. 🙂

  3. Wow, someone who agrees! I guess the grunts are really the only ones who get this concept, because management sure doesn’t.

    I once deployed 15 computers in six hours (already imaged), and had to clean up after my boss who ‘helped’ by improperly connecting the ethernet, and who later had the nerve to ask me why I was doing fewer tickets than our other tech.

    Our other tech had recently had surgery and as such was handling “easy” calls, like account resets and the like, but somehow, this obvious fact missed him completely. He was gone a month later.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)