Help Desk Perspectives

A recent experience over the use of a help desk caused me to revisit the subject, with a little more insight. It went something like this:

After completing a major upgrade at a small (25-30 users) organization, we were anxious to get feedback about improved performance and user experience. So I instructed the office manager to provide a list of issues which would help us to quickly identify individual PC’s that might be having problems.

And this was not a casual effort without communication infrastructure. The manager had direct access to me via Instant Messaging, with presence, using Lync 2010, email, and my cell phone. We conversed about other matters routinely, in fact on a frequent basis I asked about any upgrade issues specifically and the response was “thumbs up”.

Unaware to both of us was a collection of little slips of paper, post it notes, and torn off pieces of yellow note pad pages accumulating on the bulletin board next to the refrigerator in the break room. Neither I nor the office manager had the slightest idea that a major problem was causing a significant slowdown for a large number of users.

That experience did not end well, but reinforced an important lesson about how not to manage your help desk. For a review about the benefits of a help desk, please see my earlier post here.

How you identify, communicate, prioritize, assign, and account for technical support issues makes all the difference in the world with respect to how well technology works in your school. And there are a large number of help desk systems available for you to choose from. Here are the features that I would look for in a help desk system:

Universal Communication Medium

Help desk issues need an agreed upon standard communication protocol organization wide. The most practical is email, but only if you have a robust email system that provides you synchronized messaging anywhere on any device.

Email is accountable, easily distributed, actionable within automated ticketing systems, and universally used in most schools. Little post it notes (or big ones) probably won’t meet this standard, and have you no (eco-green) shame.

Filtering and Consolidation Mechanism

With the capacity to easily fire off an email to help@yourschool.com, any help desk solution will quickly be overcome with redundant and sometimes ridiculously simple support requests (computer unplugged, network cable disconnected, etc.). So there needs to be a way of collecting daily support requests in some sort of queue, in order to quickly evaluate and act upon requests.

If fifteen teachers report that a crucial website is being blocked by your content filter (for example), then it is entirely counterproductive to think about creating fifteen support requests, or even creating a single trouble ticket for that matter. In the span of time required to create a trouble ticket, you could easily log-in to the firewall and resolve the issue. Then happily delete all fifteen emails reporting the issue!

The most common mistake in designing a help-desk system is the requirement to create a support request (case, incident, ticket, or whatever you choose to call it) for each and every issue. Where a simple notification and action request exists, most ongoing support requests can be resolved as a matter of course.

This is especially true when you are fortunate to have daily onsite technical support resources.

Escalation Process

Any technical problem can be solved with sufficient resources, co-ordination of effort, documentation of actions taken and proposed, and feedback. But, complex or persistent issues may require escalation to a more experienced team member, or an outside vendor. This is not something you can do effectively with a post-it note, or even a three ring binder.

The capacity to resolve complex support requests requires documentation that is available to all parties involved. This includes desktop support technicians, network engineers, software vendors, and most importantly – the end user.

At a minimum, the documentation should include date and time stamps, priority, resolution status, technician assignment, and notes for those involved documenting steps taken and subsequent actions required. An enormously helpful feature would be automation and integration with your internal communication systems, this will facilitate status updates, expected resolution timeframes, and resource requests.

Knowledge Base and Performance Metrics

The accumulation of knowledge about your infrastructure is an important by-product of a well-designed help-desk. Issues that repeat infrequently can be more easily resolved by referring to case notes of a previous support request. Knowledge bases can also be made available to your end users and encourage more self-support in their daily activities.

Performance metrics really speak to the effectiveness of your technical support staff. The most equitable way to measure the effectiveness of your technical support team is through the reporting that comes from the very system they use to resolve your technical support issues. If one of your technicians routinely resolves a significantly larger number of support cases (or queues) in a specified period of time, you might want to consider giving him a promotion!

Summary

Getting frustrated about the difficulty in using a help desk is understandable if it is too cumbersome, complex, and available to only a few individuals. But don’t give up, the benefits of a rational help desk are significant and worth the investment of your time and resources. It can pay big dividends.

Find a simple and reliable communication method (we recommend email) that can be used by anyone having a support request.  Incorporate a practical filtering and issue consolidation process that helps you assess priorities, gauge relative impact (many or few users), and provides a working list for your support staff. Then develop a time or severity based escalation process that formalizes support requests and starts the documentation to resolve and account for more serious issues. And finally, look more long-term at the reports coming from your help desk to assess the effectiveness of your support staff and technical support organization.

And if you really just can’t give up your yellow post it notes, do your support team a favor. Place them in a prominent position and don’t scold them when they miss the support request posted to the bulletin board in the break room next to the refrigerator they never use!

Let us know if you would like to explore ideas about how you can improve your help desk experience.