<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Commonsense Design &#187; User Experience</title>
	<atom:link href="http://designblog.nzeldes.com/tag/user-experience/feed/" rel="self" type="application/rss+xml" />
	<link>http://designblog.nzeldes.com</link>
	<description>Nathan Zeldes blogs on everyday product design</description>
	<lastBuildDate>Sat, 21 Jan 2012 22:01:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Only a smile</title>
		<link>http://designblog.nzeldes.com/2011/01/only-a-smile/</link>
		<comments>http://designblog.nzeldes.com/2011/01/only-a-smile/#comments</comments>
		<pubDate>Thu, 06 Jan 2011 07:38:41 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Odds and Ends]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/?p=1069</guid>
		<description><![CDATA[I wrote before about the impact of a cheerful nature on the customer service experience. Well &#8211; here is another example. We were visiting the Museum für Naturkunde in Berlin (recommended! A 200 year old Natural History museum, like the one at Dublin I wrote about once, but artfully modernized and with some really big [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2011%2F01%2Fonly-a-smile%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2011%2F01%2Fonly-a-smile%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I <a href="http://designblog.nzeldes.com/2010/09/one-key-to-great-customer-support/">wrote before</a> about the impact of a cheerful nature on the customer service experience. Well &#8211; here is another example.</p>
<p>We were visiting the <a href="http://www.naturkundemuseum-berlin.de/index_english.html">Museum für Naturkunde</a> in Berlin (recommended! A 200 year old Natural History museum, like the one at Dublin I <a href="http://www.nzeldes.com/Miscellany/RealThing.htm">wrote about</a> once, but artfully modernized and with some really big dinosaurs thrown in!)  It being in winter, we obviously headed first for the cloakroom where we dumped a few kilograms of insulation; and we started on the task of deciphering a sign on the wall  to figure the fee we&#8217;d have to pay.</p>
<p>At which point the young lady at the counter, perceiving our linguistic struggle, said to us in English: &#8220;It costs only a smile!&#8221; &#8230;  and she proceeded to illustrate with a charming one of her own, invoking a return in kind.</p>
<p>What a lovely welcome!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2011/01/only-a-smile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One key to great customer support</title>
		<link>http://designblog.nzeldes.com/2010/09/one-key-to-great-customer-support/</link>
		<comments>http://designblog.nzeldes.com/2010/09/one-key-to-great-customer-support/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 19:58:50 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Odds and Ends]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/?p=953</guid>
		<description><![CDATA[This morning my notebook&#8217;s battery died an ignominious death, and I had to hurriedly procure a new one. Not a good start for the day. I called the vendor&#8217;s customer support center, and plodded through the Interactive Voice Response (IVR) menu, fully expecting a harrowing experience. Instead, I was routed to a service rep who [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2010%2F09%2Fone-key-to-great-customer-support%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2010%2F09%2Fone-key-to-great-customer-support%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>This morning my notebook&#8217;s battery died an ignominious death, and I had to hurriedly procure a new one. Not a good start for the day.</p>
<p>I called the vendor&#8217;s customer support center, and plodded through the Interactive Voice Response (IVR) menu, fully expecting a harrowing experience. Instead, I was routed to a service rep who gave me the information I needed (well, it was not rocket science after all) but did it in a manner that completely undid the bad mood I was in. It&#8217;s hard to put a finger on it, but she was cheerful, confident, friendly, and really conveyed the feeling that she was proud to be able to solve my problem, and solve it fast. Basically this woman was transmitting good service vibes, and the positive mood was contagious.</p>
<p>I suppose it goes to this particular rep&#8217;s character and style, but the difference from service reps I usually talk to anywhere was impressive. The others were polite (or not) and doing a job; this one was enjoying it. What a difference this can make in the user experience!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2010/09/one-key-to-great-customer-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Let&#8217;s add Interrupt capability to customer support systems</title>
		<link>http://designblog.nzeldes.com/2009/08/lets-add-interrupt-capability-to-customer-support-systems/</link>
		<comments>http://designblog.nzeldes.com/2009/08/lets-add-interrupt-capability-to-customer-support-systems/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 08:54:00 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Improvement]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/?p=595</guid>
		<description><![CDATA[I&#8217;m sure this happened to you: you call the support number of your bank/phone company/whatever, go patiently through all the Interactive Voice Response (IVR) menus, get shunted to an &#8220;all agents are currently busy&#8221; music, waste long minutes listening, and finally get a human to talk to. You explain your request, and the agent politely [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F08%2Flets-add-interrupt-capability-to-customer-support-systems%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F08%2Flets-add-interrupt-capability-to-customer-support-systems%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I&#8217;m sure this happened to you: you call the support number of your bank/phone company/whatever, go patiently through all the Interactive Voice Response (IVR) menus, get shunted to an &#8220;all agents are currently busy&#8221; music, waste long minutes listening, and finally get a human to talk to. You explain your request, and the agent politely says  &#8220;Let me put you on hold while I find out the information&#8221;.  Before you can protest, you&#8217;re back on the music!</p>
<p>Which goes on and on, and you have no idea whether the agent is really digging up the information, or he had a heart attack, or he simply forgot about you&#8230; the music just drones on. Doubt starts gnawing: should you hang up and start over? Maybe he&#8217;s just seconds from picking the line again? Anguish, anger, and unhappiness fill you. And if you&#8217;re in the middle of some bank transaction you don&#8217;t want to abort, and you have a meeting starting in 3 minutes, you really need to ask the agent what&#8217;s going on &#8211; but he&#8217;s just out of your reach. This is definitely <strong>not</strong> a good customer experience.</p>
<p><strong>So, what can we do about this?</strong> What is needed is a protocol we used to have when I was an amateur radio operator. Back then, people would speak in turn on the radio waves: &#8230;<em>AB1CC, this is XY7ZZ, over!</em> <em>Roger XY7ZZ, this is AB1CC&#8230;</em> But we had a mechanism for getting a word in sideways if something urgent came up, say another ham with an emergency communication: you could wait for a pause between words and say &#8220;Break-break!&#8221; and the talking party would shut up and listen. We had an Interrupt capability.</p>
<p>This capability is what we need in those service desks: a mechanism &#8211; say, some key sequence on the phone &#8211; that would cause the line to go back from hold to the agent that parked it there. Even the knowledge that you could, if you wanted to, get the agent back and ask how much longer is he going to take &#8211; would make you feel a lot better, much less helpless and frustrated.</p>
<p><strong>Take note</strong>, my dear bank &#8211; give us back some control!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2009/08/lets-add-interrupt-capability-to-customer-support-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IVR woes: good idea &#8211; poor execution</title>
		<link>http://designblog.nzeldes.com/2009/03/ivr-woes-good-idea-poor-execution/</link>
		<comments>http://designblog.nzeldes.com/2009/03/ivr-woes-good-idea-poor-execution/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 07:45:55 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Bad design]]></category>
		<category><![CDATA[Good design]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2009/03/ivr-woes-good-idea-poor-execution/</guid>
		<description><![CDATA[I was trying to reach the customer service of a company just now. There I was, listening to the endless music of an IVR system, punctuated by the usual happy reminders that I am oh-so-appreciated by them and they&#8217;ll get to me real soon (liars!), when something happened. The recording declared that they were very [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F03%2Fivr-woes-good-idea-poor-execution%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F03%2Fivr-woes-good-idea-poor-execution%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I was trying to reach the customer service of a company just now. There I was, listening to the endless music of an IVR system, punctuated by the usual happy reminders that I am oh-so-appreciated by them and they&#8217;ll get to me real soon (liars!), when something happened. The recording declared that they were very busy so if I could leave my name and number they&#8217;ll get back to me. No option to keep waiting.</p>
<p>To their credit, the next step was done professionally &#8211; the IVR had me state my name, then key in my phone number, then confirm it when it read it back to me &#8211; so I have good reason to believe they will really get back to me. Which is actually better than the silly music. So giving me this way out is a good idea.</p>
<p>The bad part is, if they knew they were busy (and, assuming it&#8217;s a FIFO queue, they had the necessary information &#8211; my place in line &#8211; as soon as they picked up my call) &#8211; why wait for long minutes of stupid music before switching to the <em>leave-your-name-and-number</em> routine? They&#8217;re giving the customer the combined worst of both solutions!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2009/03/ivr-woes-good-idea-poor-execution/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Standardization of charge indicators (Not!)</title>
		<link>http://designblog.nzeldes.com/2009/03/standardization-of-charge-indicators-not/</link>
		<comments>http://designblog.nzeldes.com/2009/03/standardization-of-charge-indicators-not/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 07:38:19 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Bad design]]></category>
		<category><![CDATA[Good design]]></category>
		<category><![CDATA[Handheld]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2009/03/standardization-of-charge-indicators-not/</guid>
		<description><![CDATA[These days we all have at least half a dozen gadgets whose batteries require charging, and they each come with their own charger (incompatible with all the others, of course). Now, I won&#8217;t push for standardizing the chargers &#8211; can&#8217;t aim that high &#8211; but here is a more modest goal: can we please standardize [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F03%2Fstandardization-of-charge-indicators-not%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F03%2Fstandardization-of-charge-indicators-not%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>These days we all have at least half a dozen gadgets whose batteries require charging, and they each come with their own charger (incompatible with all the others, of course). Now, I won&#8217;t push for standardizing the chargers &#8211; can&#8217;t aim that high &#8211; but here is a more modest goal: can we please standardize the status indicator LEDs on them?</p>
<p><img src="http://designblog.nzeldes.com/wp-content/uploads/2009/03/nikonchargers.jpg" alt="Nikon camera battery chargers" vspace="10" width="500" height="226" /></p>
<p>Here are two chargers that came with my two Nikon cameras, the old point and shoot and the newer DSLR. No, they are not interchangeable, even though the batteries are both Li-Ion and of the same voltage. Both have a LED indicator that blinks during charging and stops blinking when done; however, in one it stays lit when there&#8217;s no battery inserted, and in the other it stays unlit.</p>
<p><img src="http://designblog.nzeldes.com/wp-content/uploads/2009/03/nikoncharger.jpg" alt="Nikon D40 battery charger closeup" vspace="10" width="160" align="right" height="157" hspace="10" />But the bigger problem is remembering what&#8217;s what when you come back later and the light is stable. You see, in these, this means charge complete; but in my cordless shaver it means that it isn&#8217;t; there, blinking indicates a full charge. Different vendor, and they probably just flip a coin at design time&#8230;</p>
<p>My own solution was documenting it all on a post-it note stuck near these chargers; but then Nikon must have realized that this is an issue, because in the later camera &#8211; my D40 DSLR &#8211; they labeled the charger itself to remove any doubt. Good move!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2009/03/standardization-of-charge-indicators-not/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No, I don&#8217;t know anyone in the Ashmore Islands!</title>
		<link>http://designblog.nzeldes.com/2009/01/no-i-dont-know-anyone-in-the-ashmore-islands/</link>
		<comments>http://designblog.nzeldes.com/2009/01/no-i-dont-know-anyone-in-the-ashmore-islands/#comments</comments>
		<pubDate>Mon, 12 Jan 2009 21:10:07 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Bad design]]></category>
		<category><![CDATA[Improvement]]></category>
		<category><![CDATA[HFE]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2009/01/no-i-dont-know-anyone-in-the-ashmore-islands/</guid>
		<description><![CDATA[Two of the least pleasant-to-use GUI controls are the scrollable list box and its cousin the drop-down list, especially when they have many items listed. Of course, that&#8217;s exactly when they are indispensable&#8230; you can&#8217;t use radio buttons for 50 choices, so if you need to let the user choose a state of the union, [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F01%2Fno-i-dont-know-anyone-in-the-ashmore-islands%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2009%2F01%2Fno-i-dont-know-anyone-in-the-ashmore-islands%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Two of the least pleasant-to-use GUI controls are the scrollable list box and its cousin the drop-down list, especially when they have many items listed. Of course, that&#8217;s exactly when they are indispensable&#8230; you can&#8217;t use radio buttons for 50 choices, so if you need to let the user choose a state of the union, a drop down list is inevitable. Likewise for countries of the world, or for their currencies.</p>
<p>But the way these geographic-oriented controls are implemented in software and web sites is really annoying.</p>
<p><img src="http://designblog.nzeldes.com/wp-content/uploads/2009/01/dropdownlist.jpg" alt="Drop-down List of countries" vspace="10" width="239" align="right" height="166" hspace="10" />Take the image at right, the list you have to go through to select a country for a new contact in Outlook and other applications: it opens on a list of ten countries, of which one &#8211; Argentina &#8211; may be even remotely likely to be inhabited by business contacts of yours. You can scroll down, of course&#8230; and in the next ten you find even greater concentrations of business partners, like the entry for the <a href="http://en.wikipedia.org/wiki/Ashmore_and_Cartier_Islands">Ashmore and Cartier Islands</a>, which are a group of small <em>uninhabited</em> tropical islands in the Indian Ocean!</p>
<p>Not that I have anything against the inhabitants of Ocean islands, or of Angola, Antigua, or Anguilla, but given the statistics, why should I have to scroll past them &#8211; and past Cook Islands, and Namibia, and Nauru, and Palmyra Atoll, for that matter &#8211; on my way to find the US, or the UK, where I really have many more contacts and affairs?</p>
<p>Or look at the next screen grab, from a web site for computing currency exchange rates. Do I really need to have Equatorial Guinea&#8217;s CFA Franc, the Eritrean Nakfa, and the Ethiopian Birr pushing down the Euro and the US Dollar farther away from the British Pound, just because of the accident of alphabetic order?</p>
<p align="center"><img src="http://designblog.nzeldes.com/wp-content/uploads/2009/01/listbox.jpg" alt="List Box of currencies" vspace="10" width="440" height="185" /></p>
<p>Obviously,  the people of Estonia do care about the Kroon (and I care about the Israeli Shekel, also far from the heart of global finances). But what is needed is a list that gives the most common choices &#8211; the Dollar, the Pound, the Euro &#8211; by default at the top of the list, where 99% of users will benefit. And then we need personalization, so each of us in the rest of the world can put their country, or those they deal with, at the very top.</p>
<p>This can be done in many ways. One&#8217;s home country can be extracted from Windows Regional settings and put up front. Web sites may use cookies to remember which currencies you converted last time. Local software tools can keep my choices in the Windows registry. Smarter tools may learn from your past choices and bump them up the list in future. The techniques exist; it&#8217;s just that someone should step out of the silly box and dump the alphabetic order in favor of what makes users more productive and less annoyed!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2009/01/no-i-dont-know-anyone-in-the-ashmore-islands/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>CardScan continues to amaze!</title>
		<link>http://designblog.nzeldes.com/2008/11/cardscan-continues-to-amaze/</link>
		<comments>http://designblog.nzeldes.com/2008/11/cardscan-continues-to-amaze/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 21:01:54 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Good design]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2008/11/cardscan-continues-to-amaze/</guid>
		<description><![CDATA[A few months ago I wrote about the surprisingly good customer service I received when my CardScan business card scanner died. Well, this was no accident, it seems. The other day I installed the CardScan software on another computer and I noticed on the welcome dialog during installation the following fine print: I was impressed. [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F11%2Fcardscan-continues-to-amaze%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F11%2Fcardscan-continues-to-amaze%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>A few months ago I <a href="http://designblog.nzeldes.com/2008/08/great-service-for-a-cardscan/">wrote</a> about the surprisingly good customer service I received when my CardScan business card scanner died. Well, this was no accident, it seems.</p>
<p>The other day I installed the CardScan software on another computer and I noticed on the welcome dialog during installation the following fine print:</p>
<p><img src="http://designblog.nzeldes.com/wp-content/uploads/2008/11/cardscanpresident.jpg" alt="CardScan welcome dialog" vspace="10" width="500" height="158" /></p>
<p>I was impressed. I install many software products, and most never go beyond offering a customer service pointer in case of trouble. Mr. Weyman&#8217;s invitation is much more positive and proactive, and I may take him up on it one day&#8230;</p>
<p>And on the same dialog they also say that you can return the product in the first 30 days for a no-questions-asked refund. These guys really understand customer orientation!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2008/11/cardscan-continues-to-amaze/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amazon fighting infuriating packaging!</title>
		<link>http://designblog.nzeldes.com/2008/11/amazon-fighting-infuriating-packaging/</link>
		<comments>http://designblog.nzeldes.com/2008/11/amazon-fighting-infuriating-packaging/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 19:44:46 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Good design]]></category>
		<category><![CDATA[Environmentalism]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2008/11/amazon-fighting-infuriating-packaging/</guid>
		<description><![CDATA[Ordered some books today and was surprised to find on the Amazon.com home page a message from Jeff Bezos telling of their new initiative to alleviate &#8220;Wrap Rage&#8221; &#8211; &#8220;Amazon Frustration-free packaging&#8220;. Apparently they plan to recruit leading manufacturers to put an end to clamshell blister packs, steel-wire ties and excessive cushioning materials. They aren&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F11%2Famazon-fighting-infuriating-packaging%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F11%2Famazon-fighting-infuriating-packaging%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Ordered some books today and was surprised to find on the <a href="http://www.amazon.com/">Amazon.com</a> home page a message from Jeff Bezos telling of their new initiative to alleviate &#8220;<a href="http://en.wikipedia.org/wiki/Wrap_rage">Wrap Rage</a>&#8221; &#8211; &#8220;<em>Amazon Frustration-free packaging</em>&#8220;. Apparently they plan to recruit leading manufacturers to put an end to clamshell blister packs, steel-wire ties and excessive cushioning materials.</p>
<p align="center"><img src="http://designblog.nzeldes.com/wp-content/uploads/2008/11/frustrationfreepackaging.jpg" alt="Amazon Frustration Free Packaging compared to regular packaging" vspace="10" /></p>
<p>They aren&#8217;t necessarily resorting to Julie Andrews&#8217;s &#8220;Brown paper packages tied up with strings&#8221;, but they will push for smaller, easy-to-open, recyclable cardboard boxes designed to minimize both waste and customer fury. What&#8217;s more, these plain boxes are designed to ship as they are, without need for an additional shipping carton. More details <a href="http://www.amazon.com/gp/help/customer/display.html?nodeId=200285450">here</a>.</p>
<p>What can I say? Good idea! I wish more vendors did that sort of thing.</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2008/11/amazon-fighting-infuriating-packaging/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LCD TV screens: can&#8217;t they just switch on?</title>
		<link>http://designblog.nzeldes.com/2008/10/lcd-tv-screens-cant-they-just-switch-on/</link>
		<comments>http://designblog.nzeldes.com/2008/10/lcd-tv-screens-cant-they-just-switch-on/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 06:44:00 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Bad design]]></category>
		<category><![CDATA[Consumer electronics]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2008/10/lcd-tv-screens-cant-they-just-switch-on/</guid>
		<description><![CDATA[One problem with CRT-based television sets and computer monitors was that they took a long moment to turn on, because of the inherent necessity to heat up the filament of the picture tube. How fortunate, then, that the new generation of flat screen displays does not have a filament, allowing them to turn on practically [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F10%2Flcd-tv-screens-cant-they-just-switch-on%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F10%2Flcd-tv-screens-cant-they-just-switch-on%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>One problem with CRT-based television sets and computer monitors was that they took a long moment to turn on, because of the inherent necessity to heat up the filament of the picture tube. How fortunate, then, that the new generation of flat screen displays does not have a filament, allowing them to turn on practically instantly.</p>
<p><strong>But allowing is not the same as doing it.</strong> We bought this little 22&#8243; LCD TV recently, made by MAG, and when you turn it on it takes a full 8 seconds before the picture shows up on the screen. And the last two of those seconds are devoted to showing the manufacturer&#8217;s logo! Opinions about User Experience may vary, but no one would argue that staring at a dark screen, with or without a logo on it, can really enhance that experience.</p>
<p><img vspace="10" width="500" src="http://designblog.nzeldes.com/wp-content/uploads/2008/10/mag-tv.jpg" alt="MAG LCD TV with logo on screen" height="362" /></p>
<p>With all respect, MAG designers, you&#8217;re welcome to etch your logo on the screen bezel in all its glory (as you have); but when I hit that On/Off switch, I want the screen to light up in 2 seconds, max. I know you could do it, if you set your minds to it!</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2008/10/lcd-tv-screens-cant-they-just-switch-on/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Snagit 9 vs. FastStone 6: Simpler is better!</title>
		<link>http://designblog.nzeldes.com/2008/10/snagit-9-vs-faststone-6-simpler-is-better/</link>
		<comments>http://designblog.nzeldes.com/2008/10/snagit-9-vs-faststone-6-simpler-is-better/#comments</comments>
		<pubDate>Mon, 13 Oct 2008 15:07:36 +0000</pubDate>
		<dc:creator>Nathan Zeldes</dc:creator>
				<category><![CDATA[Bad design]]></category>
		<category><![CDATA[Design principles]]></category>
		<category><![CDATA[Good design]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://designblog.nzeldes.com/2008/10/snagit-9-vs-faststone-6-simpler-is-better/</guid>
		<description><![CDATA[I needed a screen grabber, and based on recommendations from a friend downloaded the trial version of Snagit 9. I was impressed and disappointed.Impressed, because this is one potent package. It can do everything you may ever want to do about image grabbing. I particularly liked the &#8220;Scrolling window&#8221; option, for capturing a web page [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F10%2Fsnagit-9-vs-faststone-6-simpler-is-better%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdesignblog.nzeldes.com%2F2008%2F10%2Fsnagit-9-vs-faststone-6-simpler-is-better%2F&amp;source=nzeldes&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<link rel="stylesheet" type="text/css" href="http://designblog.nzeldes.com/default.css" />I needed a screen grabber, and based on recommendations from a friend downloaded the trial version of Snagit 9. I was impressed and disappointed.Impressed, because this is one potent package. It can do everything you may ever want to do about image grabbing. I particularly liked the &#8220;Scrolling window&#8221; option, for capturing a web page longer than one screenful. BUT… this program has an extremely complex and ornate user interface, giving you access to countless possibilities; and these are presented in the most colorful UI I&#8217;ve seen since my kids graduated from Fisher-Price. Take a look :
<p><img vspace="10" src="http://designblog.nzeldes.com/wp-content/uploads/2008/10/snagit-ui.jpg" alt="Snagit 9 User Interface" /></p>
<p>Compare this to Photoshop: powerful and feature rich, but its UI is simple, with minimalist icons in monochrome…</p>
<p><img align="right" src="http://designblog.nzeldes.com/wp-content/uploads/2008/10/faststone-ui.jpg" hspace="10" alt="FastStone user interface" />I found this so distracting that I went and downloaded another shareware product, FastStone Capture (Ver. 6). Check the utterly simple UI to the right:</p>
<p>Note that 99% of the time, these few icons (including &#8220;Scrolling window&#8221;) cover all you need; the rest is accessible but unobtrusive in a drop down menu at the right, where it can&#8217;t distract you. Click a button on this tiny floating toolbar and the capture begins. The same icons exist in the Snagit window, but actually, once you click one there you then need to click the big red round button &#8211; which may make you feel powerful, but is a redundant action. Of course it&#8217;s a single extra click, but it&#8217;s also double the number of clicks required  in FastStone.</p>
<p>Interestingly, the development team at Snagit have a blog where they share their thoughts (commendable!) and <a href="http://visuallounge.techsmith.com/2008/06/road_to_snagit_9_sylvania_dye.html">there I read</a> that &#8220;… we felt that the interface shouldn&#8217;t be competing for attention, but should fade away and allow people to focus on their content&#8221;. Sorry… good thought, but I can&#8217;t endorse the execution on it. Nothing about the baroque UI they built brings the word &#8220;Fade&#8221; to mind. Just compare it to the tiny toolbar of the FastStone tool.</p>
<p><strong>Simpler is better,</strong> nowhere more so than in tools you use daily.</p>
]]></content:encoded>
			<wfw:commentRss>http://designblog.nzeldes.com/2008/10/snagit-9-vs-faststone-6-simpler-is-better/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

