<?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: Rough and Tumble with ROI</title>
	<atom:link href="http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/</link>
	<description>Knowledge is Scrumptious</description>
	<lastBuildDate>Sun, 05 Feb 2012 13:13:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: rajagopal sukumar</title>
		<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/comment-page-1/#comment-10681</link>
		<dc:creator>rajagopal sukumar</dc:creator>
		<pubDate>Tue, 12 May 2009 15:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=1310#comment-10681</guid>
		<description>Interesting perspective. Thanks for sharing Ganesh. Makes sense.</description>
		<content:encoded><![CDATA[<p>Interesting perspective. Thanks for sharing Ganesh. Makes sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ganesh</title>
		<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/comment-page-1/#comment-10677</link>
		<dc:creator>Ganesh</dc:creator>
		<pubDate>Mon, 11 May 2009 20:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=1310#comment-10677</guid>
		<description>Sukumar,

Just happened to read this - http://sethgodin.typepad.com/seths_blog/2009/05/what-to-do-with-people-who-arent-going-to-go-away-quietly.html by Seth Godin. It may not apply that well to what you are asking for, but atleast in some situations, the best way to shut the nay sayers is by not fighting them.</description>
		<content:encoded><![CDATA[<p>Sukumar,</p>
<p>Just happened to read this &#8211; <a href="http://sethgodin.typepad.com/seths_blog/2009/05/what-to-do-with-people-who-arent-going-to-go-away-quietly.html" rel="nofollow">http://sethgodin.typepad.com/seths_blog/2009/05/what-to-do-with-people-who-arent-going-to-go-away-quietly.html</a> by Seth Godin. It may not apply that well to what you are asking for, but atleast in some situations, the best way to shut the nay sayers is by not fighting them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sukumar</title>
		<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/comment-page-1/#comment-10582</link>
		<dc:creator>Sukumar</dc:creator>
		<pubDate>Tue, 28 Apr 2009 12:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=1310#comment-10582</guid>
		<description>Sharmi,
Thanks. Yes, ROI is needed, i am not questioning the need for calculating ROI. 

What i am worried about is, how many ideas are we nipping in the bud because we don&#039;t know the ROI when we start? This is why some of the commenters have suggested rapid prototyping, failing fast etc.  The main reason you consider ROI is when you have a significant investment to make. But if you use rapid prototyping/fail fast pilots etc, your cost of trying ideas may be more. That way you are less likely to kill promising ideas because the originator could not come up with the ROI upfront. 

Does that make sense to you?  Are there other ways?</description>
		<content:encoded><![CDATA[<p>Sharmi,<br />
Thanks. Yes, ROI is needed, i am not questioning the need for calculating ROI. </p>
<p>What i am worried about is, how many ideas are we nipping in the bud because we don&#8217;t know the ROI when we start? This is why some of the commenters have suggested rapid prototyping, failing fast etc.  The main reason you consider ROI is when you have a significant investment to make. But if you use rapid prototyping/fail fast pilots etc, your cost of trying ideas may be more. That way you are less likely to kill promising ideas because the originator could not come up with the ROI upfront. </p>
<p>Does that make sense to you?  Are there other ways?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharmi</title>
		<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/comment-page-1/#comment-10577</link>
		<dc:creator>Sharmi</dc:creator>
		<pubDate>Tue, 28 Apr 2009 10:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=1310#comment-10577</guid>
		<description>Great post Sukumar.

 ROI to me is definitely an essential tool to give focus towards success for any project.I do not see it as an obstruction to innovation. If you focus &quot;what will ROI of this project be &quot;it will lead you to more focused questions towards your success.By preparing for the answers  of these questions you can prepare a more robust plan with a. clear “begin with the end in mind” Somebody doing an ROI should have an open mind. It may be that we do not have the answers to all the questions that is coming up ,but that does not mean that we stop doing that project.We think of multiple channels to address the questions .

I am in training industry for quite some time now, and training is a function which apart from couple of  organizations who focuses on learning  as a key tool for growth ,others treat it as a cost centre. So at every step we have to think of ROI.I personally am challenged by ROI for all programs I plan. Not that my leaders ask for it i.It is something I try to start working on as I plan a program. I have seen that helps me to convince myself, when I take a call before suggesting investment for a program.

The objective of the program becomes much clearer when we focus on the ROI of the program. When we do a training need analysis we try to see if we launch this program how will I show an ROI to the sponsors .Rather we ask the requestor what improvement will you see when we plan this program for you? If it is a new program which we think is needed in the organization –we need to ask what will be the benefit, how can we show the benefit, is it measurable?(normally not ) list down the intangible benefits, how can we capture those? We need to ask what will happen if we don’t do it ?...and we need to go on…

Though in the same breath I would say it is extremely difficult.

So sometimes even when we do not see a clear ROI in the beginning we  start, but we need to keep the ROI in mind.

Maybe if there is a clear guideline that all programs above XXXX amount should have a ROI plan that will help. You see what I mean I am not telling you need to have an ROI , I am telling a ROI plan should be there.</description>
		<content:encoded><![CDATA[<p>Great post Sukumar.</p>
<p> ROI to me is definitely an essential tool to give focus towards success for any project.I do not see it as an obstruction to innovation. If you focus &#8220;what will ROI of this project be &#8220;it will lead you to more focused questions towards your success.By preparing for the answers  of these questions you can prepare a more robust plan with a. clear “begin with the end in mind” Somebody doing an ROI should have an open mind. It may be that we do not have the answers to all the questions that is coming up ,but that does not mean that we stop doing that project.We think of multiple channels to address the questions .</p>
<p>I am in training industry for quite some time now, and training is a function which apart from couple of  organizations who focuses on learning  as a key tool for growth ,others treat it as a cost centre. So at every step we have to think of ROI.I personally am challenged by ROI for all programs I plan. Not that my leaders ask for it i.It is something I try to start working on as I plan a program. I have seen that helps me to convince myself, when I take a call before suggesting investment for a program.</p>
<p>The objective of the program becomes much clearer when we focus on the ROI of the program. When we do a training need analysis we try to see if we launch this program how will I show an ROI to the sponsors .Rather we ask the requestor what improvement will you see when we plan this program for you? If it is a new program which we think is needed in the organization –we need to ask what will be the benefit, how can we show the benefit, is it measurable?(normally not ) list down the intangible benefits, how can we capture those? We need to ask what will happen if we don’t do it ?&#8230;and we need to go on…</p>
<p>Though in the same breath I would say it is extremely difficult.</p>
<p>So sometimes even when we do not see a clear ROI in the beginning we  start, but we need to keep the ROI in mind.</p>
<p>Maybe if there is a clear guideline that all programs above XXXX amount should have a ROI plan that will help. You see what I mean I am not telling you need to have an ROI , I am telling a ROI plan should be there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rajagopal sukumar</title>
		<link>http://www.sastwingees.org/2009/04/23/rough-and-tumble-with-roi/comment-page-1/#comment-10574</link>
		<dc:creator>rajagopal sukumar</dc:creator>
		<pubDate>Tue, 28 Apr 2009 05:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=1310#comment-10574</guid>
		<description>Ganesh,
Thanks. ROI is an essential tool and as Jim pointed out above, only one of the tools in the repertoire. I am not denying that. 

My main grouse has been that ROI gets applied incorrectly even in areas where it is not applicable. It has become a key tool of the devil&#039;s advocate to kill promising ideas. 

Yes, failing fast and cheap and moving on is spot on. We do need to figure out how to do that to test ideas. Learning from failure is also an important thing. 

Thanks for those insights.</description>
		<content:encoded><![CDATA[<p>Ganesh,<br />
Thanks. ROI is an essential tool and as Jim pointed out above, only one of the tools in the repertoire. I am not denying that. </p>
<p>My main grouse has been that ROI gets applied incorrectly even in areas where it is not applicable. It has become a key tool of the devil&#8217;s advocate to kill promising ideas. </p>
<p>Yes, failing fast and cheap and moving on is spot on. We do need to figure out how to do that to test ideas. Learning from failure is also an important thing. </p>
<p>Thanks for those insights.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

