<?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: Apple Doesn&#8217;t Always Get It</title>
	<atom:link href="http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/</link>
	<description>User Experience Design</description>
	<lastBuildDate>Wed, 01 Feb 2012 13:59:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Russ</title>
		<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/#comment-18001</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Mon, 25 Jan 2010 14:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkbrownstone.com/blog/?p=3#comment-18001</guid>
		<description>Great insight, Neil - thanks for dropping in and bringing this post back to the forefront; we certainly don&#039;t mind that it has a bit of age to it - nice to know it is still striking a chord. Thanks for the comments!</description>
		<content:encoded><![CDATA[<p>Great insight, Neil &#8211; thanks for dropping in and bringing this post back to the forefront; we certainly don&#8217;t mind that it has a bit of age to it &#8211; nice to know it is still striking a chord. Thanks for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil</title>
		<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/#comment-17964</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Mon, 25 Jan 2010 04:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkbrownstone.com/blog/?p=3#comment-17964</guid>
		<description>Interesting post and thought process. And don&#039;t ask my why I&#039;m commenting on a year + old post (I have my reasons, okay?). My two cents:

@ Don’t rely on the notion that your users will figure things out

-I love that idea, and it supports my instinct that there are times when hitting people over the head, though less elegant, is actually showing a certain amount of empathy/respect. Not to mention that customers are not always thinking clearly or paying attention, and it shouldn&#039;t be their job to anyway. 

And if Apple is breaking convention by not having a traditional cash register situation, it&#039;s their responsibility to give major design cues to customers that something new is afoot. Anything else is making Apple too cool for their customers, and nobody should be made to feel like they&#039;re not cool enough to buy an Apple product (even if it&#039;s true in some cases!).

My additional suggestion to Apple, in terms of the 20-minute wait to return a product: always make one employee the &quot;perspective person.&quot; Just like the sound engineer who sits in the back of the theater with their mixing board so that they can hear a live concert like every fan, the store should have an expediter to stand back for a second and notice the inefficiencies as they happen, and help confused customers find the right place. 

Or tell them that they don&#039;t have to go to the &quot;cash register&quot; to buy something.</description>
		<content:encoded><![CDATA[<p>Interesting post and thought process. And don&#8217;t ask my why I&#8217;m commenting on a year + old post (I have my reasons, okay?). My two cents:</p>
<p>@ Don’t rely on the notion that your users will figure things out</p>
<p>-I love that idea, and it supports my instinct that there are times when hitting people over the head, though less elegant, is actually showing a certain amount of empathy/respect. Not to mention that customers are not always thinking clearly or paying attention, and it shouldn&#8217;t be their job to anyway. </p>
<p>And if Apple is breaking convention by not having a traditional cash register situation, it&#8217;s their responsibility to give major design cues to customers that something new is afoot. Anything else is making Apple too cool for their customers, and nobody should be made to feel like they&#8217;re not cool enough to buy an Apple product (even if it&#8217;s true in some cases!).</p>
<p>My additional suggestion to Apple, in terms of the 20-minute wait to return a product: always make one employee the &#8220;perspective person.&#8221; Just like the sound engineer who sits in the back of the theater with their mixing board so that they can hear a live concert like every fan, the store should have an expediter to stand back for a second and notice the inefficiencies as they happen, and help confused customers find the right place. </p>
<p>Or tell them that they don&#8217;t have to go to the &#8220;cash register&#8221; to buy something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: russ</title>
		<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/#comment-29</link>
		<dc:creator>russ</dc:creator>
		<pubDate>Tue, 11 Nov 2008 18:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkbrownstone.com/blog/?p=3#comment-29</guid>
		<description>You hit that nail on the head, Jeff - I had another bad experience there last night trying to explain to the &quot;genius&quot; who was &quot;helping&quot; me that my iPhone clearly has a shielding issue. The other guys I work with have the same exact phone - when they get close to speakers, there is some noise...when I get close to speakers, they go BALLISTIC - and when I get calls upstairs in my house, it sets off the motion detector lights. I kid you not. 

He couldn&#039;t reproduce it in the apple store (gee, I wonder why? because you have all apple compatible, sheilded equipment there, per chance?), and proceded to give me a level 101 speech about how all cell phones make noise. 

I told him that if he wasn&#039;t going to help me, to just say so, and not talk to me like I am an idiot. 

Genius. Pfffft.</description>
		<content:encoded><![CDATA[<p>You hit that nail on the head, Jeff &#8211; I had another bad experience there last night trying to explain to the &#8220;genius&#8221; who was &#8220;helping&#8221; me that my iPhone clearly has a shielding issue. The other guys I work with have the same exact phone &#8211; when they get close to speakers, there is some noise&#8230;when I get close to speakers, they go BALLISTIC &#8211; and when I get calls upstairs in my house, it sets off the motion detector lights. I kid you not. </p>
<p>He couldn&#8217;t reproduce it in the apple store (gee, I wonder why? because you have all apple compatible, sheilded equipment there, per chance?), and proceded to give me a level 101 speech about how all cell phones make noise. </p>
<p>I told him that if he wasn&#8217;t going to help me, to just say so, and not talk to me like I am an idiot. </p>
<p>Genius. Pfffft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brizza</title>
		<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/#comment-4</link>
		<dc:creator>Brizza</dc:creator>
		<pubDate>Thu, 09 Oct 2008 14:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkbrownstone.com/blog/?p=3#comment-4</guid>
		<description>VERY interesting stuff. Clearly Apple is not in danger of destroying the brand equity that they have carefully built up over the years, but small mistakes can gradually be painful. This seems like another great idea from the folks in marketing that was faithfully executed, but without the feedback loop. 

The intention was clearly to make the user experience BETTER, to redesign retail. So whose fault is it - marketing because they didn&#039;t think things through enough? Or retail ops because they didn&#039;t point out the clear stumbling point? 

And how can we avoid the same mistake?</description>
		<content:encoded><![CDATA[<p>VERY interesting stuff. Clearly Apple is not in danger of destroying the brand equity that they have carefully built up over the years, but small mistakes can gradually be painful. This seems like another great idea from the folks in marketing that was faithfully executed, but without the feedback loop. </p>
<p>The intention was clearly to make the user experience BETTER, to redesign retail. So whose fault is it &#8211; marketing because they didn&#8217;t think things through enough? Or retail ops because they didn&#8217;t point out the clear stumbling point? </p>
<p>And how can we avoid the same mistake?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.thinkbrownstone.com/blog/2008/10/07/apple-doesnt-always-get-it/#comment-3</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 09 Oct 2008 14:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkbrownstone.com/blog/?p=3#comment-3</guid>
		<description>Great points Professor, that&#039;s exactly why I do not buy any of my Apple gear at their stores. The minimalistic hipster motif is fine for coffee houses, but not here. I like good signage, employees with assigned tasks in their assigned places and lots of impulse buys at the counter (I always need compressed air), that&#039;s why I go to Microcenter when I want to buy and test drive. Plus, the &quot;Genius&quot; moniker has always turned me off, (PhDs curing cancer might be a bit put off being lumped in the same category).</description>
		<content:encoded><![CDATA[<p>Great points Professor, that&#8217;s exactly why I do not buy any of my Apple gear at their stores. The minimalistic hipster motif is fine for coffee houses, but not here. I like good signage, employees with assigned tasks in their assigned places and lots of impulse buys at the counter (I always need compressed air), that&#8217;s why I go to Microcenter when I want to buy and test drive. Plus, the &#8220;Genius&#8221; moniker has always turned me off, (PhDs curing cancer might be a bit put off being lumped in the same category).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

