<?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"
	>
<channel>
	<title>Comments on: Usability Test: Want valuable feedback? Recruit real user for testing</title>
	<atom:link href="http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 06:34:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: David Alfaro</title>
		<link>http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-299</link>
		<dc:creator>David Alfaro</dc:creator>
		<pubDate>Fri, 09 May 2008 16:37:20 +0000</pubDate>
		<guid isPermaLink="false">http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-299</guid>
		<description>Yeap Lara, it's a very good point, something is better than nothing. And in those "something" cases I wouldn't proclaim "I am doing serious Usability tests", I would rather say humbly "I did something for guessing what real users would think, if you want a more precise and relevant idea before shipping, we need to invest in doing serious usability testing". I suggest in the cases you mention, (if possible) to tell the client the cost/benefit differences between "real" and "some" usability testing. If the client choose "some", at least everybody took a intentional decision, fully aware of consequences. If you don't push toward quality, nobody will. It's cheaper fixing UX mistakes earlier in a product life-cycle than later once it has shipped and in contact with real users. Just take an intentional decision knowing that.</description>
		<content:encoded><![CDATA[<p>Yeap Lara, it&#8217;s a very good point, something is better than nothing. And in those &#8220;something&#8221; cases I wouldn&#8217;t proclaim &#8220;I am doing serious Usability tests&#8221;, I would rather say humbly &#8220;I did something for guessing what real users would think, if you want a more precise and relevant idea before shipping, we need to invest in doing serious usability testing&#8221;. I suggest in the cases you mention, (if possible) to tell the client the cost/benefit differences between &#8220;real&#8221; and &#8220;some&#8221; usability testing. If the client choose &#8220;some&#8221;, at least everybody took a intentional decision, fully aware of consequences. If you don&#8217;t push toward quality, nobody will. It&#8217;s cheaper fixing UX mistakes earlier in a product life-cycle than later once it has shipped and in contact with real users. Just take an intentional decision knowing that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lara</title>
		<link>http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-289</link>
		<dc:creator>Lara</dc:creator>
		<pubDate>Fri, 09 May 2008 08:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-289</guid>
		<description>I agree that we need to always test with 'real' users but this is very difficult to do in the business environment sometimes, due to time and cost pressures... The quality of the test and results may not be as good but surely some usability testing is better than no usability testing?

=)</description>
		<content:encoded><![CDATA[<p>I agree that we need to always test with &#8216;real&#8217; users but this is very difficult to do in the business environment sometimes, due to time and cost pressures&#8230; The quality of the test and results may not be as good but surely some usability testing is better than no usability testing?</p>
<p>=)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Alfaro</title>
		<link>http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-287</link>
		<dc:creator>David Alfaro</dc:creator>
		<pubDate>Thu, 08 May 2008 15:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-287</guid>
		<description>It's true Peter, but in those rare cases you have to be aware that the feedback you are getting is not good as it can be, and can that it's  biased, asses the risk of doing in that way and remember those caveats when evaluating the results. It's a matter of how realistic a test is, the more realistic the better decisions you can take. Thanks for commenting Peter.</description>
		<content:encoded><![CDATA[<p>It&#8217;s true Peter, but in those rare cases you have to be aware that the feedback you are getting is not good as it can be, and can that it&#8217;s  biased, asses the risk of doing in that way and remember those caveats when evaluating the results. It&#8217;s a matter of how realistic a test is, the more realistic the better decisions you can take. Thanks for commenting Peter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-284</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 08 May 2008 09:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://agilenature.com/2008/05/08/usability-test-want-valuable-feedback-recruit-real-user-for-testing/#comment-284</guid>
		<description>Totally agree although sometimes getting at least someone to test your site with is better than having no-one.</description>
		<content:encoded><![CDATA[<p>Totally agree although sometimes getting at least someone to test your site with is better than having no-one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
