<?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: Musings on UTR 2008</title>
	<atom:link href="http://theappslab.com/2008/03/24/musings-on-utr-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/</link>
	<description>Driving Innovation</description>
	<pubDate>Sun, 05 Jul 2009 03:35:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mathew</title>
		<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/comment-page-1/#comment-3273</link>
		<dc:creator>mathew</dc:creator>
		<pubDate>Wed, 26 Mar 2008 20:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/2008/03/24/musings-on-utr-2008/#comment-3273</guid>
		<description>Thanks for mentioning blist - basically we have a window of opportunity to do much needed rapid feature development before we release a premium version of blist and charge actual, real money for it - at which point, it obviously won't be okay to be 'very beta'.

Mat</description>
		<content:encoded><![CDATA[<p>Thanks for mentioning blist - basically we have a window of opportunity to do much needed rapid feature development before we release a premium version of blist and charge actual, real money for it - at which point, it obviously won&#8217;t be okay to be &#8216;very beta&#8217;.</p>
<p>Mat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Pedrazzi</title>
		<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/comment-page-1/#comment-3259</link>
		<dc:creator>Paul Pedrazzi</dc:creator>
		<pubDate>Tue, 25 Mar 2008 22:59:31 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/2008/03/24/musings-on-utr-2008/#comment-3259</guid>
		<description>Ridgely,  I am sure you have the right priorities.  In fact, I even wonder how slick the UI needs to be for your audience - your bare bones approach may be just fine.  eBay made it with a terrible user experience and I used to think Excite would crush Google, so it's more of a personal preference for me.

That said, more and more UI is a differentiator.  It is the first thing you see after all and a big message of quality (or lack therof) sent to potential users.  I certainly wouldn't buy from a website that looked like a FrontPage template.  I look forward to the refresh!

Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Ridgely,  I am sure you have the right priorities.  In fact, I even wonder how slick the UI needs to be for your audience - your bare bones approach may be just fine.  eBay made it with a terrible user experience and I used to think Excite would crush Google, so it&#8217;s more of a personal preference for me.</p>
<p>That said, more and more UI is a differentiator.  It is the first thing you see after all and a big message of quality (or lack therof) sent to potential users.  I certainly wouldn&#8217;t buy from a website that looked like a FrontPage template.  I look forward to the refresh!</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ridgely Evers</title>
		<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/comment-page-1/#comment-3258</link>
		<dc:creator>Ridgely Evers</dc:creator>
		<pubDate>Tue, 25 Mar 2008 22:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/2008/03/24/musings-on-utr-2008/#comment-3258</guid>
		<description>Thanks for the kind words, Paul.  

Rest assured that we're working on reskinning the UI as we speak.  It'll take a little while longer than we'd like, but we wanted to get the "innards" right first.  Not very Web 2.0, I know, but the right priority given our stewardship of customers' data.

Best,

--Ridge</description>
		<content:encoded><![CDATA[<p>Thanks for the kind words, Paul.  </p>
<p>Rest assured that we&#8217;re working on reskinning the UI as we speak.  It&#8217;ll take a little while longer than we&#8217;d like, but we wanted to get the &#8220;innards&#8221; right first.  Not very Web 2.0, I know, but the right priority given our stewardship of customers&#8217; data.</p>
<p>Best,</p>
<p>&#8211;Ridge</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Pedrazzi</title>
		<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/comment-page-1/#comment-3255</link>
		<dc:creator>Paul Pedrazzi</dc:creator>
		<pubDate>Tue, 25 Mar 2008 16:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/2008/03/24/musings-on-utr-2008/#comment-3255</guid>
		<description>Hi Charles, I am sure your approach yields a much improved  result vis a vis something like MS Project.  I do not doubt that.  To be fair, the problem I am looking to solve is more for the casual projects that mire my existence more than the structured, long term, projects.  The ones where no one wants or needs a full project plan is where I see the most pain.  Obviously you are not tackling that market, but I do see some others taking a stab at it (sadly using the same old models, but now on the web).  

I tend to think that for the ad hoc projects we need something outside the standard task, owner, deliverable mindset.  I even think that a zero UI might be the answer.

Of course I don't have a solution either, but I keep looking...

Thanks for the comment!

Paul</description>
		<content:encoded><![CDATA[<p>Hi Charles, I am sure your approach yields a much improved  result vis a vis something like MS Project.  I do not doubt that.  To be fair, the problem I am looking to solve is more for the casual projects that mire my existence more than the structured, long term, projects.  The ones where no one wants or needs a full project plan is where I see the most pain.  Obviously you are not tackling that market, but I do see some others taking a stab at it (sadly using the same old models, but now on the web).  </p>
<p>I tend to think that for the ad hoc projects we need something outside the standard task, owner, deliverable mindset.  I even think that a zero UI might be the answer.</p>
<p>Of course I don&#8217;t have a solution either, but I keep looking&#8230;</p>
<p>Thanks for the comment!</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Seybold</title>
		<link>http://theappslab.com/2008/03/24/musings-on-utr-2008/comment-page-1/#comment-3252</link>
		<dc:creator>Charles Seybold</dc:creator>
		<pubDate>Tue, 25 Mar 2008 16:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/2008/03/24/musings-on-utr-2008/#comment-3252</guid>
		<description>Hi Paul - Thanks for noting LiquidPlanner. It's tough to describe a concept like revolutionizing the Gantt chart and building a product around it a 6 minute demo. It's not your standard consumer software which is what is mostly seen at UTR. The LiquidPlanner schedule is designed to look familiar, but it functions in a dramatically different way than a typical Gantt. I would be happy to setup a web conference with you if you'd like a briefing.  Key things you'll see include: capturing uncertainty, seeing effects of uncertainty on dependant and independant chains, automatic tracking, and how (by capturing every change) the system builds up a data warehouse of project information that can be leveraged to help organizations learn how to be better estimators.

Best Regards, Charles, CEO &#124; LiquidPlanner.</description>
		<content:encoded><![CDATA[<p>Hi Paul - Thanks for noting LiquidPlanner. It&#8217;s tough to describe a concept like revolutionizing the Gantt chart and building a product around it a 6 minute demo. It&#8217;s not your standard consumer software which is what is mostly seen at UTR. The LiquidPlanner schedule is designed to look familiar, but it functions in a dramatically different way than a typical Gantt. I would be happy to setup a web conference with you if you&#8217;d like a briefing.  Key things you&#8217;ll see include: capturing uncertainty, seeing effects of uncertainty on dependant and independant chains, automatic tracking, and how (by capturing every change) the system builds up a data warehouse of project information that can be leveraged to help organizations learn how to be better estimators.</p>
<p>Best Regards, Charles, CEO | LiquidPlanner.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
