Skip to main content

Measuring Performance

Measuring Performance (Pocket Mentor)
Why do you measure performance?  Well probably the simplest and most common phrase (that I have mangled, but) that you might have already heard is "you can't fix what you don't know" or "you can't manage what you don't measure" or even "what you measure gets done".  While these are all true in their own way, the real reason that you should be thinking of measuring performance is from a proactive standpoint and not a reactive one which is what these all are.

You want to measure so that you know what is GOING to happen - which is extremely difficult but also extremely necessary.  By ensuring that your resources are in place and trained BEFORE the customer knows that's what they want is only going to make your company shine that much brighter!  Put another way - "you measure to ensure you have enough time to adjust".

Measuring a project (or for that matter your teams individual (see my post on Annual Performance Reviews) performance) at the end, is often too late.  Constant and continuous measurement and feedback is needed throughout the course of the objective to ensure that you are able to appropriately adjust to any deviations and make the appropriate modifications necessary.  By determining that a project has failed to meet the objectives only at the end of the project you are missing a key step.

KPI's (Key Performance Indicators) are a way for you to organize these measurements on a frequent basis and it is key that you share this performance with the staff/teams impacted.  By  only reporting UP in the chain of command with regards to KPIs and performance the people actually impacted are unable to adjust their performance appropriately.

Remember, its a continuous feedback loop just like any other Quality initiave and one of the key pieces of continuous feedback is that failures are fed back into the process as a step in the chain for improvements.

You may find these related posts of interest:
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…