Skip to main content

Service Desk Metrics

Earlier in my career I had the pleasure of managing a Service Desk. This function is the unsung hero of IT support!

We had a multitude of measurements and metric that were taken every day and then meticulously charted, reported and analyzed. At the time it’s what we did.

I recently had the opportunity to visit my old Service desk and found to my horror, that many of these metrics were no longer being used. I also was informed that customer satisfaction had not dropped significantly and that some of the KPI still being measured were well within an acceptable range. Now that I no longer am in the thick of it, I took some time to really think about what was it we were measuring and what did it really mean. As an organization we did all of the industry best practices measurements.
  • Speed of answer
  • Call duration
  • Number of calls per day/week/month and analyst
  • Abandoned calls
  • Number of tickets opened versus number of tickets closed
  • Percentage 1st call resolved
  • Customer satisfaction survey
 After talking with my former staff, what began to emerge was that with the limited resources that were now available for the management of this process it was decided to limit these KPIs to what really impacted the customer. How was it decided what impacted the customer? They asked and not through a survey sheet but by talking with each and every customer that called or emailed. From the this response, reporting was boiled down to several core KPIs that really mattered to the customers. In this difficult business environment, with seemingly less and less resources we must review what it is we do and ask “Does this provide value? Does this enhance the customer’s experience? Is it important to the delivery of our services? Communication and a willingness to continually ask do I provide value is the key to ongoing success.

Comments

Angel said…
You mentioned that your old service desk had reduced the metrics that they tracked and reported on to those they found really mattered to their customers. Which metrics were they?
The one customer metric that was kept was Service Availability. This measured the availability of the service being delivered to the customer location. It also showed all of the incidents that impacted the delivery of the service. This was still being done on a monthly basis. The desk was still keeping the standard Help desk metrics such as time to answer, average duration and %of 1st call resolve but, these were being utilized by the desk only. IT management was no longer looking at these as valuable tools.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…