<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Water here, no water there, and less and less to drink</title>
<link>http://www2.johnson.cornell.edu/alumni/enterprise/fall2012/index.cfm?action=feature&amp;feature_id=2</link>
<description>Comments for &quot;Water here, no water there, and less and less to drink&quot; at http://www2.johnson.cornell.edu/alumni/enterprise/fall2012/index.cfm?action=feature&amp;feature_id=2</description>
<lastBuildDate>Sun, 19 May 2013 03:05:37 GMT</lastBuildDate>
<language>en-us</language><item>
<title>...</title>
<author>Subha Ramiah</author>
<link>http://www2.johnson.cornell.edu/alumni/enterprise/fall2012/index.cfm?action=feature&amp;feature_id=2#item1611</link>
<guid>http://www2.johnson.cornell.edu/alumni/enterprise/fall2012/index.cfm?action=feature&amp;feature_id=2#item1611</guid>
<pubDate>Sun, 27 Jan 2013 19:17:51 GMT</pubDate>
<description><![CDATA[<p>Excellent Article.  To add to Erin Daly's point, getting the innovation out fast to the customer's had is one of the key factors which makes the innovation successful.  Often the users "hack" the product to meet their need which was never the intent of the original design. This makes the product mature from 1.x to x.x in continuous improvement cycle.!</p><p>I am a big believer in 30-60-90! The idea has to hatch out in 30 days with alpha, become beta in 60 and 1.0 in 90 days!<br/>In this information explosive age 1 week could decide the "success" vs "failure!<br/>Subha Ramiah<br/>MBA'07 (E) <br/>Innovator with a technology heart and business brain in Healcthcare</p><p></p>]]></description>
</item>
</channel>
</rss> 