<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Plugging Holes in the Experience, Sort Of</title>
	<atom:link href="http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 11 Feb 2012 08:11:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Pete Williams</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-145318</link>
		<dc:creator>Pete Williams</dc:creator>
		<pubDate>Fri, 16 Jan 2009 12:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-145318</guid>
		<description>I would suggest that UPS effectively have two tracking numbers, one for the shipper and one for the recipient. This could be as simple as adding a given letter to the front or end of the existing number to identify it as a recipient&#039;s enquiry. 

This would allow them to tailor the interface and associated terminology/statuses to the correct audience. As mentioned billing information isn&#039;t relevent to the recipient, so their status would simply say whether it has been received by UPS or not, and if so where it&#039;s got to.</description>
		<content:encoded><![CDATA[<p>I would suggest that UPS effectively have two tracking numbers, one for the shipper and one for the recipient. This could be as simple as adding a given letter to the front or end of the existing number to identify it as a recipient&#8217;s enquiry. </p>
<p>This would allow them to tailor the interface and associated terminology/statuses to the correct audience. As mentioned billing information isn&#8217;t relevent to the recipient, so their status would simply say whether it has been received by UPS or not, and if so where it&#8217;s got to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Avore</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-145058</link>
		<dc:creator>Chris Avore</dc:creator>
		<pubDate>Wed, 07 Jan 2009 14:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-145058</guid>
		<description>I&#039;ve been driven nuts by this ridiculous tracking process for years. While I agree the updated tracking screen is better, I still feel like I&#039;m looking under the hood at some technical process I probably shouldn&#039;t have access to, based on the choice of language, codes and the like. 

I&#039;ve taken a few minutes to re-prioritize the layout and posted the new mockup here:

http://www.erova.com/blog/?p=65

Another uhh, interesting, UI choice the UPS guys have made is the Log In button right next to their search box.  I wonder how many search logs reveal usernames...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been driven nuts by this ridiculous tracking process for years. While I agree the updated tracking screen is better, I still feel like I&#8217;m looking under the hood at some technical process I probably shouldn&#8217;t have access to, based on the choice of language, codes and the like. </p>
<p>I&#8217;ve taken a few minutes to re-prioritize the layout and posted the new mockup here:</p>
<p><a href="http://www.erova.com/blog/?p=65" rel="nofollow">http://www.erova.com/blog/?p=65</a></p>
<p>Another uhh, interesting, UI choice the UPS guys have made is the Log In button right next to their search box.  I wonder how many search logs reveal usernames&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: erova &#8226; UX Remix: UPS Tracking Screen - erova notebook &#8226; a user experience blog by Chris Avore</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-145057</link>
		<dc:creator>erova &#8226; UX Remix: UPS Tracking Screen - erova notebook &#8226; a user experience blog by Chris Avore</dc:creator>
		<pubDate>Wed, 07 Jan 2009 14:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-145057</guid>
		<description>[...] Spool&#8217;s January 3rd, 2009 Plugging Holes in the Experience, Sort Of questions the layout, language, and design (and ultimately the audience) of UPS&#8217;s package [...]</description>
		<content:encoded><![CDATA[<p>[...] Spool&#8217;s January 3rd, 2009 Plugging Holes in the Experience, Sort Of questions the layout, language, and design (and ultimately the audience) of UPS&#8217;s package [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Zuschlag</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-145017</link>
		<dc:creator>Michael Zuschlag</dc:creator>
		<pubDate>Mon, 05 Jan 2009 19:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-145017</guid>
		<description>Looks like a classic case of the content written in terms important to the _writer_ not the _reader_. Getting billing information from the shipper matters a lot to UPS, but not a hoot to the user. What matters to the reader is when they will get the shipment. If UPS can’t determine specifically when they’ll get the package from the vendor, they can at least say something like “[Vendor] has notified UPS that this shipment will be ready in the near future.” Maybe even include text to the effect of “If the shipment is included with the next pickup from [Vendor], the package should arrive at your door on [Date].” That at least sets a lower bound on when the reader can expect the shipment.</description>
		<content:encoded><![CDATA[<p>Looks like a classic case of the content written in terms important to the _writer_ not the _reader_. Getting billing information from the shipper matters a lot to UPS, but not a hoot to the user. What matters to the reader is when they will get the shipment. If UPS can’t determine specifically when they’ll get the package from the vendor, they can at least say something like “[Vendor] has notified UPS that this shipment will be ready in the near future.” Maybe even include text to the effect of “If the shipment is included with the next pickup from [Vendor], the package should arrive at your door on [Date].” That at least sets a lower bound on when the reader can expect the shipment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Franceschini</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-145015</link>
		<dc:creator>Gary Franceschini</dc:creator>
		<pubDate>Mon, 05 Jan 2009 18:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-145015</guid>
		<description>The page looks to me to be very close to what I, the customer, need.

However, I *would* remove the text in bold (it was the last thing I read - on the second reading) and change the Status line to read something like: &quot;Verifying information with vendor. Check later for updated shipment status or contact shipper for details.&quot;</description>
		<content:encoded><![CDATA[<p>The page looks to me to be very close to what I, the customer, need.</p>
<p>However, I *would* remove the text in bold (it was the last thing I read &#8211; on the second reading) and change the Status line to read something like: &#8220;Verifying information with vendor. Check later for updated shipment status or contact shipper for details.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederic</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-144992</link>
		<dc:creator>Frederic</dc:creator>
		<pubDate>Mon, 05 Jan 2009 09:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-144992</guid>
		<description>I guess, as a customer, you want to know that something positive is happening somewhere on the chain. Potentially, a simple way to plug this hole would be to have the system say something like: &quot;xxxxxxx has informed us that your order is ready for shipment. We&#039;re taking care of it and you will receive it shortly&quot;

The process is the same but the message is different. That can be the difference between a positive or incomplete experience.</description>
		<content:encoded><![CDATA[<p>I guess, as a customer, you want to know that something positive is happening somewhere on the chain. Potentially, a simple way to plug this hole would be to have the system say something like: &#8220;xxxxxxx has informed us that your order is ready for shipment. We&#8217;re taking care of it and you will receive it shortly&#8221;</p>
<p>The process is the same but the message is different. That can be the difference between a positive or incomplete experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-144937</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Sun, 04 Jan 2009 16:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-144937</guid>
		<description>@Daniel brings up a good point: &lt;em&gt;&quot;Does UPS care?&quot;&lt;/em&gt;

The UPS designers have aimed the new design at their paying customers—the shippers. The recipients don&#039;t pay UPS, so it could be that they aren&#039;t really that interested in making that audience as happy.

However, as @Vivienne points out, this is a touchpoint for a future potential customer. UPS has a big business delivering packages from individual customers. People who receive things are likely to someday be people who ship things. Since the UPS logo and brand elements are all over the status page (which, in itself is interesting—why not brand it with the shippers logo and be invisible?), people will associate their experience with the UPS brand. A bad experience here will create &lt;em&gt;bad juju&lt;/em&gt; (the technical term for weakened brand engagement) with these potential customers.

But, wait, there&#039;s more. High end retailers, like Williams-Sonoma and Lands&#039; End use UPS as their delivery agent. If, in the process of servicing their orders, UPS creates bad juju, some of that juju rubs off on the e-commerce retailer. 

@Daniel asked how many calls UPS gets? I&#039;m wondering how many calls the vendor gets when the UPS interface is inscrutable. It could be that if the retailer feels UPS is running up their support costs or hurting their brand, it&#039;s worth reconsidering their shipping partner.</description>
		<content:encoded><![CDATA[<p>@Daniel brings up a good point: <em>&#8220;Does UPS care?&#8221;</em></p>
<p>The UPS designers have aimed the new design at their paying customers—the shippers. The recipients don&#8217;t pay UPS, so it could be that they aren&#8217;t really that interested in making that audience as happy.</p>
<p>However, as @Vivienne points out, this is a touchpoint for a future potential customer. UPS has a big business delivering packages from individual customers. People who receive things are likely to someday be people who ship things. Since the UPS logo and brand elements are all over the status page (which, in itself is interesting—why not brand it with the shippers logo and be invisible?), people will associate their experience with the UPS brand. A bad experience here will create <em>bad juju</em> (the technical term for weakened brand engagement) with these potential customers.</p>
<p>But, wait, there&#8217;s more. High end retailers, like Williams-Sonoma and Lands&#8217; End use UPS as their delivery agent. If, in the process of servicing their orders, UPS creates bad juju, some of that juju rubs off on the e-commerce retailer. </p>
<p>@Daniel asked how many calls UPS gets? I&#8217;m wondering how many calls the vendor gets when the UPS interface is inscrutable. It could be that if the retailer feels UPS is running up their support costs or hurting their brand, it&#8217;s worth reconsidering their shipping partner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivienne Woodhead</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-144913</link>
		<dc:creator>Vivienne Woodhead</dc:creator>
		<pubDate>Sun, 04 Jan 2009 04:36:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-144913</guid>
		<description>&quot;Does UPS care?&quot; The impact of improving a customer&#039;s experience may not be directly measurable in terms of $¢/time for UPS, but for the customer ease of use is not only a matter of customer time = customer money. Their feeling about UPS being bad or good at understanding and communication affects their likelihood of using it again. A good user experience is like good ads, good Customer Service, it&#039;s a tad touchy feely but it affects a company&#039;s bottom line if they are a pain to do business with, and appear not to care about the customer&#039;s convenience.</description>
		<content:encoded><![CDATA[<p>&#8220;Does UPS care?&#8221; The impact of improving a customer&#8217;s experience may not be directly measurable in terms of $¢/time for UPS, but for the customer ease of use is not only a matter of customer time = customer money. Their feeling about UPS being bad or good at understanding and communication affects their likelihood of using it again. A good user experience is like good ads, good Customer Service, it&#8217;s a tad touchy feely but it affects a company&#8217;s bottom line if they are a pain to do business with, and appear not to care about the customer&#8217;s convenience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Tunkelang</title>
		<link>http://www.uie.com/brainsparks/2009/01/03/plugging-holes-in-the-experience-sort-of/comment-page-1/#comment-144889</link>
		<dc:creator>Daniel Tunkelang</dc:creator>
		<pubDate>Sat, 03 Jan 2009 20:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=771#comment-144889</guid>
		<description>Seems pretty clear that, if UPS intends this page for package recipients (particularly e-commerce customers), it should offer explanations from their point of view, which is basically UPS Awaiting Shipment From Sender. The tool tip could explain that the sender has sent UPS details about the shipment but not the shipment itself.

Bigger question: does UPS care? Is an improvement to this experience likely to have any impact on their bottom line? In particular, will it affect the decisions of ecommerce sellers to use UPS? And can those sellers work around the poor experience by offering customers custom interfaces to track packages?

That said, I wonder how much UPS spends on customer service, fielding calls from customers confused by this interface.</description>
		<content:encoded><![CDATA[<p>Seems pretty clear that, if UPS intends this page for package recipients (particularly e-commerce customers), it should offer explanations from their point of view, which is basically UPS Awaiting Shipment From Sender. The tool tip could explain that the sender has sent UPS details about the shipment but not the shipment itself.</p>
<p>Bigger question: does UPS care? Is an improvement to this experience likely to have any impact on their bottom line? In particular, will it affect the decisions of ecommerce sellers to use UPS? And can those sellers work around the poor experience by offering customers custom interfaces to track packages?</p>
<p>That said, I wonder how much UPS spends on customer service, fielding calls from customers confused by this interface.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

