<?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>Fri, 10 Sep 2010 11:46:14 +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 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>
	<item>
		<title>Comment on ITIL – Not a Cure for the Common Cold! by ThinkITSM Blog &#187; ITIL Case Study – If you want to Loose Weight, Get on the Scale</title>
		<link>http://www.thinkitsm.com/blog/?p=119&#038;cpage=1#comment-174</link>
		<dc:creator>ThinkITSM Blog &#187; ITIL Case Study – If you want to Loose Weight, Get on the Scale</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=119#comment-174</guid>
		<description>[...] blog is a follow on to the “ITIL – Not a Cure for the Common Cold!” blog where I provided an overview of a large government’s service management journey and outlined [...]</description>
		<content:encoded><![CDATA[<p>[...] blog is a follow on to the “ITIL – Not a Cure for the Common Cold!” blog where I provided an overview of a large government’s service management journey and outlined [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ITIL – Not a Cure for the Common Cold! by Shelley Woods</title>
		<link>http://www.thinkitsm.com/blog/?p=119&#038;cpage=1#comment-11</link>
		<dc:creator>Shelley Woods</dc:creator>
		<pubDate>Wed, 27 May 2009 18:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkitsm.com/blog/?p=119#comment-11</guid>
		<description>Awesome work....this work was years ahead of its time</description>
		<content:encoded><![CDATA[<p>Awesome work&#8230;.this work was years ahead of its time</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ‘KISSing’ ITIL by Charles Cyna</title>
		<link>http://www.thinkitsm.com/blog/?p=21&#038;cpage=1#comment-9</link>
		<dc:creator>Charles Cyna</dc:creator>
		<pubDate>Tue, 19 May 2009 15:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtest_.thinkitsm.com/blog/?p=21#comment-9</guid>
		<description>BSM has evolved from ITSM as a term to apply many of the practices IT use to manage workflow and process to other areas within the organization. For example, an Incident Management workflow to solve an IT question can be easily applied to an HR department who is answering questions regarding benefits or pay issues.</description>
		<content:encoded><![CDATA[<p>BSM has evolved from ITSM as a term to apply many of the practices IT use to manage workflow and process to other areas within the organization. For example, an Incident Management workflow to solve an IT question can be easily applied to an HR department who is answering questions regarding benefits or pay issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ‘KISSing’ ITIL by David G</title>
		<link>http://www.thinkitsm.com/blog/?p=21&#038;cpage=1#comment-3</link>
		<dc:creator>David G</dc:creator>
		<pubDate>Thu, 30 Apr 2009 19:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtest_.thinkitsm.com/blog/?p=21#comment-3</guid>
		<description>&lt;a href="#comment-1" rel="nofollow"&gt;@Bob Oswald&lt;/a&gt; 
What about BSM (i.e. Business Service Management)? How does that relate to ITSM?</description>
		<content:encoded><![CDATA[<p><a href="#comment-1" rel="nofollow">@Bob Oswald</a><br />
What about BSM (i.e. Business Service Management)? How does that relate to ITSM?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ‘KISSing’ ITIL by David Brighton</title>
		<link>http://www.thinkitsm.com/blog/?p=21&#038;cpage=1#comment-2</link>
		<dc:creator>David Brighton</dc:creator>
		<pubDate>Fri, 24 Apr 2009 15:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtest_.thinkitsm.com/blog/?p=21#comment-2</guid>
		<description>One of the main issues with ITSM gaining popularity is IT Management, who seem to be happy to keep the business in the dark about what it truly takes to keep the IT 'lights on'. This is short sighted in a world where IT departments are in more danger of being outsourced with an abundance of outsourced operations infringing on the IT departments traditional domain.</description>
		<content:encoded><![CDATA[<p>One of the main issues with ITSM gaining popularity is IT Management, who seem to be happy to keep the business in the dark about what it truly takes to keep the IT &#8216;lights on&#8217;. This is short sighted in a world where IT departments are in more danger of being outsourced with an abundance of outsourced operations infringing on the IT departments traditional domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ‘KISSing’ ITIL by Bob Oswald</title>
		<link>http://www.thinkitsm.com/blog/?p=21&#038;cpage=1#comment-1</link>
		<dc:creator>Bob Oswald</dc:creator>
		<pubDate>Fri, 24 Apr 2009 15:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtest_.thinkitsm.com/blog/?p=21#comment-1</guid>
		<description>As a manager of IT, I find that the term ITSM has become confusing as many of the help desk tool makers call their ITIL products ITSM. This is probably a shame because the concept is quite powerful when it is focused on how IT interacts with its customers.</description>
		<content:encoded><![CDATA[<p>As a manager of IT, I find that the term ITSM has become confusing as many of the help desk tool makers call their ITIL products ITSM. This is probably a shame because the concept is quite powerful when it is focused on how IT interacts with its customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
