<?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: Why I&#8217;m Not Doing a Paper Prototype</title>
	<atom:link href="http://dubroy.com/blog/why-im-not-doing-a-paper-prototype/feed/" rel="self" type="application/rss+xml" />
	<link>http://dubroy.com/blog/why-im-not-doing-a-paper-prototype/</link>
	<description>programming, usability, and interaction design</description>
	<lastBuildDate>Wed, 11 Aug 2010 20:40:29 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrick</title>
		<link>http://dubroy.com/blog/why-im-not-doing-a-paper-prototype/comment-page-1/#comment-966</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Wed, 06 Jun 2007 15:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://dubroy.com/blog/2007/06/05/why-im-not-doing-a-paper-prototype/#comment-966</guid>
		<description>&lt;p&gt;Well, yes and no. For an email client for example, the test subject would need to allow me to read their email, and use it in the paper prototype. That makes it difficult. And then I would need to simulate the kinds of email they would typically be receiving (or actually monitor their inbox). For something like a search tool, because the use is so open ended, there is almost no way that you could prepare a paper prototype for a realistic use case.&lt;/p&gt;

&lt;p&gt;And as I mentioned, when you are looking at interaction techniques, instead of specific applications, the most important part is often the exact thing that paper prototyping leaves out -- the really subtle &quot;this feels right&quot;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well, yes and no. For an email client for example, the test subject would need to allow me to read their email, and use it in the paper prototype. That makes it difficult. And then I would need to simulate the kinds of email they would typically be receiving (or actually monitor their inbox). For something like a search tool, because the use is so open ended, there is almost no way that you could prepare a paper prototype for a realistic use case.</p>

<p>And as I mentioned, when you are looking at interaction techniques, instead of specific applications, the most important part is often the exact thing that paper prototyping leaves out &#8212; the really subtle &#8220;this feels right&#8221;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: e</title>
		<link>http://dubroy.com/blog/why-im-not-doing-a-paper-prototype/comment-page-1/#comment-965</link>
		<dc:creator>e</dc:creator>
		<pubDate>Wed, 06 Jun 2007 15:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://dubroy.com/blog/2007/06/05/why-im-not-doing-a-paper-prototype/#comment-965</guid>
		<description>&lt;p&gt;Can&#039;t you do a lo-fi prototype with real data culled from a real data source?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Can&#8217;t you do a lo-fi prototype with real data culled from a real data source?</p>]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->