<?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:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Usability and Branding: You Can Have Both</title>
	<atom:link href="http://www.highcontext.com/hcarchives/2006/02/12/usability-and-branding-you-can-have-both/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.highcontext.com/hcarchives/2006/02/12/usability-and-branding-you-can-have-both/</link>
	<description>Unleashing the strategic potential of the Web.</description>
	<lastBuildDate>Tue, 03 Aug 2010 20:47:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Association Inc. &#187; Blog Archive &#187; Usability, Experience, and the Art of Burritos</title>
		<link>http://www.highcontext.com/hcarchives/2006/02/12/usability-and-branding-you-can-have-both/comment-page-1/#comment-964</link>
		<dc:creator>Association Inc. &#187; Blog Archive &#187; Usability, Experience, and the Art of Burritos</dc:creator>
		<pubDate>Tue, 14 Feb 2006 04:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.highcontext.com/?p=602#comment-964</guid>
		<description>[...] UPDATE: Just noticed that David responded, and I think we agree more than he thinks: I agree that Chipotle could also have changed its website to showcase its locator more than it does without losing its &#8220;hipness.&#8221; However, I stand by my contention that in any comparison between these two sites &#8212; a comparison that I didn&#8217;t choose but am merely commenting upon &#8212; Chipotle wins, hands down. The BajaFresh site, any way you look at it, simply sucks. [...]</description>
		<content:encoded><![CDATA[<p>[...] UPDATE: Just noticed that David responded, and I think we agree more than he thinks: I agree that Chipotle could also have changed its website to showcase its locator more than it does without losing its &#8220;hipness.&#8221; However, I stand by my contention that in any comparison between these two sites &#8212; a comparison that I didn&#8217;t choose but am merely commenting upon &#8212; Chipotle wins, hands down. The BajaFresh site, any way you look at it, simply sucks. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred Simmons</title>
		<link>http://www.highcontext.com/hcarchives/2006/02/12/usability-and-branding-you-can-have-both/comment-page-1/#comment-963</link>
		<dc:creator>Fred Simmons</dc:creator>
		<pubDate>Mon, 13 Feb 2006 15:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.highcontext.com/?p=602#comment-963</guid>
		<description>I&#039;m with you on this one. Search Google for &quot;Chipotle locations&quot; and you get http://www.chipotlefan.com/index.php?id=locations, a site &quot;not affiliated with Chipotle Mexican Grill.&quot; The funny thing is once you submit a search it takes you back to chipotle.com&#039;s results page. It&#039;s a fan&#039;s fix for poor functionality. Too funny.

I&#039;m all for branding consistency, but there&#039;s easy ways to make Flash searchable these days. They just have lazy developers.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with you on this one. Search Google for &#8220;Chipotle locations&#8221; and you get <a href="http://www.chipotlefan.com/index.php?id=locations" rel="nofollow">http://www.chipotlefan.com/index.php?id=locations</a>, a site &#8220;not affiliated with Chipotle Mexican Grill.&#8221; The funny thing is once you submit a search it takes you back to chipotle.com&#8217;s results page. It&#8217;s a fan&#8217;s fix for poor functionality. Too funny.</p>
<p>I&#8217;m all for branding consistency, but there&#8217;s easy ways to make Flash searchable these days. They just have lazy developers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
