<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Measuring a Site&#8217;s &#8220;Blink&#8221; Response</title>
	<atom:link href="http://www.uie.com/brainsparks/2005/11/15/measuring-a-sites-blink-response/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2005/11/15/measuring-a-sites-blink-response/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 20 Mar 2010 16:51:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Human Resources Home Page</title>
		<link>http://www.uie.com/brainsparks/2005/11/15/measuring-a-sites-blink-response/comment-page-1/#comment-111033</link>
		<dc:creator>Human Resources Home Page</dc:creator>
		<pubDate>Fri, 07 Mar 2008 20:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=121#comment-111033</guid>
		<description>&lt;strong&gt;The significance of attentive job search in the human resources market...&lt;/strong&gt;

The part of human resources in present society is being &quot;reinvented&quot;, especially as the human resources market already is packed with potential recruits. It is not simple to find the high-paid place to work, with all some other benefits. Moreover, th...</description>
		<content:encoded><![CDATA[<p><strong>The significance of attentive job search in the human resources market&#8230;</strong></p>
<p>The part of human resources in present society is being &#8220;reinvented&#8221;, especially as the human resources market already is packed with potential recruits. It is not simple to find the high-paid place to work, with all some other benefits. Moreover, th&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enric Naval</title>
		<link>http://www.uie.com/brainsparks/2005/11/15/measuring-a-sites-blink-response/comment-page-1/#comment-290</link>
		<dc:creator>Enric Naval</dc:creator>
		<pubDate>Wed, 16 Nov 2005 20:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=121#comment-290</guid>
		<description>In our cases, we hadn&#039;t what we could call a &quot;technique&quot;. Basically, showing the page to the user and asking them what they thought worked quite well. 

We just ask the user for their first impression after opening the page and before they start the actual usability test. We can ask them for a on-the-fly critic of the general design before telling them about the tasks they have to do. 

Of course, users may accept temporaly an ugly design and a bad first impression, as long as they know that they can achieve their most important goals on your page, or they can achieve them better than in other pages.

It helps if you asure them that you will pay a designer to make it better :)  

The first impression is very important, but once we are past the first impression, the funcionality, including whether they can do their tasks fastly, weigths so much so the first impression pales in comparison.  Of course, this must mean that your page actually offers something worthy to the user or the first impression will just wear out after a while and they will leave :( 

That&#039;s why we didn&#039;t make separate test for first impressions. We had scarce resources and it was &quot;cheaper&quot; to make a first impression test before each usability test, even if this meant that our design sucked for a while because we hadn&#039;t enough input from users because we only did usability tests once in a while.</description>
		<content:encoded><![CDATA[<p>In our cases, we hadn&#8217;t what we could call a &#8220;technique&#8221;. Basically, showing the page to the user and asking them what they thought worked quite well. </p>
<p>We just ask the user for their first impression after opening the page and before they start the actual usability test. We can ask them for a on-the-fly critic of the general design before telling them about the tasks they have to do. </p>
<p>Of course, users may accept temporaly an ugly design and a bad first impression, as long as they know that they can achieve their most important goals on your page, or they can achieve them better than in other pages.</p>
<p>It helps if you asure them that you will pay a designer to make it better <img src='http://www.uie.com/brainsparks/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   </p>
<p>The first impression is very important, but once we are past the first impression, the funcionality, including whether they can do their tasks fastly, weigths so much so the first impression pales in comparison.  Of course, this must mean that your page actually offers something worthy to the user or the first impression will just wear out after a while and they will leave <img src='http://www.uie.com/brainsparks/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  </p>
<p>That&#8217;s why we didn&#8217;t make separate test for first impressions. We had scarce resources and it was &#8220;cheaper&#8221; to make a first impression test before each usability test, even if this meant that our design sucked for a while because we hadn&#8217;t enough input from users because we only did usability tests once in a while.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
