<?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/"
	>
<channel>
	<title>Comments for ThinkITSM Blog</title>
	<atom:link href="http://www.thinkitsm.com/blog/index.php" rel="self" type="application/rss+xml" />
	<link>http://www.thinkitsm.com/blog</link>
	<description>Define Measure Achieve. Repeat</description>
	<pubDate>Sat, 19 May 2012 07:44:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on ITIL – Not a Cure for the Common Cold! by Morton Byrd</title>
		<link>http://www.thinkitsm.com/blog/?p=119&#038;cpage=1#comment-8016</link>
		<dc:creator>Morton Byrd</dc:creator>
		<pubDate>Tue, 14 Jun 2011 06:06:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=119#comment-8016</guid>
		<description>Cool,
Very interesting site.
That’s the most interesting info I have found about this.
Thank you!</description>
		<content:encoded><![CDATA[<p>Cool,<br />
Very interesting site.<br />
That’s the most interesting info I have found about this.<br />
Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL maturity - where do you want to be and why. by bofa online banking sign in</title>
		<link>http://www.thinkitsm.com/blog/?p=331&#038;cpage=1#comment-6914</link>
		<dc:creator>bofa online banking sign in</dc:creator>
		<pubDate>Tue, 22 Feb 2011 01:56:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=331#comment-6914</guid>
		<description>Many thanks for the article. I will have a link back to this information from our fresh blog. Thanks again.</description>
		<content:encoded><![CDATA[<p>Many thanks for the article. I will have a link back to this information from our fresh blog. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL maturity - where do you want to be and why. by Len Hendershott</title>
		<link>http://www.thinkitsm.com/blog/?p=331&#038;cpage=1#comment-6132</link>
		<dc:creator>Len Hendershott</dc:creator>
		<pubDate>Mon, 17 Jan 2011 17:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=331#comment-6132</guid>
		<description>While ITIL v3 makes some strides in the CSI publication towards acknowledging the imapct of organizational capability, the state of the ITSM/ITIL framework needs still further integration with CMMI maturity modelling concepts. CobIT 5/ValIT are closer to this accommodattion than ITIL V3/v3x. This is not the mamby-pamby recognition of maturity levels in CSI, but detailed mappings of ITIL best practices against organizational process/practice areas. It should lead to greater recognition of a need for introducing ITIL best practices within an organization in conjunction with the capability of that organization to absorb and institutionalize the change.

Not only are many organizations incapable, by virtue of their lack of  maturity (eg. process/performance absenteeism), from implementing many ITIL best practices, but their culture often prevents any progress, whatsoever. Individual and siloed work habits prevent the kinds of cross-organization endevours necessary to achieve CMMI level 3 (ie., process-driven) maturity characteristics. Performance measures may be reported but they reflect internal massaging to bloat results to enhance or maintain staffing and budget levels - there is no independent verification of measures or results. Indeed, best practice initiatives will most often "back-slide" and individuals and silos retrench to reflect protective measures (much as countries retrench during recessions to protect their own workers). Momentuum must be sustained to "institutionalize" results or regression is inevitable.

There is still much conceptual work to be done in ITSM. The concepts in CMMI, MOF, CobIT, SixSigma and ITIL need to be brought together into a complete framework. Unfortuneately, there is less overall money to be made in an integrated framework than in separate, competing methodologies, leaving it to the implementer to take the best of each and produce their own appraoch.</description>
		<content:encoded><![CDATA[<p>While ITIL v3 makes some strides in the CSI publication towards acknowledging the imapct of organizational capability, the state of the ITSM/ITIL framework needs still further integration with CMMI maturity modelling concepts. CobIT 5/ValIT are closer to this accommodattion than ITIL V3/v3x. This is not the mamby-pamby recognition of maturity levels in CSI, but detailed mappings of ITIL best practices against organizational process/practice areas. It should lead to greater recognition of a need for introducing ITIL best practices within an organization in conjunction with the capability of that organization to absorb and institutionalize the change.</p>
<p>Not only are many organizations incapable, by virtue of their lack of  maturity (eg. process/performance absenteeism), from implementing many ITIL best practices, but their culture often prevents any progress, whatsoever. Individual and siloed work habits prevent the kinds of cross-organization endevours necessary to achieve CMMI level 3 (ie., process-driven) maturity characteristics. Performance measures may be reported but they reflect internal massaging to bloat results to enhance or maintain staffing and budget levels - there is no independent verification of measures or results. Indeed, best practice initiatives will most often &#8220;back-slide&#8221; and individuals and silos retrench to reflect protective measures (much as countries retrench during recessions to protect their own workers). Momentuum must be sustained to &#8220;institutionalize&#8221; results or regression is inevitable.</p>
<p>There is still much conceptual work to be done in ITSM. The concepts in CMMI, MOF, CobIT, SixSigma and ITIL need to be brought together into a complete framework. Unfortuneately, there is less overall money to be made in an integrated framework than in separate, competing methodologies, leaving it to the implementer to take the best of each and produce their own appraoch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL maturity - where do you want to be and why. by Mihai Ghimpu</title>
		<link>http://www.thinkitsm.com/blog/?p=331&#038;cpage=1#comment-4682</link>
		<dc:creator>Mihai Ghimpu</dc:creator>
		<pubDate>Fri, 26 Nov 2010 08:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=331#comment-4682</guid>
		<description>Interesting blog</description>
		<content:encoded><![CDATA[<p>Interesting blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Service Desk Measurement - Be careful what you wish for! by Mihai Ghimpu</title>
		<link>http://www.thinkitsm.com/blog/?p=302&#038;cpage=1#comment-4681</link>
		<dc:creator>Mihai Ghimpu</dc:creator>
		<pubDate>Fri, 26 Nov 2010 08:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=302#comment-4681</guid>
		<description>Nice post</description>
		<content:encoded><![CDATA[<p>Nice post</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Evolving Metrics as a Key Component of Your ITSM Evolution&#8230; by Mihai Ghimpu</title>
		<link>http://www.thinkitsm.com/blog/?p=156&#038;cpage=1#comment-4680</link>
		<dc:creator>Mihai Ghimpu</dc:creator>
		<pubDate>Fri, 26 Nov 2010 08:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=156#comment-4680</guid>
		<description>Nice weblog</description>
		<content:encoded><![CDATA[<p>Nice weblog</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Service Desk Measurement - Be careful what you wish for! by Maria Ritchie</title>
		<link>http://www.thinkitsm.com/blog/?p=302&#038;cpage=1#comment-413</link>
		<dc:creator>Maria Ritchie</dc:creator>
		<pubDate>Fri, 09 Oct 2009 19:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=302#comment-413</guid>
		<description>This is actually a more common problem than you may think - sometimes management just doesn't know what's good for them. Truth is they are often bombarded with information (often more like pages of data) that fail to help them make decisions.  Somehow your Help Desk reports need to provide the "At-A-Glance" information that is relevant and actionable.  I have a couple of thoughts for you to consider....

&lt;strong&gt;Ask Them What They Need! &lt;/strong&gt; - If they aren't interested in looking at what you are producing, find out what they would be interesting in looking at.  The service desk is the moment of truth for your IT services and organization.  It provides an important touch point with your users and in return collects very valuable information that, if presented properly, is a gold mine for actionable improvements and early warning to pending issues and customer dissatisfaction.

&lt;strong&gt;Find the Dog to Put the Flea On!&lt;/strong&gt;  If your not ready to approach senior management to draw out their requirements, then seek out that little itch that you can scratch for them.  Use your knowledge of the information available from your service desk and link it to an issue you know is top of mind with your management team. Too often service desk reports speak about incident volumes and FPOC rates, when what management really needs to hear is that there is a spike in outages for a particular application solution that is really impacting the business.  When it comes to reporting 

&lt;strong&gt;Think Big, Start Small, Scale Fast!&lt;/strong&gt; Find the critical few out of the important many reports that you have available.  Before you know it your Service Desk will be recognized as an invaluable source for customer satisfaction and service improvement information.</description>
		<content:encoded><![CDATA[<p>This is actually a more common problem than you may think - sometimes management just doesn&#8217;t know what&#8217;s good for them. Truth is they are often bombarded with information (often more like pages of data) that fail to help them make decisions.  Somehow your Help Desk reports need to provide the &#8220;At-A-Glance&#8221; information that is relevant and actionable.  I have a couple of thoughts for you to consider&#8230;.</p>
<p><strong>Ask Them What They Need! </strong> - If they aren&#8217;t interested in looking at what you are producing, find out what they would be interesting in looking at.  The service desk is the moment of truth for your IT services and organization.  It provides an important touch point with your users and in return collects very valuable information that, if presented properly, is a gold mine for actionable improvements and early warning to pending issues and customer dissatisfaction.</p>
<p><strong>Find the Dog to Put the Flea On!</strong>  If your not ready to approach senior management to draw out their requirements, then seek out that little itch that you can scratch for them.  Use your knowledge of the information available from your service desk and link it to an issue you know is top of mind with your management team. Too often service desk reports speak about incident volumes and FPOC rates, when what management really needs to hear is that there is a spike in outages for a particular application solution that is really impacting the business.  When it comes to reporting </p>
<p><strong>Think Big, Start Small, Scale Fast!</strong> Find the critical few out of the important many reports that you have available.  Before you know it your Service Desk will be recognized as an invaluable source for customer satisfaction and service improvement information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Service Desk Measurement - Be careful what you wish for! by John Nash</title>
		<link>http://www.thinkitsm.com/blog/?p=302&#038;cpage=1#comment-409</link>
		<dc:creator>John Nash</dc:creator>
		<pubDate>Fri, 09 Oct 2009 15:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=302#comment-409</guid>
		<description>My help desk spent time and effort learning about what reports we should be generating, provided them to management and then was told after two months to stop producing them as  no one was interested in looking at them anyway. To say that this was discouraging to the team was an understatement. Do you have any suggestions about how to re-engage senior IT management as to the value proposition of the reports the help desk provides to end this type of cycle?</description>
		<content:encoded><![CDATA[<p>My help desk spent time and effort learning about what reports we should be generating, provided them to management and then was told after two months to stop producing them as  no one was interested in looking at them anyway. To say that this was discouraging to the team was an understatement. Do you have any suggestions about how to re-engage senior IT management as to the value proposition of the reports the help desk provides to end this type of cycle?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL maturity - where do you want to be and why. by mritchie</title>
		<link>http://www.thinkitsm.com/blog/?p=331&#038;cpage=1#comment-399</link>
		<dc:creator>mritchie</dc:creator>
		<pubDate>Thu, 08 Oct 2009 15:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=331#comment-399</guid>
		<description>Amen! Too many ITIL journeys in general lack a focus on outcomes and demonstrable benefits. It is a little scary how many organizations have ITIL improvement projects underway but can't actually define what real benefits they expect to achieve and how they will know they achieved them.  Reaching a maturity level can be a means to an end, but certainly not the end.  Thanks for your insight!</description>
		<content:encoded><![CDATA[<p>Amen! Too many ITIL journeys in general lack a focus on outcomes and demonstrable benefits. It is a little scary how many organizations have ITIL improvement projects underway but can&#8217;t actually define what real benefits they expect to achieve and how they will know they achieved them.  Reaching a maturity level can be a means to an end, but certainly not the end.  Thanks for your insight!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL maturity - where do you want to be and why. by Dave</title>
		<link>http://www.thinkitsm.com/blog/?p=331&#038;cpage=1#comment-389</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 07 Oct 2009 02:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=331#comment-389</guid>
		<description>While I agree with your premise, I see too many organizations pursuing a level of maturity for the sake of the number, with little regard for the business value derived. While reaching a Level 3 or 4 does, in itself, imply some connection with business goals, too many times I see this connection being lost. I've worked with many organizations that have found that the most valuable part of their quest for ITSM maturity is actually the journey, and not the achievement of a particular maturity level.</description>
		<content:encoded><![CDATA[<p>While I agree with your premise, I see too many organizations pursuing a level of maturity for the sake of the number, with little regard for the business value derived. While reaching a Level 3 or 4 does, in itself, imply some connection with business goals, too many times I see this connection being lost. I&#8217;ve worked with many organizations that have found that the most valuable part of their quest for ITSM maturity is actually the journey, and not the achievement of a particular maturity level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

