
Measurement need not be complicated, although over time you will likely develop increasingly sophisticated ways of keeping a eye on every aspect of your business. Over the coming weeks and months, we will cover some suggestions in more detail through dedicated entries on these topics.
But beyond the what of what you are measuring is the when. Measurement must take place at several frequencies in order to be effective. The best way to illustrate why this is important is through an example: let's use trouble resolution, a central help desk feature.
For this example, we'll assume
Now, back to measurement. Measurement of the trouble resolution performance of your help desk is the goal, but where do you begin? Here are a few important statistics to start with:
- How many tickets are currently open?
- Which tickets have been open too long?
- Who in the team is the most and least effective at dealing with tickets?
- As frequently as possible.
- Daily.
- Weekly.
- Monthly.
While not every permutation of statistic and measurement frequency provides value, many do, making it important to consider all possible combinations when defining your measurement strategy.
Stay up to date about ITIL News, Service Desk Software, and more! Subscribe today!
Related Articles:





» Tech Support to User Ratio: What are your numbers? from HelpDeskNotes
Today some of my colleagues and I had a good laugh, and I need to share it! Some of my colleague's competitors are running an IT business with a staff that is lopsided with technical support. They have 20 tech... [Read More]
Tracked on: December 5, 2007 12:01 AM | Permalink to Trackback