<?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: Process Rarely Fixes The Problem</title>
	<atom:link href="http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/</link>
	<description>Where programming, the internet and social media collide.</description>
	<lastBuildDate>Mon, 21 May 2012 05:30:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Fixed bid isn't nirvanna &#124; Lambert on Development</title>
		<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/comment-page-1/#comment-3403</link>
		<dc:creator>Fixed bid isn't nirvanna &#124; Lambert on Development</dc:creator>
		<pubDate>Fri, 01 Jan 2010 01:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=1132#comment-3403</guid>
		<description>[...] Process Rarely Fixes The Problem (regulargeek.com) [...]</description>
		<content:encoded><![CDATA[<p>[...] Process Rarely Fixes The Problem (regulargeek.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Stewart &#124; ChangeForge</title>
		<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/comment-page-1/#comment-3125</link>
		<dc:creator>Ken Stewart &#124; ChangeForge</dc:creator>
		<pubDate>Sun, 01 Nov 2009 01:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=1132#comment-3125</guid>
		<description>Rob, interesting post... This post really catches my interest as I make my living identifying need in business and applying a process to successfully scale that process (given it aligns with and/or supports the offerings of the business).

As with all things, when taken to extremes first create problems and then become the problem themselves; why do you think large corporations are so often held up as examples of soulless and following the letter of the law (instead of spirit). It&#039;s because they have allowed process to overgrow the foundational reason for the process in the first place.

Process is intended to mitigate risk. In this you are certainly correct. It is also to shore up delivery of the product or service to the customer. All of this aside, I have always believed the Agile model to help development teams cope with all of the multiple injection points solicitations will come from in today&#039;s business environment, and the increase the speed to [accurate] delivery - or reduce exposure to a missed feature, which can be built in more quickly.

So I agree that process is not a &quot;fix&quot; for a problem. However, did you realize that the word problem originates from 2 words in Latin which could be translated to mean, &quot;to throw forward&quot;. One interpretation of this might be that we place the &quot;problem&quot; in front of us for all to see and observe; thus if we see the issue we can accurately identify it, or so the hope would go.

Perhaps the problem is not the application of process, or even simplification itself. Perhaps the resolution to our problem might just be perspective. After all, if in your example the company spent the time building relationship with its customers instead of trying to force some video to go viral wouldn&#039;t that build trust for a long term community of clients? The proper perspective applied would certainly show us how our clients respond best.

Of course, as a prospective customer, I might have the perspective this company was simply out for a quick hit - and might not be around tomorrow. That does make my decision much more simple!

Warmest Regards,
Ken Stewart
ChangeForge</description>
		<content:encoded><![CDATA[<p>Rob, interesting post&#8230; This post really catches my interest as I make my living identifying need in business and applying a process to successfully scale that process (given it aligns with and/or supports the offerings of the business).</p>
<p>As with all things, when taken to extremes first create problems and then become the problem themselves; why do you think large corporations are so often held up as examples of soulless and following the letter of the law (instead of spirit). It&#8217;s because they have allowed process to overgrow the foundational reason for the process in the first place.</p>
<p>Process is intended to mitigate risk. In this you are certainly correct. It is also to shore up delivery of the product or service to the customer. All of this aside, I have always believed the Agile model to help development teams cope with all of the multiple injection points solicitations will come from in today&#8217;s business environment, and the increase the speed to [accurate] delivery &#8211; or reduce exposure to a missed feature, which can be built in more quickly.</p>
<p>So I agree that process is not a &#8220;fix&#8221; for a problem. However, did you realize that the word problem originates from 2 words in Latin which could be translated to mean, &#8220;to throw forward&#8221;. One interpretation of this might be that we place the &#8220;problem&#8221; in front of us for all to see and observe; thus if we see the issue we can accurately identify it, or so the hope would go.</p>
<p>Perhaps the problem is not the application of process, or even simplification itself. Perhaps the resolution to our problem might just be perspective. After all, if in your example the company spent the time building relationship with its customers instead of trying to force some video to go viral wouldn&#8217;t that build trust for a long term community of clients? The proper perspective applied would certainly show us how our clients respond best.</p>
<p>Of course, as a prospective customer, I might have the perspective this company was simply out for a quick hit &#8211; and might not be around tomorrow. That does make my decision much more simple!</p>
<p>Warmest Regards,<br />
Ken Stewart<br />
ChangeForge</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Process Rarely Fixes The Problem &#124; Regular Geek -- Topsy.com</title>
		<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/comment-page-1/#comment-3030</link>
		<dc:creator>Tweets that mention Process Rarely Fixes The Problem &#124; Regular Geek -- Topsy.com</dc:creator>
		<pubDate>Sat, 17 Oct 2009 12:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=1132#comment-3030</guid>
		<description>[...] This post was mentioned on Twitter by Rob Diana and LG Shared Items, Phạm Duy Nguyên. Phạm Duy Nguyên said: “Where is this decade’s Access?” From Agile Software Development to Risk Management - an interesting read http://is.gd/4nDri [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Rob Diana and LG Shared Items, Phạm Duy Nguyên. Phạm Duy Nguyên said: “Where is this decade’s Access?” From Agile Software Development to Risk Management &#8211; an interesting read <a href="http://is.gd/4nDri" rel="nofollow">http://is.gd/4nDri</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Diana</title>
		<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/comment-page-1/#comment-3029</link>
		<dc:creator>Rob Diana</dc:creator>
		<pubDate>Sat, 17 Oct 2009 11:22:37 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=1132#comment-3029</guid>
		<description>John

You make some very good points. When I was writing the post I was trying to not focus on software development which was a mistake. 

In your example, you say that using a tool like Blogger makes it easier to get your message out, but competitors also have access to the same tools. Therefore, you still risk not being heard. That is closer to the point I am trying to make. A blog does not get you heard, a blog that is shared bunches of times on Facebook, Twitter and FriendFeed gets you heard. How do you simplify that process?

Coming from the business angle you present, a custom solution to this type of problem does cost money. If the costs associated with the tools is of greater risk, then you have just transferred the risk. I agree with that, and in that case you really have not solved the problem, you just made the problem someone else&#039;s.

I may have to write another post on this that focuses on the tools that need to be created to make things simpler.

Thanks for the excellent comment!</description>
		<content:encoded><![CDATA[<p>John</p>
<p>You make some very good points. When I was writing the post I was trying to not focus on software development which was a mistake. </p>
<p>In your example, you say that using a tool like Blogger makes it easier to get your message out, but competitors also have access to the same tools. Therefore, you still risk not being heard. That is closer to the point I am trying to make. A blog does not get you heard, a blog that is shared bunches of times on Facebook, Twitter and FriendFeed gets you heard. How do you simplify that process?</p>
<p>Coming from the business angle you present, a custom solution to this type of problem does cost money. If the costs associated with the tools is of greater risk, then you have just transferred the risk. I agree with that, and in that case you really have not solved the problem, you just made the problem someone else&#8217;s.</p>
<p>I may have to write another post on this that focuses on the tools that need to be created to make things simpler.</p>
<p>Thanks for the excellent comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John E. Bredehoft</title>
		<link>http://regulargeek.com/2009/10/16/process-rarely-fixes-the-problem/comment-page-1/#comment-3027</link>
		<dc:creator>John E. Bredehoft</dc:creator>
		<pubDate>Sat, 17 Oct 2009 04:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=1132#comment-3027</guid>
		<description>While I heartily agree that a process or a tool (Agile, Twitter, whatever) is not a solution to a problem, I&#039;m not quite convinced that one can sign on to a platform of eliminating risk. Perhaps the word &quot;eliminating&quot; is an exaggeration, but even if one is talking about a massive reduction in risk, that can&#039;t happen either. 

Let me share an example. Let&#039;s say that an organization faces the risk of its message not being heard. Now you can simplify the creation of communications by using ready-made tools such as Blogger or Wordpress. Now you have simplified your tools and provided a way to get your message out...but your competitors have access to that same tool. &lt;a href=&quot;http://blog.louisgray.com/2009/10/blogs-place-in-world-of-microblogging.html&quot; rel=&quot;nofollow&quot;&gt;Louis Gray just noted&lt;/a&gt; that there are ten million content creators on Blogger alone. So risk hasn&#039;t been dramatically reduced by simplification - if anything, the risk that your message won&#039;t be heard has increased.

And even if an organization simplifies via a proprietary technology that is not accessible to its competitors, such simplification comes at a cost. The people or financial resources who simplified the tool are people/resources who couldn&#039;t work on something else, thus increasing other risks of the firm.

Risk can be redistributed, but I&#039;m not certain that it can be dramatically reduced.</description>
		<content:encoded><![CDATA[<p>While I heartily agree that a process or a tool (Agile, Twitter, whatever) is not a solution to a problem, I&#8217;m not quite convinced that one can sign on to a platform of eliminating risk. Perhaps the word &#8220;eliminating&#8221; is an exaggeration, but even if one is talking about a massive reduction in risk, that can&#8217;t happen either. </p>
<p>Let me share an example. Let&#8217;s say that an organization faces the risk of its message not being heard. Now you can simplify the creation of communications by using ready-made tools such as Blogger or WordPress. Now you have simplified your tools and provided a way to get your message out&#8230;but your competitors have access to that same tool. <a href="http://blog.louisgray.com/2009/10/blogs-place-in-world-of-microblogging.html" rel="nofollow">Louis Gray just noted</a> that there are ten million content creators on Blogger alone. So risk hasn&#8217;t been dramatically reduced by simplification &#8211; if anything, the risk that your message won&#8217;t be heard has increased.</p>
<p>And even if an organization simplifies via a proprietary technology that is not accessible to its competitors, such simplification comes at a cost. The people or financial resources who simplified the tool are people/resources who couldn&#8217;t work on something else, thus increasing other risks of the firm.</p>
<p>Risk can be redistributed, but I&#8217;m not certain that it can be dramatically reduced.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.416 seconds -->

