<?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: A Real-World Example Of Experiential Perspective</title>
	<atom:link href="http://arapehlivanian.com/a-real-world-example-of-experiential-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://arapehlivanian.com/a-real-world-example-of-experiential-perspective/</link>
	<description>Web Standards, Web Culture, Web Everything.™</description>
	<lastBuildDate>Sun, 25 Sep 2011 04:23:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ara Pehlivanian</title>
		<link>http://arapehlivanian.com/a-real-world-example-of-experiential-perspective/comment-page-1/#comment-55685</link>
		<dc:creator>Ara Pehlivanian</dc:creator>
		<pubDate>Tue, 14 Apr 2009 23:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=558#comment-55685</guid>
		<description>Luke: You know it&#039;s like Paul Bennett says in his 2005 GlobalTED talk, &quot;&lt;a href=&#039;http://www.ted.com/index.php/talks/paul_bennett_finds_design_in_the_details.html&#039; rel=&quot;nofollow&quot;&gt;Design is in the Details&lt;/a&gt;.&quot; He says that often the best design solutions are the ones that are right in front of you and you&#039;ve got to try hard just to see them. (He explains it better than I just did.)</description>
		<content:encoded><![CDATA[<p>Luke: You know it&#8217;s like Paul Bennett says in his 2005 GlobalTED talk, &#8220;<a href='http://www.ted.com/index.php/talks/paul_bennett_finds_design_in_the_details.html' rel="nofollow">Design is in the Details</a>.&#8221; He says that often the best design solutions are the ones that are right in front of you and you&#8217;ve got to try hard just to see them. (He explains it better than I just did.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Maciak</title>
		<link>http://arapehlivanian.com/a-real-world-example-of-experiential-perspective/comment-page-1/#comment-55684</link>
		<dc:creator>Luke Maciak</dc:creator>
		<pubDate>Tue, 14 Apr 2009 22:02:48 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=558#comment-55684</guid>
		<description>Amen! You don&#039;t even want to know how many times this has happened to me. I code something up, test it and it seems perfectly intuitive to me. Someone else tests it, and they report it is intuitive and works fine.

So we set up a beta and give it to couple of end users and then watch them be BAFFLED by our &quot;intuitive&quot; interface. 

Or I&#039;m amazed the way some people use the tools we take for granted. For example, whenever I need to make edits to an attachment I save it somewhere on the file system first. Then when I need to send it I go to my email client, create a new email, and attach the file.

I actually observed people to open the email from an attachment, edit it, then go to File-&gt;Send To and email the working copy, without it ever actually being saved on the file system. Of course this failed miserably when we got 3rd party documents which used VB macros that required the files to be saved somewhere on the fie system in a non-temp directory for some reason. Whoever wrote them never assumed people could use office documents this way. And so the app would blow up every time people opened it directly from the email without saving it somewhere first.

Also, I wonder why we ended up with the &quot;Drag and Drop&quot; action rather the more intuitive &quot;Pick up and Drop&quot; action you described above. It seems like it makes more sense. But then again, until I read this post I never even considered it.</description>
		<content:encoded><![CDATA[<p>Amen! You don&#8217;t even want to know how many times this has happened to me. I code something up, test it and it seems perfectly intuitive to me. Someone else tests it, and they report it is intuitive and works fine.</p>
<p>So we set up a beta and give it to couple of end users and then watch them be BAFFLED by our &#8220;intuitive&#8221; interface. </p>
<p>Or I&#8217;m amazed the way some people use the tools we take for granted. For example, whenever I need to make edits to an attachment I save it somewhere on the file system first. Then when I need to send it I go to my email client, create a new email, and attach the file.</p>
<p>I actually observed people to open the email from an attachment, edit it, then go to File-&gt;Send To and email the working copy, without it ever actually being saved on the file system. Of course this failed miserably when we got 3rd party documents which used VB macros that required the files to be saved somewhere on the fie system in a non-temp directory for some reason. Whoever wrote them never assumed people could use office documents this way. And so the app would blow up every time people opened it directly from the email without saving it somewhere first.</p>
<p>Also, I wonder why we ended up with the &#8220;Drag and Drop&#8221; action rather the more intuitive &#8220;Pick up and Drop&#8221; action you described above. It seems like it makes more sense. But then again, until I read this post I never even considered it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

