<?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 Study Pitfalls</title>
	<atom:link href="http://www.roninapp.com/blog/2009/01/16/usability-study-pitfalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roninapp.com/blog/2009/01/16/usability-study-pitfalls/</link>
	<description>Tidbits about software development, entrepreneurship, and our product, Ronin</description>
	<pubDate>Sat, 20 Mar 2010 08:29:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Usability feedback loop of web-based software at Design and Development</title>
		<link>http://www.roninapp.com/blog/2009/01/16/usability-study-pitfalls/#comment-98</link>
		<dc:creator>Usability feedback loop of web-based software at Design and Development</dc:creator>
		<pubDate>Mon, 27 Jul 2009 08:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.roninapp.com/?p=97#comment-98</guid>
		<description>[...] run plenty of usability studies here at Ronin. We run them so commonly, that we think of them as taste tests - it&#8217;s only any [...]</description>
		<content:encoded><![CDATA[<p>[...] run plenty of usability studies here at Ronin. We run them so commonly, that we think of them as taste tests - it&#8217;s only any [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recurring Invoices - Back to Basics. at Design and Development</title>
		<link>http://www.roninapp.com/blog/2009/01/16/usability-study-pitfalls/#comment-67</link>
		<dc:creator>Recurring Invoices - Back to Basics. at Design and Development</dc:creator>
		<pubDate>Sat, 28 Mar 2009 07:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.roninapp.com/?p=97#comment-67</guid>
		<description>[...] eventually built the feature, but decided to hold off on releasing it until we did enough user testing before releasing the feature. As it turns out, the first iteration of it, indeed, wasn&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[...] eventually built the feature, but decided to hold off on releasing it until we did enough user testing before releasing the feature. As it turns out, the first iteration of it, indeed, wasn&#8217;t [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
