<?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: Should Nav be on the Left or on the Right?</title>
	<atom:link href="http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 25 May 2013 00:51:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Designing faceted search: Getting the basics right (part 1) &#171; Information Interaction</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-159832</link>
		<dc:creator>Designing faceted search: Getting the basics right (part 1) &#171; Information Interaction</dc:creator>
		<pubDate>Wed, 18 May 2011 10:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-159832</guid>
		<description>[...] has been written about the merits of left vs. right hand placement for navigation menus, which we won’t repeat here. However, two caveats apply. Firstly, for faceted navigation (as [...]</description>
		<content:encoded><![CDATA[<p>[...] has been written about the merits of left vs. right hand placement for navigation menus, which we won’t repeat here. However, two caveats apply. Firstly, for faceted navigation (as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cpo</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-149942</link>
		<dc:creator>cpo</dc:creator>
		<pubDate>Fri, 19 Feb 2010 01:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-149942</guid>
		<description>Check out 2 &quot;right sided navigation&quot; sites I&#039;ve encountered on the web (among the hundreds or thousands):
http://www.boost.org/
http://www.multcolib.org/

They &quot;seem&quot; to work, IMHO.  Content focusing seems better, but again that&#039;s only MHO.  Right-sided navigation is probably a calculated risk web designers make.</description>
		<content:encoded><![CDATA[<p>Check out 2 &#8220;right sided navigation&#8221; sites I&#8217;ve encountered on the web (among the hundreds or thousands):<br />
<a href="http://www.boost.org/" rel="nofollow">http://www.boost.org/</a><br />
<a href="http://www.multcolib.org/" rel="nofollow">http://www.multcolib.org/</a></p>
<p>They &#8220;seem&#8221; to work, IMHO.  Content focusing seems better, but again that&#8217;s only MHO.  Right-sided navigation is probably a calculated risk web designers make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2006-04-23 at disambiguity</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-6434</link>
		<dc:creator>links for 2006-04-23 at disambiguity</dc:creator>
		<pubDate>Sun, 23 Apr 2006 09:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-6434</guid>
		<description>[...] Should Nav be on the Left or on the Right? UIE Brain Sparks Jared says: having tested a ton of users on bundles of sites, we’ve learned over the years that navigation placement doesn’t matter one whit. Put the navigation practically anywhere on the page and users will find it when they need it. (tags: navigation usability RHS-navigation research) [...]</description>
		<content:encoded><![CDATA[<p>[...] Should Nav be on the Left or on the Right? UIE Brain Sparks Jared says: having tested a ton of users on bundles of sites, we’ve learned over the years that navigation placement doesn’t matter one whit. Put the navigation practically anywhere on the page and users will find it when they need it. (tags: navigation usability RHS-navigation research) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Expressions &#187; Blog Archive &#187; WordPress Themes</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-1248</link>
		<dc:creator>Expressions &#187; Blog Archive &#187; WordPress Themes</dc:creator>
		<pubDate>Fri, 03 Feb 2006 05:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-1248</guid>
		<description>[...] The better way of choosing a theme is not to look at the presentation, but rather the structure. There are only a few possibilities. One column, two column, three column and maybe even four column. After choosing the number of columns you choose the location of your navigation bar and the content, left vs right. Then finally you choose whether you want fixed width or fluid full browser width. [...]</description>
		<content:encoded><![CDATA[<p>[...] The better way of choosing a theme is not to look at the presentation, but rather the structure. There are only a few possibilities. One column, two column, three column and maybe even four column. After choosing the number of columns you choose the location of your navigation bar and the content, left vs right. Then finally you choose whether you want fixed width or fluid full browser width. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Expressions &#187; Blog Archive &#187; Wordpress Themes</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-1247</link>
		<dc:creator>Expressions &#187; Blog Archive &#187; Wordpress Themes</dc:creator>
		<pubDate>Fri, 03 Feb 2006 04:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-1247</guid>
		<description>[...] The better way of choosing a theme is not to look at the presentation, but rather the structure. There are only a few possibilities. One column, two column, three column and maybe even four column. After choosing the number of columns you choose the location of your navigation bar and the content, left vs right. Then finally you choose whether you want fixed width or fluid full browser width. Once you choose the structure from the possibilities above, just look at themes that come closest to what you want as a starting point and then start hacking the theme.  Contrary to what you might believe, you do need to customize your theme somewhat. [...]</description>
		<content:encoded><![CDATA[<p>[...] The better way of choosing a theme is not to look at the presentation, but rather the structure. There are only a few possibilities. One column, two column, three column and maybe even four column. After choosing the number of columns you choose the location of your navigation bar and the content, left vs right. Then finally you choose whether you want fixed width or fluid full browser width. Once you choose the structure from the possibilities above, just look at themes that come closest to what you want as a starting point and then start hacking the theme.  Contrary to what you might believe, you do need to customize your theme somewhat. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kirkwood</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-248</link>
		<dc:creator>Andy Kirkwood</dc:creator>
		<pubDate>Sun, 06 Nov 2005 08:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-248</guid>
		<description>I find it useful to refer to the usability.govt &lt;a href=&quot;http://usability.gov/basics/index.html&quot; rel=&quot;nofollow&quot;&gt;what is usability&lt;/a&gt; when considering the issue of left vs right navigation.

&lt;strong&gt;Ease of learning&lt;/strong&gt;: if well-designed, i.e. &#039;looks&#039; like navigation, communicates its function, no difference; left 1, right 1&lt;strong&gt;Efficiency of use&lt;/strong&gt;: depends on how the user browses and the task they are trying to complete, assuming scrolling using the scrollbar on the right of the browser window, it takes less time to move the mouse from bottom-right to top-right; left 0, right 1&lt;strong&gt;Memorability&lt;/strong&gt;: once learnt, likely to be equal; left 1, right 1&lt;strong&gt;Error frequency&lt;/strong&gt;: n/a&lt;strong&gt;Subjective satisfaction&lt;/strong&gt;: left matches conventions (or at least it did prior to the blog revolution), right may cause a slight mental &#039;twinge&#039;; left 1, right .5

Tally: left 3 right 3.5.

And now the deciding round.

What is the user&#039;s mental model (their instinctive understanding) of the relationship between the navigation and the content based on the location of the navigation on the page?

My belief is that left hand navigation, at an instinctual level, is commonly understood as a formal &lt;strong&gt;hierarchy&lt;/strong&gt;, locating the content within a greater information structure (similar to a topic path/breadcrumb nav).
Right-hand navigation is likely to suggest links that are &lt;strong&gt;related&lt;/strong&gt; to the current content, e.g. of a similar granularity, topic or in the case of blogs, another entry (i.e. related by author). This understanding of right hand navigation is likely to be based on the layout conventions of print and newspapers where sidebars tend to be positioned to the right of articles.

If the placement of the navigation corresponds with the relationship between navigation and content, then the fight could be decided in favour of either the left or right.
So context appears to be the winner on the night.

(Enabling repetitive links to be by-passed by users with assistive technologies is not included in this discussion, as both left and right navigation can equally be made accessible.)</description>
		<content:encoded><![CDATA[<p>I find it useful to refer to the usability.govt <a href="http://usability.gov/basics/index.html" rel="nofollow">what is usability</a> when considering the issue of left vs right navigation.</p>
<p><strong>Ease of learning</strong>: if well-designed, i.e. &#8216;looks&#8217; like navigation, communicates its function, no difference; left 1, right 1<strong>Efficiency of use</strong>: depends on how the user browses and the task they are trying to complete, assuming scrolling using the scrollbar on the right of the browser window, it takes less time to move the mouse from bottom-right to top-right; left 0, right 1<strong>Memorability</strong>: once learnt, likely to be equal; left 1, right 1<strong>Error frequency</strong>: n/a<strong>Subjective satisfaction</strong>: left matches conventions (or at least it did prior to the blog revolution), right may cause a slight mental &#8216;twinge&#8217;; left 1, right .5</p>
<p>Tally: left 3 right 3.5.</p>
<p>And now the deciding round.</p>
<p>What is the user&#8217;s mental model (their instinctive understanding) of the relationship between the navigation and the content based on the location of the navigation on the page?</p>
<p>My belief is that left hand navigation, at an instinctual level, is commonly understood as a formal <strong>hierarchy</strong>, locating the content within a greater information structure (similar to a topic path/breadcrumb nav).<br />
Right-hand navigation is likely to suggest links that are <strong>related</strong> to the current content, e.g. of a similar granularity, topic or in the case of blogs, another entry (i.e. related by author). This understanding of right hand navigation is likely to be based on the layout conventions of print and newspapers where sidebars tend to be positioned to the right of articles.</p>
<p>If the placement of the navigation corresponds with the relationship between navigation and content, then the fight could be decided in favour of either the left or right.<br />
So context appears to be the winner on the night.</p>
<p>(Enabling repetitive links to be by-passed by users with assistive technologies is not included in this discussion, as both left and right navigation can equally be made accessible.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-221</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Tue, 01 Nov 2005 00:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-221</guid>
		<description>&lt;blockquote&gt;I see this as another example of assuming all your users are nondisabled (i.e., all your users are just like you – a typical fanboy error). &lt;/blockquote&gt;

Joe,

Once again, you are absolutely right. We haven&#039;t taken the disabled into account at all in our research. (It&#039;s not that we think they are an unimportant segment, it&#039;s just that we have our hands full trying to understand the problems for the subset of users that are non-disabled.)

&lt;blockquote&gt;Screen-reader and -magnifier users have actual preferences. It does “matter one whit” to them. The problem is they require two different methods. &lt;/blockquote&gt;

Well, what I know about screen readers you could fit onto a very small, well, um, screen. Isn&#039;t it true that in a world of CSS/Standards-goodness, screen-readers and -magnifiers could look into the HTML and pull out the navigation from the other content of the page, assuming it was indicated with some sort of magic tags to do so. How come there hasn&#039;t been a movement to make the magic tags work? Then the readers wouldn&#039;t care about the physical rendering on the page, right?</description>
		<content:encoded><![CDATA[<blockquote><p>I see this as another example of assuming all your users are nondisabled (i.e., all your users are just like you – a typical fanboy error). </p></blockquote>
<p>Joe,</p>
<p>Once again, you are absolutely right. We haven&#8217;t taken the disabled into account at all in our research. (It&#8217;s not that we think they are an unimportant segment, it&#8217;s just that we have our hands full trying to understand the problems for the subset of users that are non-disabled.)</p>
<blockquote><p>Screen-reader and -magnifier users have actual preferences. It does “matter one whit” to them. The problem is they require two different methods. </p></blockquote>
<p>Well, what I know about screen readers you could fit onto a very small, well, um, screen. Isn&#8217;t it true that in a world of CSS/Standards-goodness, screen-readers and -magnifiers could look into the HTML and pull out the navigation from the other content of the page, assuming it was indicated with some sort of magic tags to do so. How come there hasn&#8217;t been a movement to make the magic tags work? Then the readers wouldn&#8217;t care about the physical rendering on the page, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-220</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Tue, 01 Nov 2005 00:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-220</guid>
		<description>Jim, 

You asked, 
&lt;blockquote&gt;doesn’t this all depend on the situation?&lt;/blockquote&gt;

Absolutely! However, some situations are likely to be more frequent than others. And, in our experience, we&#039;ve found that the &lt;strong&gt;need&lt;/strong&gt; for global navigation is quite rare, &lt;em&gt;when the site is designed well&lt;/em&gt;. 

When the site is designed poorly, users will gravitate to global nav frequently. This sets up a addressing-the-symptoms feedback loop: &lt;em&gt;&quot;Oh my, users are asking for better global navigation. We better give it to them.&quot;&lt;/em&gt;

When someone is asking for global nav, it&#039;s best to spend the time to find out why. There&#039;s a good chance there&#039;s a better way to design it.</description>
		<content:encoded><![CDATA[<p>Jim, </p>
<p>You asked, </p>
<blockquote><p>doesn’t this all depend on the situation?</p></blockquote>
<p>Absolutely! However, some situations are likely to be more frequent than others. And, in our experience, we&#8217;ve found that the <strong>need</strong> for global navigation is quite rare, <em>when the site is designed well</em>. </p>
<p>When the site is designed poorly, users will gravitate to global nav frequently. This sets up a addressing-the-symptoms feedback loop: <em>&#8220;Oh my, users are asking for better global navigation. We better give it to them.&#8221;</em></p>
<p>When someone is asking for global nav, it&#8217;s best to spend the time to find out why. There&#8217;s a good chance there&#8217;s a better way to design it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-211</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Sat, 29 Oct 2005 16:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-211</guid>
		<description>Hi Dave,

All fixed.</description>
		<content:encoded><![CDATA[<p>Hi Dave,</p>
<p>All fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-209</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 29 Oct 2005 14:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-209</guid>
		<description>Hi Jared, The URL in the post above is wrong for IxDA ... you have it slightly messed up. It is http://ixda.org

-- dave</description>
		<content:encoded><![CDATA[<p>Hi Jared, The URL in the post above is wrong for IxDA &#8230; you have it slightly messed up. It is <a href="http://ixda.org" rel="nofollow">http://ixda.org</a></p>
<p>&#8211; dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Szuc</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-208</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Sat, 29 Oct 2005 12:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-208</guid>
		<description>There are also cases where users IGNORE navigation completely directing all attention to login to get access their relationship with the company. 

Be interesting to explore and discuss stats from banks, ebays, yahoo to see how much attention we have before login (and what people are using to find information) and post login (when the company has your attention) e.g. login and show me how much i owe, what are my latest transactions etc.</description>
		<content:encoded><![CDATA[<p>There are also cases where users IGNORE navigation completely directing all attention to login to get access their relationship with the company. </p>
<p>Be interesting to explore and discuss stats from banks, ebays, yahoo to see how much attention we have before login (and what people are using to find information) and post login (when the company has your attention) e.g. login and show me how much i owe, what are my latest transactions etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-207</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Sat, 29 Oct 2005 12:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-207</guid>
		<description>I see this as another example of assuming all your users are nondisabled (i.e., all your users are just like you – a typical fanboy error). 

Screen-reader and -magnifier users have actual preferences. It does &quot;matter one whit&quot; to them. The problem is they require two different methods.</description>
		<content:encoded><![CDATA[<p>I see this as another example of assuming all your users are nondisabled (i.e., all your users are just like you – a typical fanboy error). </p>
<p>Screen-reader and -magnifier users have actual preferences. It does &#8220;matter one whit&#8221; to them. The problem is they require two different methods.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-206</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Sat, 29 Oct 2005 08:05:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-206</guid>
		<description>Hey Jared,

doesn&#039;t this all depend on the situation?

I&#039;m the guy who did this study for the Audi website:
http://jodi.tamu.edu/Articles/v04/i01/Kalbach/

Basically, this was a formality to convince the client that the sky was not falling. We as designers knew it was the best design to have the navigation on the right: it&#039;s more innovative (an Audi brand value), none of the competitors have the navigation on the right, Fitt&#039;s law, etc etc. 

Global nav v. no global nav, right v. left side, etc. MAY matter depending on the situation. You can&#039;t make an asituational blanket statement about these things.  Designers just need to get their heads out of guidelines and do what&#039;s best for the situation. Oh yeah, testing with users helps too.

Cheers,
Jim</description>
		<content:encoded><![CDATA[<p>Hey Jared,</p>
<p>doesn&#8217;t this all depend on the situation?</p>
<p>I&#8217;m the guy who did this study for the Audi website:<br />
<a href="http://jodi.tamu.edu/Articles/v04/i01/Kalbach/" rel="nofollow">http://jodi.tamu.edu/Articles/v04/i01/Kalbach/</a></p>
<p>Basically, this was a formality to convince the client that the sky was not falling. We as designers knew it was the best design to have the navigation on the right: it&#8217;s more innovative (an Audi brand value), none of the competitors have the navigation on the right, Fitt&#8217;s law, etc etc. </p>
<p>Global nav v. no global nav, right v. left side, etc. MAY matter depending on the situation. You can&#8217;t make an asituational blanket statement about these things.  Designers just need to get their heads out of guidelines and do what&#8217;s best for the situation. Oh yeah, testing with users helps too.</p>
<p>Cheers,<br />
Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-204</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Sat, 29 Oct 2005 04:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-204</guid>
		<description>&lt;blockquote&gt;-Navigation matters, including global navigation - customers nearly ALWAYS used it and relied upon it to accomplish tasks.&lt;/blockquote&gt;

J D,

With all due respect, how do you know that users nearly always used the global navigation because they preferred to use it? What if they used it because your design forced them to?

In other words, if you had a radically different design that either (a) always had the information they needed on the current page (because you had the forsight to know what they would need) or (b) had local navigation links to the next content they would need, would they still gravitate to the global nav? In our studies, the answer is no.

&lt;blockquote&gt;I may be looking at a cookbook on Amazon.com and decide I need a new roasting pan. There just might not be a local link. &lt;/blockquote&gt;

So, what we&#039;re telling our clients is, instead of worrying about designing the ultimate global nav, use those resources to make sure there&#039;s the right local links. You&#039;ll end up with a design that works much better for users.</description>
		<content:encoded><![CDATA[<blockquote><p>-Navigation matters, including global navigation &#8211; customers nearly ALWAYS used it and relied upon it to accomplish tasks.</p></blockquote>
<p>J D,</p>
<p>With all due respect, how do you know that users nearly always used the global navigation because they preferred to use it? What if they used it because your design forced them to?</p>
<p>In other words, if you had a radically different design that either (a) always had the information they needed on the current page (because you had the forsight to know what they would need) or (b) had local navigation links to the next content they would need, would they still gravitate to the global nav? In our studies, the answer is no.</p>
<blockquote><p>I may be looking at a cookbook on Amazon.com and decide I need a new roasting pan. There just might not be a local link. </p></blockquote>
<p>So, what we&#8217;re telling our clients is, instead of worrying about designing the ultimate global nav, use those resources to make sure there&#8217;s the right local links. You&#8217;ll end up with a design that works much better for users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Cottingham &#187; Healing the left-right navigation bar rift</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-203</link>
		<dc:creator>Rob Cottingham &#187; Healing the left-right navigation bar rift</dc:creator>
		<pubDate>Sat, 29 Oct 2005 04:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-203</guid>
		<description>[...] Over on UIE Brain Sparks, Jared Spool weighs in on the civil war over whether web navigation bars should be on the left or right side of the page: having tested a ton of users on bundles of sites, we’ve learned over the years that navigation placement doesn’t matter one whit. Put the navigation practically anywhere on the page and users will find it when they need it. [...]</description>
		<content:encoded><![CDATA[<p>[...] Over on UIE Brain Sparks, Jared Spool weighs in on the civil war over whether web navigation bars should be on the left or right side of the page: having tested a ton of users on bundles of sites, we’ve learned over the years that navigation placement doesn’t matter one whit. Put the navigation practically anywhere on the page and users will find it when they need it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J D Moore - Marketing Comet</title>
		<link>http://www.uie.com/brainsparks/2005/10/28/should-nav-be-on-the-left-or-on-the-right/comment-page-1/#comment-202</link>
		<dc:creator>J D Moore - Marketing Comet</dc:creator>
		<pubDate>Fri, 28 Oct 2005 21:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=97#comment-202</guid>
		<description>I worked in UI design for the web for almost 10 years and have spent a lot of time in the usability lab of a major financial company. What we found was:

-Navigation matters, including global navigation - customers nearly ALWAYS used it and relied upon it to accomplish tasks.

-Customers get frustrated when they have to &quot;find things&quot; on a web page

-People get trained by conventions like clicking on a comapny logo in the upper right hand of a page bringing you to a home page. Differing from what customers expect is very frustrating for them.

As to right or left side, convention trains people. If you want people to be comfortable using your site - give them what they&#039;re used to. You are just dead wrong to state that you can put global navigation anywhere and it doesn&#039;t matter. What would happen if we suddenly reveresed the gas and brake pedals in a new car? 

Local navigation is important, and should be well designed. However, particularly on large sites, sometimes I want to navigate to first-tier sections. I may be looking at a cookbook on Amazon.com and decide  I need a new roasting pan. There just might not be a local link. If it takes me too long to find the cookware on Amazon - I&#039;ll go elsewhere.</description>
		<content:encoded><![CDATA[<p>I worked in UI design for the web for almost 10 years and have spent a lot of time in the usability lab of a major financial company. What we found was:</p>
<p>-Navigation matters, including global navigation &#8211; customers nearly ALWAYS used it and relied upon it to accomplish tasks.</p>
<p>-Customers get frustrated when they have to &#8220;find things&#8221; on a web page</p>
<p>-People get trained by conventions like clicking on a comapny logo in the upper right hand of a page bringing you to a home page. Differing from what customers expect is very frustrating for them.</p>
<p>As to right or left side, convention trains people. If you want people to be comfortable using your site &#8211; give them what they&#8217;re used to. You are just dead wrong to state that you can put global navigation anywhere and it doesn&#8217;t matter. What would happen if we suddenly reveresed the gas and brake pedals in a new car? </p>
<p>Local navigation is important, and should be well designed. However, particularly on large sites, sometimes I want to navigate to first-tier sections. I may be looking at a cookbook on Amazon.com and decide  I need a new roasting pan. There just might not be a local link. If it takes me too long to find the cookware on Amazon &#8211; I&#8217;ll go elsewhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
