<?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: Designing for experience vs experience design</title>
	<atom:link href="http://designingforexperience.com/2008/07/17/designing-for-experience-vs-experience-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://designingforexperience.com/2008/07/17/designing-for-experience-vs-experience-design/</link>
	<description>A Holistic Approach to Design for People, Interaction, &#38; Business</description>
	<lastBuildDate>Mon, 07 Nov 2011 13:17:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: aaronh</title>
		<link>http://designingforexperience.com/2008/07/17/designing-for-experience-vs-experience-design/comment-page-1/#comment-171</link>
		<dc:creator>aaronh</dc:creator>
		<pubDate>Tue, 22 Jul 2008 19:17:47 +0000</pubDate>
		<guid isPermaLink="false">http://designingforexperience.com/?p=56#comment-171</guid>
		<description>Matthew-
You are right, it is much more likely that many people will never use what is designed the way it was intended to be used by the designer, more often it is employed in much better ways, or without making any normative claims, they use it in ways which are different, but neither better or worse, simply what is needed or wanted.</description>
		<content:encoded><![CDATA[<p>Matthew-<br />
You are right, it is much more likely that many people will never use what is designed the way it was intended to be used by the designer, more often it is employed in much better ways, or without making any normative claims, they use it in ways which are different, but neither better or worse, simply what is needed or wanted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M.Jenkins</title>
		<link>http://designingforexperience.com/2008/07/17/designing-for-experience-vs-experience-design/comment-page-1/#comment-170</link>
		<dc:creator>M.Jenkins</dc:creator>
		<pubDate>Tue, 22 Jul 2008 17:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://designingforexperience.com/?p=56#comment-170</guid>
		<description>I think it&#039;s OK to design for experience even without any guarantees of achieving that experience. There&#039;s no way 100% of the earth&#039;s population will ever &quot;get&quot; what you&#039;re trying to do - because you&#039;d have to account for cultural history, web literacy, and an impossible number of other unknowns.

Since design is an art, we must do like the artist. The composer makes beautiful music knowing full well the majority of listeners will not feel the experience to the fullest. The poet, doubly so.

Nice blog!</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s OK to design for experience even without any guarantees of achieving that experience. There&#8217;s no way 100% of the earth&#8217;s population will ever &#8220;get&#8221; what you&#8217;re trying to do &#8211; because you&#8217;d have to account for cultural history, web literacy, and an impossible number of other unknowns.</p>
<p>Since design is an art, we must do like the artist. The composer makes beautiful music knowing full well the majority of listeners will not feel the experience to the fullest. The poet, doubly so.</p>
<p>Nice blog!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

