<?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: Encounters And Experiences</title>
	<atom:link href="http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/feed/" rel="self" type="application/rss+xml" />
	<link>http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 18 Feb 2010 22:50:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nate</title>
		<link>http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/comment-page-1/#comment-6881</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Mon, 07 Apr 2008 19:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/#comment-6881</guid>
		<description>In practice, doesn&#039;t a series of encounters create an experience?  After multiple encounters, I tend to start to form opinions about a service.  Those opinions are fortified and validated the more encounters I have.  For this reason, creating a good experience design has to mimic the formation of a good experience.  This is why the service design process is iterative, why a good research methodology is comprised of analyzing encounters and then reflecting on them as a whole, time and time again.  An experience designer will never be out of work: this iterative process means that the job is never done!</description>
		<content:encoded><![CDATA[<p>In practice, doesn&#8217;t a series of encounters create an experience?  After multiple encounters, I tend to start to form opinions about a service.  Those opinions are fortified and validated the more encounters I have.  For this reason, creating a good experience design has to mimic the formation of a good experience.  This is why the service design process is iterative, why a good research methodology is comprised of analyzing encounters and then reflecting on them as a whole, time and time again.  An experience designer will never be out of work: this iterative process means that the job is never done!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/comment-page-1/#comment-6876</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 07 Apr 2008 08:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/2008/04/04/encounters-and-experiences/#comment-6876</guid>
		<description>Hi Steven, I agree that experiences can come from people with many different titles; I was mainly pointing out that most UX designers are falling short of designing experiences, so we should recognize the difference. Transactions, encounters, occasions, occurances. I started this train of thought in &lt;a href=&quot;http://designforservice.wordpress.com/2008/03/07/creating-killer-services/&quot; rel=&quot;nofollow&quot;&gt;Creating Killer Services&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Hi Steven, I agree that experiences can come from people with many different titles; I was mainly pointing out that most UX designers are falling short of designing experiences, so we should recognize the difference. Transactions, encounters, occasions, occurances. I started this train of thought in <a href="http://designforservice.wordpress.com/2008/03/07/creating-killer-services/" rel="nofollow">Creating Killer Services</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
