<?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 realities of &#8216;ROI&#8217; for developers</title>
	<atom:link href="http://www.crazymcphee.net/x/2009/05/01/the-realities-of-roi-for-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crazymcphee.net/x/2009/05/01/the-realities-of-roi-for-developers/</link>
	<description>programming idiom and methodology</description>
	<lastBuildDate>Tue, 24 Aug 2010 08:56:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Scot Mcphee</title>
		<link>http://www.crazymcphee.net/x/2009/05/01/the-realities-of-roi-for-developers/comment-page-1/#comment-143</link>
		<dc:creator>Scot Mcphee</dc:creator>
		<pubDate>Sat, 02 May 2009 11:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=347#comment-143</guid>
		<description>Well, maybe it&#039;s that simple, and maybe it isn&#039;t. Because it certainly isn&#039;t as simple as &quot;mentioning&quot; the new system&#039;s payment schedule functionality. Also, perhaps the system is relying on &#039;costly&#039; to be reflected not just in in the internal system, but the way this reflects to teh customer&#039;s experience of the system. We&#039;ve all come across things that are trivially easy to sign up to, but nigh near-on impossible to sign out of. Look at SMS texting services, for example. The crushing bureaucracy is a *feature* from the POV of the CFO.

The point is, you need to be very sure what exactly the &quot;ROI&quot; is in all of these sorts of situations.</description>
		<content:encoded><![CDATA[<p>Well, maybe it&#8217;s that simple, and maybe it isn&#8217;t. Because it certainly isn&#8217;t as simple as &#8220;mentioning&#8221; the new system&#8217;s payment schedule functionality. Also, perhaps the system is relying on &#8216;costly&#8217; to be reflected not just in in the internal system, but the way this reflects to teh customer&#8217;s experience of the system. We&#8217;ve all come across things that are trivially easy to sign up to, but nigh near-on impossible to sign out of. Look at SMS texting services, for example. The crushing bureaucracy is a *feature* from the POV of the CFO.</p>
<p>The point is, you need to be very sure what exactly the &#8220;ROI&#8221; is in all of these sorts of situations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.crazymcphee.net/x/2009/05/01/the-realities-of-roi-for-developers/comment-page-1/#comment-142</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 02 May 2009 02:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=347#comment-142</guid>
		<description>Scot, it&#039;s very simple: propose the solution for eliminating the costly manual process, and mention how the new system would have the ability to just schedule the payment when desired... the business hangs onto the money as long as they want!</description>
		<content:encoded><![CDATA[<p>Scot, it&#8217;s very simple: propose the solution for eliminating the costly manual process, and mention how the new system would have the ability to just schedule the payment when desired&#8230; the business hangs onto the money as long as they want!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
