Some time ago, I wrote a blog about Defining Metrics for the Service Desk. Recently someone asked me what about the help desk? This person works for an organization that doesn’t have an enormous service desk, with hundreds of agents and a complex multi-level service catalogue. Instead, there’s a help desk with just a few technicians who provide support to their users. I’ve worked with IT departments from several small- and medium-sized organizations. In one organization, the help desk consisted of just two technicians whose manager also managed many other people in a variety of different roles. In other organizations, the help desk may have up to 30 or 40 agents, but they don’t operate on the same scale as a large corporate service desk.
Many of the differences between a help desk and a service desk stem from this difference in scale. Typically, a help desk doesn’t have the kind of sophisticated telephone system that routes calls and generates statistics on how long it takes each agent to answer the phone. Instead, staff use a combination of a normal telephone and a web-portal to receive calls from users, and respond to them. The behavior we want to encourage, the metrics needed to encourage that behaviour, and the data available for actually doing the measuring, are all likely to differ significantly from what works best for a service desk.
Some of the advice I offered in my blog about metrics for a service desk does apply just as well to a help desk. This includes:
So now that we’ve spent some time thinking about general advice, let’s focus on some of the practical things you can do. The most important first step to take is to spend some time thinking about the things that your help desk should achieve, and then to write those things down as simply as you can. Remember that these achievements don’t have to be measurable. However, they do have to be the things that you and your customers really care about. Here are some examples of things you might care about:
But please don’t just copy these ideas. Make your own list, one that is relevant to your situation, and then talk to your customers about it. Make sure everyone agrees that these are the most important things for you to achieve.
Once you and your customers have reached agreement about what you should achieve, you have some objectives to work with.
For each of the objectives that you’ve written down you should now think of 2 or 3 KPIs that you can measure to indicate how well the help desk is meeting the objective. It’s important to remember that your KPIs are just indicators; don’t have too many of them, collecting more data than you need is a waste of everyone’s time and effort.
Here are some examples of KPIs a help desk could use to indicate whether they are achieving the objectives in my list of examples:
Objective: Customers find it easy to contact the help desk when they need to.
Objective: The help desk solves customer issues quickly.
Objective: The help desk communicates well with users, keeping them informed and meeting their expectations.
Objective: The help desk collaborates with other parts of the IT organization when needed.
When you look at these KPIs and think about them, these are the important points to notice:
If you decide to follow the advice I’ve been offering, by this point you will have a list of objectives for your help desk, and a list of KPIs for measuring and reporting on how well it is performing. At this stage, it’s all too easy to get so caught up in the KPIs that you lose sight of the original objectives; and it’s vital that you don’t let that happen.
The best way to make sure that you always stay focused on your objectives is to create reports that include them; list the measured metrics and trends under the objective they refer to. This way you will be able to lead conversation about your reporting back to the things that matter.
When you take the report to your customer, the conversation should be about the objectives. Ask about them directly: “Did the help desk solve your issues quickly?” You can provide the metrics to show how quickly you solved issues, and you can use the trends to show that you are improving every week, but don’t present the numbers and tell the customer that this means you did a great job. You must allow your customer to tell you how well you did.
For example, think about a KPI that reads “98% of incidents are resolved within the times defined in the SLA”. Let’s suppose the help desk achieved 99% this month, but one incident that didn’t get resolved within the timeframe specified by the SLA had a huge financial impact. Your customer might well not agree that you did a good job, and your KPI definitely needs some tweaking.
So, use the KPIs for setting thresholds to help you take action when things aren’t going well, and for trend analysis, to see which things are getting better and which might need improvement. But DON’T use them to tell your customers that they are satisfied!
Appropriate KPIs for a help desk are unlikely to be exactly the same as those for a service desk, but the underlying principles don’t change. Identify your objectives, then identify things you can measure and report to indicate how well you’re meeting the objectives. Use what you discover to help you communicate with your customers and to help you identify what you need to improve.
When did you last review your help desk metrics? When did you last talk to your customers about them? Are you measuring and reporting the right things? As always do please let me know if you try the ideas from my blogs.