<?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: Using ROI As A Constraint, Not An End In Itself</title>
	<atom:link href="http://lostechies.com/derickbailey/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/derickbailey/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself/</link>
	<description>Better Than Yesterday</description>
	<lastBuildDate>Fri, 24 May 2013 06:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Steve</title>
		<link>http://lostechies.com/derickbailey/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself/#comment-561</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 08 Feb 2010 19:18:33 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself.aspx#comment-561</guid>
		<description>ROI isn&#039;t really the issue here, perceived ROI is.  Also, many IT departments are viewed as nothing but a cost within the executive branch which also cause no ends of trouble.

For example, if a nightly process breaks say once a week, and some IT guy who&#039;s on call gets up at 3am and somehow fixes the problem, that has no cost to the business (at least no perceived cost).  So the next day when the IT guy who fixed the problem asks for some time to fix it he can&#039;t prove ROI since fixing the problem is &quot;free&quot;.  

So when it comes time for the IT Manager/Director/Whatever to go hat-in-hand to the Executives to say &quot;Hey, we&#039;ve been doing nothing but delivering new features for two straight years, I really could use a couple of months to stabalize certain things.&quot; he gets shot down because hey, that IT guy getting up at 3am is free.



</description>
		<content:encoded><![CDATA[<p>ROI isn&#8217;t really the issue here, perceived ROI is.  Also, many IT departments are viewed as nothing but a cost within the executive branch which also cause no ends of trouble.</p>
<p>For example, if a nightly process breaks say once a week, and some IT guy who&#8217;s on call gets up at 3am and somehow fixes the problem, that has no cost to the business (at least no perceived cost).  So the next day when the IT guy who fixed the problem asks for some time to fix it he can&#8217;t prove ROI since fixing the problem is &#8220;free&#8221;.  </p>
<p>So when it comes time for the IT Manager/Director/Whatever to go hat-in-hand to the Executives to say &#8220;Hey, we&#8217;ve been doing nothing but delivering new features for two straight years, I really could use a couple of months to stabalize certain things.&#8221; he gets shot down because hey, that IT guy getting up at 3am is free.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Baley</title>
		<link>http://lostechies.com/derickbailey/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself/#comment-560</link>
		<dc:creator>Kyle Baley</dc:creator>
		<pubDate>Sat, 06 Feb 2010 21:51:01 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2010/02/06/using-roi-as-a-constraint-not-an-end-in-itself.aspx#comment-560</guid>
		<description>I help out on an economics course each year and the instructor likes to drive home a similar point. ROI by itself isn&#039;t a good metric. Take two scenarios: invest $1 today and get $2 next year or invest $1million today and get $1.5million next year. The ROI on the first is much better but few people would take it over the second. You also have to consider the net present value.</description>
		<content:encoded><![CDATA[<p>I help out on an economics course each year and the instructor likes to drive home a similar point. ROI by itself isn&#8217;t a good metric. Take two scenarios: invest $1 today and get $2 next year or invest $1million today and get $1.5million next year. The ROI on the first is much better but few people would take it over the second. You also have to consider the net present value.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
