<?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 on: The Skinny on Lean IT</title>
	<atom:link href="http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/</link>
	<description>IT Strategies for CIOs and IT leaders</description>
	<lastBuildDate>Tue, 31 Jan 2012 14:10:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sudesh Sapra</title>
		<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/comment-page-1/#comment-2835</link>
		<dc:creator>Sudesh Sapra</dc:creator>
		<pubDate>Wed, 02 Sep 2009 00:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=871#comment-2835</guid>
		<description>Thanks Chris. 

I like the comment about the recent diamond project team analyzing service request processes in IT (Transportation industry)where it will take 3 day fulfillment time because a single person has to approve. 

My question is how many processes do we have that require manual interventions that are so inefficient to the business. These are opportunities for the business to redesign and introduce straight through processing. On the other hand, IT can advise on the best tools and technologies out there that will enable this automation more efficient and thus demise the legacy technology that may be carrying excess weight. 

Good article indeed!</description>
		<content:encoded><![CDATA[<p>Thanks Chris. </p>
<p>I like the comment about the recent diamond project team analyzing service request processes in IT (Transportation industry)where it will take 3 day fulfillment time because a single person has to approve. </p>
<p>My question is how many processes do we have that require manual interventions that are so inefficient to the business. These are opportunities for the business to redesign and introduce straight through processing. On the other hand, IT can advise on the best tools and technologies out there that will enable this automation more efficient and thus demise the legacy technology that may be carrying excess weight. </p>
<p>Good article indeed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sudesh Sapra</title>
		<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/comment-page-1/#comment-30591</link>
		<dc:creator>Sudesh Sapra</dc:creator>
		<pubDate>Wed, 02 Sep 2009 00:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=871#comment-30591</guid>
		<description>Thanks Chris. 

I like the comment about the recent diamond project team analyzing service request processes in IT (Transportation industry)where it will take 3 day fulfillment time because a single person has to approve. 

My question is how many processes do we have that require manual interventions that are so inefficient to the business. These are opportunities for the business to redesign and introduce straight through processing. On the other hand, IT can advise on the best tools and technologies out there that will enable this automation more efficient and thus demise the legacy technology that may be carrying excess weight. 

Good article indeed!</description>
		<content:encoded><![CDATA[<p>Thanks Chris. </p>
<p>I like the comment about the recent diamond project team analyzing service request processes in IT (Transportation industry)where it will take 3 day fulfillment time because a single person has to approve. </p>
<p>My question is how many processes do we have that require manual interventions that are so inefficient to the business. These are opportunities for the business to redesign and introduce straight through processing. On the other hand, IT can advise on the best tools and technologies out there that will enable this automation more efficient and thus demise the legacy technology that may be carrying excess weight. </p>
<p>Good article indeed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Lean Equivalent to Optimized? &#124; Tao of IT - Leading and living wisely in the world of Information Technology</title>
		<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/comment-page-1/#comment-2625</link>
		<dc:creator>Is Lean Equivalent to Optimized? &#124; Tao of IT - Leading and living wisely in the world of Information Technology</dc:creator>
		<pubDate>Wed, 26 Aug 2009 20:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=871#comment-2625</guid>
		<description>[...] &amp;&#160;IT&#160;and Chris Curran proposed 2 Lean schemes (Quick Fix and Deep Dive) in The Skinny on Lean IT. On my part, I did mention in a previous post&#160;that &quot;Going Lean&quot; is one aspect of [...]</description>
		<content:encoded><![CDATA[<p>[...] &amp;&nbsp;IT&nbsp;and Chris Curran proposed 2 Lean schemes (Quick Fix and Deep Dive) in The Skinny on Lean IT. On my part, I did mention in a previous post&nbsp;that &quot;Going Lean&quot; is one aspect of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Beech</title>
		<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/comment-page-1/#comment-2102</link>
		<dc:creator>Simon Beech</dc:creator>
		<pubDate>Thu, 13 Aug 2009 07:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=871#comment-2102</guid>
		<description>An excellent article showing how we can use Lean to solve real practical problems in IT.

I like the point about not optimising a process that doesn&#039;t exist - obvious, but often overlooked in the rush.

The distinction between &quot;Quick Hit&quot; and &quot;Deep Dive&quot; is also useful.  This counters a recent Ovum opinion that it&#039;s too late to do Lean IT because it all takes too long.  I use a Lean IT Healthcheck as a diagnostic which can rapidly identify the &quot;Quick Hits&quot; and the &quot;Deep Dives&quot;.  That means CIOs know how to get improvements quickly</description>
		<content:encoded><![CDATA[<p>An excellent article showing how we can use Lean to solve real practical problems in IT.</p>
<p>I like the point about not optimising a process that doesn&#8217;t exist &#8211; obvious, but often overlooked in the rush.</p>
<p>The distinction between &#8220;Quick Hit&#8221; and &#8220;Deep Dive&#8221; is also useful.  This counters a recent Ovum opinion that it&#8217;s too late to do Lean IT because it all takes too long.  I use a Lean IT Healthcheck as a diagnostic which can rapidly identify the &#8220;Quick Hits&#8221; and the &#8220;Deep Dives&#8221;.  That means CIOs know how to get improvements quickly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Beech</title>
		<link>http://www.ciodashboard.com/it-management/the-skinny-on-lean-it/comment-page-1/#comment-30590</link>
		<dc:creator>Simon Beech</dc:creator>
		<pubDate>Thu, 13 Aug 2009 07:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=871#comment-30590</guid>
		<description>An excellent article showing how we can use Lean to solve real practical problems in IT.

I like the point about not optimising a process that doesn&#039;t exist - obvious, but often overlooked in the rush.

The distinction between &quot;Quick Hit&quot; and &quot;Deep Dive&quot; is also useful.  This counters a recent Ovum opinion that it&#039;s too late to do Lean IT because it all takes too long.  I use a Lean IT Healthcheck as a diagnostic which can rapidly identify the &quot;Quick Hits&quot; and the &quot;Deep Dives&quot;.  That means CIOs know how to get improvements quickly</description>
		<content:encoded><![CDATA[<p>An excellent article showing how we can use Lean to solve real practical problems in IT.</p>
<p>I like the point about not optimising a process that doesn&#8217;t exist &#8211; obvious, but often overlooked in the rush.</p>
<p>The distinction between &#8220;Quick Hit&#8221; and &#8220;Deep Dive&#8221; is also useful.  This counters a recent Ovum opinion that it&#8217;s too late to do Lean IT because it all takes too long.  I use a Lean IT Healthcheck as a diagnostic which can rapidly identify the &#8220;Quick Hits&#8221; and the &#8220;Deep Dives&#8221;.  That means CIOs know how to get improvements quickly</p>
]]></content:encoded>
	</item>
</channel>
</rss>

