<?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: Three Amazon Design Ideas</title>
	<atom:link href="http://www.andersramsay.com/2009/04/03/three-amazon-design-ideas/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andersramsay.com/2009/04/03/three-amazon-design-ideas</link>
	<description>designing user experiences</description>
	<lastBuildDate>Tue, 31 Jan 2012 23:48:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Anders</title>
		<link>http://www.andersramsay.com/2009/04/03/three-amazon-design-ideas/comment-page-1#comment-13703</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Mon, 13 Apr 2009 19:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=500#comment-13703</guid>
		<description>Hi Fredrik - interesting point about different purchasing options being tied to different organizational units.  I think my approach would be to meet with each of the representatives of those units and communicate to them that all organizational units would benefit from being displayed in a unified way.

At the same time, I&#039;m not even sure if the reason for the current somewhat Frankensteinian display is tied to there being different org. units that are responsible for the various purchasing options.  My guess is that it instead is a consequence of many many continual design updates to these templates, which over time has led to the current somewhat fractured visual representation.</description>
		<content:encoded><![CDATA[<p>Hi Fredrik &#8211; interesting point about different purchasing options being tied to different organizational units.  I think my approach would be to meet with each of the representatives of those units and communicate to them that all organizational units would benefit from being displayed in a unified way.</p>
<p>At the same time, I&#8217;m not even sure if the reason for the current somewhat Frankensteinian display is tied to there being different org. units that are responsible for the various purchasing options.  My guess is that it instead is a consequence of many many continual design updates to these templates, which over time has led to the current somewhat fractured visual representation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Matheson</title>
		<link>http://www.andersramsay.com/2009/04/03/three-amazon-design-ideas/comment-page-1#comment-13702</link>
		<dc:creator>Fredrik Matheson</dc:creator>
		<pubDate>Mon, 13 Apr 2009 18:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.andersramsay.com/?p=500#comment-13702</guid>
		<description>I think your redesign solves quite a few problems. I like it.

Interestingly, the three sections you meld into one (buy new, buy used and add to list) are quite likely under the purview of three different people/units at Amazon. Thus, the redesign would require quite a bit of organizational facilitation.

What would be your approach here?</description>
		<content:encoded><![CDATA[<p>I think your redesign solves quite a few problems. I like it.</p>
<p>Interestingly, the three sections you meld into one (buy new, buy used and add to list) are quite likely under the purview of three different people/units at Amazon. Thus, the redesign would require quite a bit of organizational facilitation.</p>
<p>What would be your approach here?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

