Comments on: 3 Tenets of Performance Metrics http://ericgoldsmith.com/2009/03/02/3-tenets-of-performance-metrics/ Random thoughts on life and technology Sun, 05 Feb 2012 03:49:21 +0000 http://wordpress.org/?v=2.2.1 By: Mark Morscher http://ericgoldsmith.com/2009/03/02/3-tenets-of-performance-metrics/#comment-649 Mark Morscher Thu, 19 Mar 2009 18:01:07 +0000 http://ericgoldsmith.com/2009/03/02/3-tenets-of-performance-metrics/#comment-649 Good tenets from a performance metric analyzer point-of-view. People used to always sneer at my thirst for all metrics available, or request to generate more, before figuring out which correlate to the problem at hand! I always seemed to have a much heartier appetite than most for the metrics. Another tenet per #3 is is the old adage of turning metrics into information, specifically useful information to those that can make a difference. I've always found two avenues for this: 1. Recognize metrics you observe that important to the business and communicate (per your "so what" example). 2. Recognize "pain" being experienced by the business/executives, and root out the appropriate metric to improve and follow. In the old CompuServe days, the "pain" was the VP of Ops being pinged whenever other executives couldn't load the CompuServe Main Menu! The metric ended up being availability, which led to a whole treasure trove of other metrics (Capacity, publishing, server metrics...) Mark Good tenets from a performance metric analyzer point-of-view. People used to always sneer at my thirst for all metrics available, or request to generate more, before figuring out which correlate to the problem at hand! I always seemed to have a much heartier appetite than most for the metrics.

Another tenet per #3 is is the old adage of turning metrics into information, specifically useful information to those that can make a difference. I’ve always found two avenues for this:

1. Recognize metrics you observe that important to the business and communicate (per your “so what” example).

2. Recognize “pain” being experienced by the business/executives, and root out the appropriate metric to improve and follow. In the old CompuServe days, the “pain” was the VP of Ops being pinged whenever other executives couldn’t load the CompuServe Main Menu! The metric ended up being availability, which led to a whole treasure trove of other metrics (Capacity, publishing, server metrics…)

Mark

]]>