<?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: Projects vs. Process Improvement</title>
	<atom:link href="http://www.dailykaizen.org/archives/565/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dailykaizen.org/archives/565</link>
	<description>A blog about improvement in health care</description>
	<pubDate>Wed, 07 Jan 2009 18:41:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: avodartus</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6905</link>
		<dc:creator>avodartus</dc:creator>
		<pubDate>Thu, 25 Dec 2008 18:53:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6905</guid>
		<description>&lt;a href="http://writing.colostate.edu/blogs/view.cfm?blogid=42558" rel="nofollow"&gt;dutasteride baldness&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://writing.colostate.edu/blogs/view.cfm?blogid=42558" rel="nofollow">dutasteride baldness</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #39</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6693</link>
		<dc:creator>Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #39</dc:creator>
		<pubDate>Tue, 15 Jul 2008 17:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6693</guid>
		<description>[...] Projects vs. Process Improvement - &#8220;By taking a project as opposed to process improvement approach it is very hard to make performance visible and understand the effect improvement interventions are having or will have.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Projects vs. Process Improvement - &#8220;By taking a project as opposed to process improvement approach it is very hard to make performance visible and understand the effect improvement interventions are having or will have.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erika Fox</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6688</link>
		<dc:creator>Erika Fox</dc:creator>
		<pubDate>Fri, 11 Jul 2008 23:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6688</guid>
		<description>I think the challenge of project vs process improvement is tricky. I'm living the same challenge as Sean in the Primary Care call management work (i.e. large scope RPIW followed by large-scale implementation = project). Some of it has to do with how we spread an improvement across the delivery system in a standard way. If it is a complex process that touches multiple departments, requires resourcing, capital, technological changes or support, lots of change management etc, it is hard to move away from a project implementation model and have ownership for those details decentralized. All the challenges you described are accurate. 

However, I think the solution might have more to do with how we select improvements in the first place. If we begin with value stream mapping, then will we be less likely to suffer under this project-based approach. 

And I do believe it is a change in thinking as well as a change in the way we do our work. But some days it feels a bit like the chicken and the egg. Which is first? I like the idea that we act our way into a new way of thinking, but that also implies that we are going to take a while to get to the 'thinking differently' part because the 'acting differently' part is going to be fraught with problems and take a while and we're learning as we go. But that's gold, right? 

thanks for this post. thoughtful and insightful as always.</description>
		<content:encoded><![CDATA[<p>I think the challenge of project vs process improvement is tricky. I&#8217;m living the same challenge as Sean in the Primary Care call management work (i.e. large scope RPIW followed by large-scale implementation = project). Some of it has to do with how we spread an improvement across the delivery system in a standard way. If it is a complex process that touches multiple departments, requires resourcing, capital, technological changes or support, lots of change management etc, it is hard to move away from a project implementation model and have ownership for those details decentralized. All the challenges you described are accurate. </p>
<p>However, I think the solution might have more to do with how we select improvements in the first place. If we begin with value stream mapping, then will we be less likely to suffer under this project-based approach. </p>
<p>And I do believe it is a change in thinking as well as a change in the way we do our work. But some days it feels a bit like the chicken and the egg. Which is first? I like the idea that we act our way into a new way of thinking, but that also implies that we are going to take a while to get to the &#8216;thinking differently&#8217; part because the &#8216;acting differently&#8217; part is going to be fraught with problems and take a while and we&#8217;re learning as we go. But that&#8217;s gold, right? </p>
<p>thanks for this post. thoughtful and insightful as always.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Adams</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6686</link>
		<dc:creator>Pete Adams</dc:creator>
		<pubDate>Tue, 08 Jul 2008 19:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6686</guid>
		<description>Wonderful observations, Lee.  Just getting started on our own lean journey, I appreciate your distinctions between a process approach and a project approach.  I will need to remain vigilant to my own schema!</description>
		<content:encoded><![CDATA[<p>Wonderful observations, Lee.  Just getting started on our own lean journey, I appreciate your distinctions between a process approach and a project approach.  I will need to remain vigilant to my own schema!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Sessions</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6684</link>
		<dc:creator>Sean Sessions</dc:creator>
		<pubDate>Tue, 08 Jul 2008 18:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6684</guid>
		<description>I'm seeing this very issue with project-based work following my last RPIW.  We came out with such a large implementation plan that spin-off groups were required to manage work determined necessary during the RPIW.  The good part is that local method owners are responsible for the work, but the work is still being managed using the same historic mental model.  We (facilitators) knew the process going into the RPIW very well, but didn't know that there was a lot of overhead with decisions made up the value stream that impacted resources and timelines and made quick, rapid wins during the RPIW difficult.

Another situation, seperate from my own experience is that of the recent ELT approval of the Medicare PPO expansion.  Knowing that current, daily claims volumes state-wide have exceeded 53,000 in queue, many of which are PPO, I wonder how our resources can continue to improve the claims process given the new contracts being sold up the value stream.  We continue to add contracts to the mix, despite the difficult and often manual claims adjutication processes that our systems don't yet know how to automate.</description>
		<content:encoded><![CDATA[<p>I&#8217;m seeing this very issue with project-based work following my last RPIW.  We came out with such a large implementation plan that spin-off groups were required to manage work determined necessary during the RPIW.  The good part is that local method owners are responsible for the work, but the work is still being managed using the same historic mental model.  We (facilitators) knew the process going into the RPIW very well, but didn&#8217;t know that there was a lot of overhead with decisions made up the value stream that impacted resources and timelines and made quick, rapid wins during the RPIW difficult.</p>
<p>Another situation, seperate from my own experience is that of the recent ELT approval of the Medicare PPO expansion.  Knowing that current, daily claims volumes state-wide have exceeded 53,000 in queue, many of which are PPO, I wonder how our resources can continue to improve the claims process given the new contracts being sold up the value stream.  We continue to add contracts to the mix, despite the difficult and often manual claims adjutication processes that our systems don&#8217;t yet know how to automate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wade</title>
		<link>http://www.dailykaizen.org/archives/565/comment-page-1#comment-6679</link>
		<dc:creator>Eric Wade</dc:creator>
		<pubDate>Mon, 07 Jul 2008 18:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/?p=565#comment-6679</guid>
		<description>Great, thought-provoking post: the process of improvements process itself can be improved.  Mind expanding on a Monday!</description>
		<content:encoded><![CDATA[<p>Great, thought-provoking post: the process of improvements process itself can be improved.  Mind expanding on a Monday!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
