<?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: Rollover and play smart</title>
	<atom:link href="http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/</link>
	<description>The pleasure of recognition and the promise of meaning.</description>
	<pubDate>Tue, 06 Jan 2009 08:23:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrick</title>
		<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/comment-page-1/#comment-159</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Thu, 04 Oct 2007 16:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fluidesign.com/archives/255#comment-159</guid>
		<description>Okay, now it's showing the right image. Was anyone else seeing a feather in a fishbowl before??</description>
		<content:encoded><![CDATA[<p>Okay, now it&#8217;s showing the right image. Was anyone else seeing a feather in a fishbowl before??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hlipner</title>
		<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/comment-page-1/#comment-157</link>
		<dc:creator>hlipner</dc:creator>
		<pubDate>Wed, 03 Oct 2007 20:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fluidesign.com/archives/255#comment-157</guid>
		<description>yeah you are ABSOLUTELY RIGHT brock. we will do that from no on. PHASE 2 it is!</description>
		<content:encoded><![CDATA[<p>yeah you are ABSOLUTELY RIGHT brock. we will do that from no on. PHASE 2 it is!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/comment-page-1/#comment-156</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Wed, 03 Oct 2007 19:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fluidesign.com/archives/255#comment-156</guid>
		<description>That's not the linked-in logo, is it?</description>
		<content:encoded><![CDATA[<p>That&#8217;s not the linked-in logo, is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brocksteady</title>
		<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/comment-page-1/#comment-154</link>
		<dc:creator>brocksteady</dc:creator>
		<pubDate>Wed, 03 Oct 2007 19:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fluidesign.com/archives/255#comment-154</guid>
		<description>Let's be clear about the fact that this functionality didn't happen in LinkedIn Phase 1. LinkedIn (and any other web app) adds features like this due to extensive live user testing. 

We can't think of everything up front when we're designing a site. And more importantly, we need to see how people are using a site before determining what enhanced functionality or help features to add. There are obviously best practices we can preemptively incorporate, but simply adding every trick in the book isn't the best approach. I personally get annoyed when a site or application is overly helpful.

If we want to truely create the best user-experience, then we need to build phase 2 [3,4,5] enhancements into the project budgets. I think almost anyone building a social site like this would understand the importance of rolling out new features as needed.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s be clear about the fact that this functionality didn&#8217;t happen in LinkedIn Phase 1. LinkedIn (and any other web app) adds features like this due to extensive live user testing. </p>
<p>We can&#8217;t think of everything up front when we&#8217;re designing a site. And more importantly, we need to see how people are using a site before determining what enhanced functionality or help features to add. There are obviously best practices we can preemptively incorporate, but simply adding every trick in the book isn&#8217;t the best approach. I personally get annoyed when a site or application is overly helpful.</p>
<p>If we want to truely create the best user-experience, then we need to build phase 2 [3,4,5] enhancements into the project budgets. I think almost anyone building a social site like this would understand the importance of rolling out new features as needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moquito</title>
		<link>http://blog.fluidesign.com/2007/10/03/rollover-and-play-smart/comment-page-1/#comment-153</link>
		<dc:creator>moquito</dc:creator>
		<pubDate>Wed, 03 Oct 2007 18:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fluidesign.com/archives/255#comment-153</guid>
		<description>This is exactly the kind of small usability detail I've been harping on - this is a great example of the kind of "little things" that I want to be built in to our projects...</description>
		<content:encoded><![CDATA[<p>This is exactly the kind of small usability detail I&#8217;ve been harping on - this is a great example of the kind of &#8220;little things&#8221; that I want to be built in to our projects&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
