Skip to main content

KPI's and the Importance of Measurements (part 2)

Continuing from my previous post here, we're going to get more in depth into KPI's and their measurement now.

How do I measure KPI’s?
Get the data (whatever is important to you ... if you use the examples previously mentioned, then track service outages by minutes for example vs. a specified date) into your spreadsheet or other tracking tool, then keep on adding more and more information every time you have another service interruption or outage.  

The key here is consistency and ensuring that you reflect as realistic a picture as possible so the more information you can capture the better.  If you are measuring outages, then make sure you reflect the customers impacted, total amount of time, volume of calls or interactions it created and reason for outage (even a simple 3rd party vs. internal tag is important as it tells you where you need to focus your attention).

Once the data has been captured - make sure you have and are using the right tool for this ... (a spreadsheet as mentioned is great in the early stages but if you can tie this back into a good Incident & Problem Management system and/or a database (I'll get into ITIL and Six Sigma in later posts) you're going to do really well!) - then you need to come up with an appropriate means of analysis.

We are all familiar with the disparaging quotes about statistics (including "There are three kinds of lies: lies, damned lies, and statistics", attributed to either Mark Twain or Disraeli, depending on whom you ask), and it's no secret that many people harbor a vague distrust of statistics as commonly used.

Averages don’t tell you very much. One data point that is extremely far outside the curve will skew everything towards it so care must be taken to ensure that you are measuring information correctly.

Good analysis is an ongoing process, so set targets and assess whether any changes you make are improving your KPI’s or not.
Post a Comment

Popular posts from this blog

The Difference Between Incident Managment and Problem Management

Incident Management and Problem Management are both key components of the ITIL service model and have been defined and created in an effort to provide a better and more streamlined service to consumers.
ITIL itself stands for the - Information Technology Infrastructure Library - and comprises of the following books:
ITIL Service Strategy ITIL Service Design ITIL Service Transition ITIL Service Operation ITIL Continual Service ImprovementIncident Management and Problem Management are both elements of the fourth volume - ITIL Service Operation, which tries to define the best practice for dealing with interruptions to a customers service. What is an Incident? An incident is a single - unique - issue impacting one specific customer and their service. While there can be many similar incidents impacting multiple customers, each of them are in their fashion unique and need to be logged and treated as such.
An example of an incident is you losing your home Internet connection. While the underly…

What is PRINCE2

PRINCE2 stands for PRojects IN Controlled Environments and is a very popular method for effective Project Management.  PROJECT MANAGEMENTWhile PRINCE2 is one way of managing Projects, it is worthwhile defining what exactly a project is and why it needs management in the first place! 

A project is specific task/role that needs to be completed to meet certain objectives. In a managed project, you would have a defined beginning and end and certain "check points" throughout the process itself to ensure that you were on target to meet your overall objectives.

These checkpoints are referred to as "gates" and at each gate, you would have certain deliverable and targets to check your progress against. By managing a project in this fashion, you are able to ensure that you stay on track and that any issues or concerns are identified and dealt with at an early stage of the process versus waiting till the end.

The defined "end" to a project is necessary as it creates …


Competition is extremely fierce in the world of business, only a handful survive, and some can barely keep up with the demands of the times. That's why it is necessary to have an idea of what it takes to be successful and an integrated strategy to help maintain excellent service results.

ITIL discusses at length the four “Ps” of strategy- perspective, position, plan and pattern, each of which represents a different way to approach your service strategy. Brief summaries are provided here: Perspective - This is basically the vision statement of an organization.  Why is it in business, why is it doing what it is doing?  What are the plans and ideas for the future and how does the organization interact with its customers?  A perspective cements a service provider’s distinctiveness in the minds of the employees and customersPositions - What is the competitive landscape and how will the organization compete with other similar providers?  What is the key distinction between them and oth…


In a similar fashion to interviewing and hiring people - the hardest and most expensive exercise is getting the right employee - getting people back into the door is exactly the same.  You want that repeat custom as that is what will save you money in your marketing and advertising.  One of the key components to this in addition to the quality of the product itself is the customer service that you provide to the customer in their purchasing and ordering decisions.  You can offer promotions and slash prices to bring in as many new customers as you want, but unless you can get some of those customers to come back, your business won't be profitable for long. Good customer service is all about bringing customers back. And about sending them away happy - happy enough to pass positive feedback about your business along to others, who may then try the product or service you offer for themselves and in their turn become repeat customers. 
Good customer service should be thought of as re…