<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Measuring Metrics</title>
	<atom:link href="http://effectivecio.com/2010/01/27/measuring-metrics/feed/" rel="self" type="application/rss+xml" />
	<link>http://effectivecio.com/2010/01/27/measuring-metrics/</link>
	<description>...ruminations on many things, all ultimately related to effective IT leadership...</description>
	<lastBuildDate>Wed, 21 Dec 2011 22:44:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Steven M. Smith</title>
		<link>http://effectivecio.com/2010/01/27/measuring-metrics/#comment-1445</link>
		<dc:creator><![CDATA[Steven M. Smith]]></dc:creator>
		<pubDate>Fri, 12 Feb 2010 17:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://effectivecio.com/?p=1676#comment-1445</guid>
		<description><![CDATA[Hi Chuck,

Re: Getting much higher than that (98 or 99 percent on a regular basis), however, involves ferreting out deep issues that may only surface under unusual circumstances. It takes discipline and focus to get there, and metrics can really help.

I agree 100%.

Re: Metrics should never be used as a defense.

I believe it&#039;s important to empathize with the IT client so I agree with your points when talking to clients (terrific analogy BTW). 

I think, however, it&#039;s important to use measurements in discussions with the clients&#039; management to put the availability trade-off into perspective. For instance, for your investment of $X, we can limit unavailability to 1% plus or minus 0.5%, which translates to 2,500 to 7,500 minutes of application unavailability each year. And saying something like, &quot;here is an example (the measurements) on how that looked last year.&quot; If that&#039;s unacceptable, then for an additional investment of $Y we can reduce unavailability by minutes per year.

Availability is truly a trade-off proposition. If the clients&#039; management is absent from deciding what an acceptable return and for the money it&#039;s willing to pay, then IT management is making that choice for the business. And that&#039;s larceny.

Re: metrics should never be used to tell the world what a great job you are doing.

I like this insight. I think, however, the world is used to organizations constantly bragging and the receivers hear the announcements as noise.

I believe strongly that when metrics show the IT organization has met its goals or on its path to meeting its goals, a celebration is warranted. Why? Constantly signals to every member of the organization the importance of availability. 

Celebrate both prevention (efforts that prevent previous outages from reoccurring or mitigate the risks of potential outages) and reaction (efforts the reduced the duration of outages). But don&#039;t over emphasize reaction, which is the typical action. Too often IT organizations only celebrate the reactions, which, in my experience, creates unhealthy internal dynamics.

Wishing you zero outages. Best regards, -Steve]]></description>
		<content:encoded><![CDATA[<p>Hi Chuck,</p>
<p>Re: Getting much higher than that (98 or 99 percent on a regular basis), however, involves ferreting out deep issues that may only surface under unusual circumstances. It takes discipline and focus to get there, and metrics can really help.</p>
<p>I agree 100%.</p>
<p>Re: Metrics should never be used as a defense.</p>
<p>I believe it&#8217;s important to empathize with the IT client so I agree with your points when talking to clients (terrific analogy BTW). </p>
<p>I think, however, it&#8217;s important to use measurements in discussions with the clients&#8217; management to put the availability trade-off into perspective. For instance, for your investment of $X, we can limit unavailability to 1% plus or minus 0.5%, which translates to 2,500 to 7,500 minutes of application unavailability each year. And saying something like, &#8220;here is an example (the measurements) on how that looked last year.&#8221; If that&#8217;s unacceptable, then for an additional investment of $Y we can reduce unavailability by minutes per year.</p>
<p>Availability is truly a trade-off proposition. If the clients&#8217; management is absent from deciding what an acceptable return and for the money it&#8217;s willing to pay, then IT management is making that choice for the business. And that&#8217;s larceny.</p>
<p>Re: metrics should never be used to tell the world what a great job you are doing.</p>
<p>I like this insight. I think, however, the world is used to organizations constantly bragging and the receivers hear the announcements as noise.</p>
<p>I believe strongly that when metrics show the IT organization has met its goals or on its path to meeting its goals, a celebration is warranted. Why? Constantly signals to every member of the organization the importance of availability. </p>
<p>Celebrate both prevention (efforts that prevent previous outages from reoccurring or mitigate the risks of potential outages) and reaction (efforts the reduced the duration of outages). But don&#8217;t over emphasize reaction, which is the typical action. Too often IT organizations only celebrate the reactions, which, in my experience, creates unhealthy internal dynamics.</p>
<p>Wishing you zero outages. Best regards, -Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debbie</title>
		<link>http://effectivecio.com/2010/01/27/measuring-metrics/#comment-1383</link>
		<dc:creator><![CDATA[Debbie]]></dc:creator>
		<pubDate>Sun, 07 Feb 2010 16:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://effectivecio.com/?p=1676#comment-1383</guid>
		<description><![CDATA[Really enjoyed this post!  I see it used every day.  What can I do....to ensure my &#039;control&#039; does not take on this &#039;habit&#039;?

Real improvement involves integration and understanding, but not at the expense of user service.  I never saw the ad Wally Bock spoke of...but it really put the spotlight on IBMs focus on real customer service.  Too many groups serve only the top few percentage to keep them happy and ignore the &#039;workers&#039; of the organization.]]></description>
		<content:encoded><![CDATA[<p>Really enjoyed this post!  I see it used every day.  What can I do&#8230;.to ensure my &#8216;control&#8217; does not take on this &#8216;habit&#8217;?</p>
<p>Real improvement involves integration and understanding, but not at the expense of user service.  I never saw the ad Wally Bock spoke of&#8230;but it really put the spotlight on IBMs focus on real customer service.  Too many groups serve only the top few percentage to keep them happy and ignore the &#8216;workers&#8217; of the organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Martin</title>
		<link>http://effectivecio.com/2010/01/27/measuring-metrics/#comment-1377</link>
		<dc:creator><![CDATA[Robert Martin]]></dc:creator>
		<pubDate>Sat, 30 Jan 2010 22:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://effectivecio.com/?p=1676#comment-1377</guid>
		<description><![CDATA[Really great post! Keep them coming!]]></description>
		<content:encoded><![CDATA[<p>Really great post! Keep them coming!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wally Bock</title>
		<link>http://effectivecio.com/2010/01/27/measuring-metrics/#comment-1373</link>
		<dc:creator><![CDATA[Wally Bock]]></dc:creator>
		<pubDate>Thu, 28 Jan 2010 22:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://effectivecio.com/?p=1676#comment-1373</guid>
		<description><![CDATA[Many years ago IBM (I think) ran a full page add with 100 clouds pictured. All were white but one, which was dark. The headline: 99 % reliability doesn&#039;t matter if you&#039;re the 1]]></description>
		<content:encoded><![CDATA[<p>Many years ago IBM (I think) ran a full page add with 100 clouds pictured. All were white but one, which was dark. The headline: 99 % reliability doesn&#8217;t matter if you&#8217;re the 1</p>
]]></content:encoded>
	</item>
</channel>
</rss>

