<?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: Is your homepage your homepage?</title>
	<atom:link href="http://blog.usabilityone.com/2010/03/is-your-homepage-your-homepage/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.usabilityone.com/2010/03/is-your-homepage-your-homepage/</link>
	<description>Usability, design and technology</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:26:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Chris Gray</title>
		<link>http://blog.usabilityone.com/2010/03/is-your-homepage-your-homepage/comment-page-1/#comment-75</link>
		<dc:creator>Chris Gray</dc:creator>
		<pubDate>Thu, 04 Mar 2010 23:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=218#comment-75</guid>
		<description>I think this has some interesting implications for the way that we undertake lab based user testing.  In the past we have generally started tasks on the homepage however your project may suggest that we could start tasks from the most common entry pages.  

How do you think this should influence our testing in the fuuture? Should we be starting users on Google with an explicit instruction to use a specific site?</description>
		<content:encoded><![CDATA[<p>I think this has some interesting implications for the way that we undertake lab based user testing.  In the past we have generally started tasks on the homepage however your project may suggest that we could start tasks from the most common entry pages.  </p>
<p>How do you think this should influence our testing in the fuuture? Should we be starting users on Google with an explicit instruction to use a specific site?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

