<?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"
	>
<channel>
	<title>Comments on: Usability Tools Podcast: Avoiding Redesigns</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<pubDate>Mon, 12 May 2008 21:45:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: David Nilsson</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-100110</link>
		<dc:creator>David Nilsson</dc:creator>
		<pubDate>Fri, 21 Dec 2007 20:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-100110</guid>
		<description>&lt;a href="http://www.alistapart.com/articles/redesignrealign" rel="nofollow"&gt;Good Designers Redesign, Great Designers Realign&lt;/a&gt;

The "buzzword" explained.</description>
		<content:encoded><![CDATA[<p><a href="http://www.alistapart.com/articles/redesignrealign" rel="nofollow">Good Designers Redesign, Great Designers Realign</a></p>
<p>The &#8220;buzzword&#8221; explained.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Crossman</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-98837</link>
		<dc:creator>Kevin Crossman</dc:creator>
		<pubDate>Sun, 09 Dec 2007 18:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-98837</guid>
		<description>I like the podcast and especially like the intro music. I've sent you guys several notes asking who the artist is, but no response. I'd think that if you're using some artists music in your podcast that you would either attribute it someplace or (as a courtesy to the band) respond to inquiries regarding it (I'd love to purchase their songs!).  So, who does the music? :-)</description>
		<content:encoded><![CDATA[<p>I like the podcast and especially like the intro music. I&#8217;ve sent you guys several notes asking who the artist is, but no response. I&#8217;d think that if you&#8217;re using some artists music in your podcast that you would either attribute it someplace or (as a courtesy to the band) respond to inquiries regarding it (I&#8217;d love to purchase their songs!).  So, who does the music? <img src='http://www.uie.com/brainsparks/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Szuc</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-98308</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Sat, 08 Dec 2007 08:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-98308</guid>
		<description>We use the term "redesign" and often its spoken of as it related to "visual change" which makes sense.  Change a template, navigation, color, widget etc

However, what truly drives something that needs to change -- What drives Amazon to tweak? What drives Netflix to Tweak? What drives Google to Tweak? 

What should teams be looking for to help better determine if something needs to change? 

I dont think anything should just be redesigned for the sake of a new look (although often thats the case). It should go much deeper into questions that designers can talk to as to why the change has happened in the first place. Then the conversation moves away from colors, brand to other useful stuff to talk to the business about.</description>
		<content:encoded><![CDATA[<p>We use the term &#8220;redesign&#8221; and often its spoken of as it related to &#8220;visual change&#8221; which makes sense.  Change a template, navigation, color, widget etc</p>
<p>However, what truly drives something that needs to change &#8212; What drives Amazon to tweak? What drives Netflix to Tweak? What drives Google to Tweak? </p>
<p>What should teams be looking for to help better determine if something needs to change? </p>
<p>I dont think anything should just be redesigned for the sake of a new look (although often thats the case). It should go much deeper into questions that designers can talk to as to why the change has happened in the first place. Then the conversation moves away from colors, brand to other useful stuff to talk to the business about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Willard</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97813</link>
		<dc:creator>Paul Willard</dc:creator>
		<pubDate>Fri, 07 Dec 2007 00:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97813</guid>
		<description>I love incrimental change for the company's needs; makes development lower risk, allows you to learn and adjust allong the way, promotes more efficient development processes like agile and extreme.  I often debate if a customer would rather see their site constantly changing underneath them vs seeing one big change every year or two.  For shopping sites and customer acquistion flows that people use less frequently, this would not matter, and you might as well enjoy the benefits of continuous small change, but a service oriented site like banking with trust issues and frequent repeat visits might prefer less frequent, larger changes and the appearance of greater stability to continuous small incremental changes and the appearance of dynamicism.</description>
		<content:encoded><![CDATA[<p>I love incrimental change for the company&#8217;s needs; makes development lower risk, allows you to learn and adjust allong the way, promotes more efficient development processes like agile and extreme.  I often debate if a customer would rather see their site constantly changing underneath them vs seeing one big change every year or two.  For shopping sites and customer acquistion flows that people use less frequently, this would not matter, and you might as well enjoy the benefits of continuous small change, but a service oriented site like banking with trust issues and frequent repeat visits might prefer less frequent, larger changes and the appearance of greater stability to continuous small incremental changes and the appearance of dynamicism.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lis</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97646</link>
		<dc:creator>Lis</dc:creator>
		<pubDate>Wed, 05 Dec 2007 14:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97646</guid>
		<description>I'd also like to hear the difference. My company just went through a similar exercise to what Amazon has done. We restructured the pages within the site as well as change the box model of the pages. It sure felt like a huge redesign to me, but I'm interested in hearing the rationale behind calling it a re-alignment.</description>
		<content:encoded><![CDATA[<p>I&#8217;d also like to hear the difference. My company just went through a similar exercise to what Amazon has done. We restructured the pages within the site as well as change the box model of the pages. It sure felt like a huge redesign to me, but I&#8217;m interested in hearing the rationale behind calling it a re-alignment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Klaiber</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97594</link>
		<dc:creator>Nate Klaiber</dc:creator>
		<pubDate>Wed, 05 Dec 2007 02:58:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97594</guid>
		<description>@KM
So what is the difference between a re-align and a re-design? They clearly re-designed. The design is no longer the same. The architecture is not the same. The hierarchy is slightly different in several areas. I wouldn't say everything is familiar, I used to easily be able to get to my profile and a few other sections, now I have to hunt for those things.

I think re-align is a buzzword to avoid re-design, personally. If they simply updated the design slightly, but the navigation, structure, and hierarchy stayed the same - then I would consider it a re-align, but they changed much more than that. As you pointed out, the navigation is in a completely different spot.

I understand it was a long time coming, and I do like it - but I don't understand how this isn't considered a large re-design?</description>
		<content:encoded><![CDATA[<p>@KM<br />
So what is the difference between a re-align and a re-design? They clearly re-designed. The design is no longer the same. The architecture is not the same. The hierarchy is slightly different in several areas. I wouldn&#8217;t say everything is familiar, I used to easily be able to get to my profile and a few other sections, now I have to hunt for those things.</p>
<p>I think re-align is a buzzword to avoid re-design, personally. If they simply updated the design slightly, but the navigation, structure, and hierarchy stayed the same - then I would consider it a re-align, but they changed much more than that. As you pointed out, the navigation is in a completely different spot.</p>
<p>I understand it was a long time coming, and I do like it - but I don&#8217;t understand how this isn&#8217;t considered a large re-design?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KM</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97586</link>
		<dc:creator>KM</dc:creator>
		<pubDate>Wed, 05 Dec 2007 01:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97586</guid>
		<description>I wouldn't say Amazon re-designed, I'd say they re-aligned. All the sections are essentially the same, they've been slowly working towards this layout that they currently have. Everything is still very familiar, the only thing that is "very" different is the main navigation which is now on the side and with dropdowns. This was a long time coming because they were really pushing the limits of their tabbed navigation.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say Amazon re-designed, I&#8217;d say they re-aligned. All the sections are essentially the same, they&#8217;ve been slowly working towards this layout that they currently have. Everything is still very familiar, the only thing that is &#8220;very&#8221; different is the main navigation which is now on the side and with dropdowns. This was a long time coming because they were really pushing the limits of their tabbed navigation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Klaiber</title>
		<link>http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97560</link>
		<dc:creator>Nate Klaiber</dc:creator>
		<pubDate>Tue, 04 Dec 2007 21:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/03/usability-tools-podcast-avoiding-redesigns/#comment-97560</guid>
		<description>In regards to Amazon re-designing, isn't that what they recently did? A completely new layout and the interface has been moved around. While I understand the premise and foundation, what are the thoughts with Amazon re-designing?</description>
		<content:encoded><![CDATA[<p>In regards to Amazon re-designing, isn&#8217;t that what they recently did? A completely new layout and the interface has been moved around. While I understand the premise and foundation, what are the thoughts with Amazon re-designing?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
