<?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: Deferring Decisions</title>
	<atom:link href="http://www.productbehavior.com/archive/deferring-decisions/feed" rel="self" type="application/rss+xml" />
	<link>http://www.productbehavior.com/archive/deferring-decisions</link>
	<description>Tell me about it.
</description>
	<pubDate>Fri, 25 Jul 2008 01:41:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Aaron</title>
		<link>http://www.productbehavior.com/archive/deferring-decisions#comment-91</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 02 Apr 2008 13:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbehavior.com/archive/deferring-decisions#comment-91</guid>
		<description>Sure. By "fake" I mean: looks like a convincing product, but with no reality--no engineering behind it, might not be actually manufacturable, looks like it's made out of materials that we don't know will work. But it's important that it look "real" and as integrated as possible; showing material samples separately from unpainted foam models is not as effective as painting the foam model with the right colors. The goal is to get the participants to talk about all of the attributes especially as they relate to each other. Then, very important: throw the examples out. They are for testing communication, not models for the final product. It's easy to fall into the trap of "well, this is close, so let's just use it" but better to start over with the new knowledge from the testing, to avoid the "Mr. Potatohead" approach: glomming a bunch of stuff that worked well in testing together. Design from scratch, but be informed.</description>
		<content:encoded><![CDATA[<p>Sure. By &#8220;fake&#8221; I mean: looks like a convincing product, but with no reality&#8211;no engineering behind it, might not be actually manufacturable, looks like it&#8217;s made out of materials that we don&#8217;t know will work. But it&#8217;s important that it look &#8220;real&#8221; and as integrated as possible; showing material samples separately from unpainted foam models is not as effective as painting the foam model with the right colors. The goal is to get the participants to talk about all of the attributes especially as they relate to each other. Then, very important: throw the examples out. They are for testing communication, not models for the final product. It&#8217;s easy to fall into the trap of &#8220;well, this is close, so let&#8217;s just use it&#8221; but better to start over with the new knowledge from the testing, to avoid the &#8220;Mr. Potatohead&#8221; approach: glomming a bunch of stuff that worked well in testing together. Design from scratch, but be informed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EZ</title>
		<link>http://www.productbehavior.com/archive/deferring-decisions#comment-87</link>
		<dc:creator>EZ</dc:creator>
		<pubDate>Mon, 31 Mar 2008 16:44:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbehavior.com/archive/deferring-decisions#comment-87</guid>
		<description>I'm intrigued- can you talk more about this process when you get a chance? Perhaps give an example of a "fake" design?</description>
		<content:encoded><![CDATA[<p>I&#8217;m intrigued- can you talk more about this process when you get a chance? Perhaps give an example of a &#8220;fake&#8221; design?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
